<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>i.MX Processors中的主题 Re: ADV7610 CSI0 input</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380082#M54760</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Got it working actually!&amp;nbsp; I used the interface described in "&lt;A _jive_internal="true" data-containerid="2004" data-containertype="14" data-content-finding="Community" data-objectid="314211" data-objecttype="1" href="https://community.nxp.com/thread/314211" style="font-weight: inherit; font-style: inherit; font-family: inherit; color: #6a737b;"&gt;https://community.freescale.com/thread/314211&lt;/A&gt;" and used internal pulldowns to pull DATA0,1, 10 and 11 low.&amp;nbsp; Using the exisitng CCIR codes seemed to work as well.&amp;nbsp; Thanks!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Allan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 15 Dec 2014 15:52:39 GMT</pubDate>
    <dc:creator>allanmatthew</dc:creator>
    <dc:date>2014-12-15T15:52:39Z</dc:date>
    <item>
      <title>ADV7610 CSI0 input</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380068#M54746</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Has anyone had any luck interfacing an ADV7610/ADV7611 HDMI input chip with CSI0?&amp;nbsp; I'm trying to get it working on an i.MX6S, and keep getting stuck at:&lt;/P&gt;&lt;BLOCKQUOTE&gt;
&lt;P&gt;ERROR: v4l2 capture: mxc_v4l_dqueue timeout enc_counter 0&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My physical interface almost exactly resembles the ADV7180/i.MX6 interface, with the addition of a DATA_ENABLE line. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've modified my device tree to include the MX6QDL_PAD_CSI0_DATA_EN__IPU1_CSI0_DATA_EN (pinctrl_ipu1_2) and I've based my driver on the ADV7180.c driver in the BSP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm positive that the ADV7611 is outputting an 8-bit BT656 720x480 (525i) signal, and I can verify that the pixelclk is running at about the right frequency.&amp;nbsp; HS, VS, DE, and PIXCLK are all enabled, and I believe the EAV/SAV are also enabled by default (these should not be needed though, right?).&amp;nbsp; I've tried a mix of HS/VS/DE/CLK polarities, but nothing seems to work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone had any luck interfacing an ADV7610/7611 to an i.MX6?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Aug 2014 21:32:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380068#M54746</guid>
      <dc:creator>allanmatthew</dc:creator>
      <dc:date>2014-08-25T21:32:06Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7610 CSI0 input</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380069#M54747</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Allan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;v4l2 capture is used for cameras, while&lt;/P&gt;&lt;P&gt;for&amp;nbsp; ADV7180 - like devices one needs to use mxc_v4l2_tvin.out, it&lt;/P&gt;&lt;P&gt;was specially created to test the adv7180 functionality, turning on the de-interlace function.&lt;/P&gt;&lt;P&gt;Pelase check below links&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/message/314760"&gt;Re: ADV7181 on IMX6Q board&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/docs/DOC-93633"&gt;De-interlace Capture Device&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/thread/324538"&gt;Can't capture data from adv7611 with CSI0 on MX6Q&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;chip&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Aug 2014 00:21:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380069#M54747</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2014-08-26T00:21:49Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7610 CSI0 input</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380070#M54748</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Chip-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the prompt reply.&amp;nbsp; I tried the mxc_v4l2_tvin.out but no dice, I see the same "&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt;ERROR: v4l2 capture: mxc_v4l_dqueue timeout enc_counter 0".&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've done a bit more testing, and here is what I know from the ADV7610 side:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.) HSYNC is active high&lt;/P&gt;&lt;P&gt;2.) VSYNC is active high&lt;/P&gt;&lt;P&gt;3.) DE is active high&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've checked with a scope and their traces appear (to me) to be correct, however they don't necessarily match the "gated mode" in the i.MX6 reference manual:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Screen Shot 2014-08-25 at 5.35.29 PM.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/44788i0142D27B57B02EE8/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screen Shot 2014-08-25 at 5.35.29 PM.png" alt="Screen Shot 2014-08-25 at 5.35.29 PM.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My VSYNC will stay high for the entirety of the frame, and the HSYNC stays high for the entirety of the line.&amp;nbsp; Thats normal operation in my experience, but does the i.MX6 require something different?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, there is almost no mention of the DATA_ENABLE line in the reference manual.&amp;nbsp; Should it be used?&amp;nbsp; How do I enable it, beyond setting the right pinctl in the DTS?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Lastly, what are the correct settings in the various IOCTLs of my driver to enable the HSYNC/VSYNC/DE modes?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Allan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Aug 2014 00:40:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380070#M54748</guid>
      <dc:creator>allanmatthew</dc:creator>
      <dc:date>2014-08-26T00:40:32Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7610 CSI0 input</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380071#M54749</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Allan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;actually suggested links answer some questions:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/message/314760"&gt;Re: ADV7181 on IMX6Q board&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for mxc_v4l2_tvin.out one needs to verify that device outputs &lt;SPAN style="background-color: #ffffff; font-family: 'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif;"&gt;EAV and SAV codes.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #ffffff; font-family: 'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif;"&gt;In BT656 interlaced mode the CSI will check the data bus for EAV and SAV, &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #ffffff; font-family: 'Helvetica Neue',Helvetica,Arial,'Lucida Grande',sans-serif;"&gt;it will only capture the video data after found the correct EAV and SAV.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If device outputs HSYNC/VSYNC, then one can use v4l2 capture, as for cameras.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;chip&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Aug 2014 04:29:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380071#M54749</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2014-08-26T04:29:05Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7610 CSI0 input</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380072#M54750</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;P&gt;Hi Chip-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Indeed, and I've tried both methods.  I can inject SAV EAV codes and try the tvin type, or leave them out and use the HSYNC/VSYNC with v4l2_capture but neither works, both give the same error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since I know the codes and sync pins are working, there must be something wrong in my i.mx6 configuration...  Could you explain what settings I need to make sure are set to get this running?  I would prefer to use the HSYNC/VSYNC.  Also, what do I need to do with the DE?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Allan&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Aug 2014 14:21:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380072#M54750</guid>
      <dc:creator>allanmatthew</dc:creator>
      <dc:date>2014-08-26T14:21:05Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7610 CSI0 input</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380073#M54751</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;OK, I seem to be able to get data now.&amp;nbsp; I had to do the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.) Make sure HSYNC and VSYNC were inverted polarity from the ADV7610&lt;/P&gt;&lt;P&gt;2.) Set a clock_curr value in my ioctl_g_ifparm() to !=0&lt;/P&gt;&lt;P&gt;3.) Set bt_sync_correct to 0 in ioctl_g_ifparm()&lt;/P&gt;&lt;P&gt;4.) set sen.pix.priv = 0 in my probe function&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm now able to get some data into a file using the mfw_v4lsrc gstreamer pipeline, but it is very noisy.&amp;nbsp; I took a scope grab of the HSYNC (purple) and VSYNC (green).&amp;nbsp; This does not match the reference manual diagram exactly in that the HSYNC is running when the VSYNC is high, but I can't figure out how to make that not happen.&amp;nbsp; The clock runs continuously and the data stays low during the blanking period.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="IMG_1115.JPG"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/16427iE8DB8508DF770A10/image-size/large?v=v2&amp;amp;px=999" role="button" title="IMG_1115.JPG" alt="IMG_1115.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Does it matter that the HSYNC continues to run during the VSYNC period?&amp;nbsp; Should the above waveforms work with the CSI0 input?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Allan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Aug 2014 19:22:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380073#M54751</guid>
      <dc:creator>allanmatthew</dc:creator>
      <dc:date>2014-08-26T19:22:15Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7610 CSI0 input</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380074#M54752</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Allan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;one can try not-gated mode (without HSYNC), timings are given in&lt;/P&gt;&lt;P&gt;sect.4.11.10.2.3 Non-Gated Clock Mode &lt;A href="http://cache.freescale.com/files/32bit/doc/data_sheet/IMX6DQCEC.pdf?fasp=1&amp;amp;WT_TYPE=Data%20Sheets&amp;amp;WT_VENDOR=FREESCALE&amp;amp;WT_FILE_FORMAT=pdf&amp;amp;WT_ASSET=Documentation&amp;amp;fileExt=.pdf"&gt;IMX6DQCEC&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;chip&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Aug 2014 02:03:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380074#M54752</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2014-08-27T02:03:03Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7610 CSI0 input</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380075#M54753</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think I've found why its not working, anyway.&amp;nbsp; I took a scope trace of an OV camera input from a BD board, shown here:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="tek00000.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/45598i2DA7C126FB8448DC/image-size/large?v=v2&amp;amp;px=999" role="button" title="tek00000.png" alt="tek00000.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;You can see that the HSYNC (light blue) is inactive for the entire blanking time, and does not run when the VSYNC is active.&amp;nbsp; This seems to jibe with the IMX6DQCEC:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Screen Shot 2014-08-26 at 9.46.29 PM.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/45659i96B6825050AA6626/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screen Shot 2014-08-26 at 9.46.29 PM.png" alt="Screen Shot 2014-08-26 at 9.46.29 PM.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So it looks like I'll have to try and get the HSYNC/VSYNC signals from my ADV7610 to match up&amp;nbsp; Unfortunately I'm not sure if this will be possible, as the ADV7610 relies mostly on the DATA_EN pin to specify if data is correct or not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there ANY WAY to make the DATA_EN pin work with the CSI0?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Allan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Aug 2014 16:17:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380075#M54753</guid>
      <dc:creator>allanmatthew</dc:creator>
      <dc:date>2014-08-27T16:17:40Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7610 CSI0 input</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380076#M54754</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;On i.MX6SDL side DATA_EN is configured using &lt;/P&gt;&lt;P&gt;CSI0_DATA_EN, Table 4-1. Pin Assignments &lt;A href="http://cache.freescale.com/files/32bit/doc/ref_manual/IMX6SDLRM.pdf?fasp=1&amp;amp;WT_TYPE=Reference%20Manuals&amp;amp;WT_VENDOR=FREESCALE&amp;amp;WT_FILE_FORMAT=pdf&amp;amp;WT_ASSET=Documentation&amp;amp;fileExt=.pdf"&gt;IMX6SDLRM&lt;/A&gt; &lt;/P&gt;&lt;P&gt;and bit CSI0_DATA_EN_POL,&amp;nbsp; register IPU_CSI0_SENS_CONF&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;~chip&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Aug 2014 00:08:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380076#M54754</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2014-08-28T00:08:27Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7610 CSI0 input</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380077#M54755</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Chip-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Actually, it turns out that turning OFF the DATA_EN seems to work a bit better.&amp;nbsp; I don't have a correct image yet, but I do have something.&amp;nbsp; There seems to be an offset in the video, like its starting to read lines in the VSYNC period when it should not be or something.&amp;nbsp; Is there a crop value or something in the v4l_capture that needs to be set?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Allan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Aug 2014 03:31:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380077#M54755</guid>
      <dc:creator>allanmatthew</dc:creator>
      <dc:date>2014-08-28T03:31:49Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7610 CSI0 input</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380078#M54756</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Allan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;from link below seems 7611 works in 12bit BT.1120 mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/thread/324538"&gt;Can't capture data from adv7611 with CSI0 on MX6Q&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ADV7610 also supports 8-/12-bit ITU-R BT.656 mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;chip&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Aug 2014 00:02:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380078#M54756</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2014-08-29T00:02:31Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7610 CSI0 input</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380079#M54757</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Chip-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yeah, I saw that.&amp;nbsp; Unfortunately I'm operating in 8-bit mode and don't have the ability to go to a 16-bit bus, but we need to support a 720p input.&amp;nbsp; We can't do that with the bt656 but should be able to do it with a simple gated parallel mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Allan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Aug 2014 01:16:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380079#M54757</guid>
      <dc:creator>allanmatthew</dc:creator>
      <dc:date>2014-08-29T01:16:28Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7610 CSI0 input</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380080#M54758</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Allan,&lt;/P&gt;&lt;P&gt;Not sure if you've solved this yet but our design is based on an i.mx6solo and includes both an ADV7181 and ADV7610. We only use one of these at a time so both are connected to CSI1 (we use CSI0 for a MIPI camara module) and we tri-state the output of the which ever one is not in use. We use BT.656 to bring in the data and have tested both chips in 8 and 16 bit width. The embedded clock mode has worked so well for us that we have actually dropped HSYNC, VSYNC and DAT_EN for our production board.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One thing that I had to mess with to get BT.656 working was the ADV7610's LLC delay. See IO Register 0x19 (LLC_DDL_EN). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here are the few changes I had to make to my adv7610 driver in order when switching between 8 and 16 bit modes:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In probe()&lt;/P&gt;&lt;P&gt;#ifdef ADV7610_16BIT&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; adv_data.v4l2_data.pix.pixelformat = V4L2_PIX_FMT_YUYV;&lt;/P&gt;&lt;P&gt;#else&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; adv_data.v4l2_data.pix.pixelformat = V4L2_PIX_FMT_UYVY;&lt;/P&gt;&lt;P&gt;#endif&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In init_ADV7610_regs:&lt;/P&gt;&lt;P&gt;#ifdef ADV7610_16BIT&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; { IO_ADDR, 0x03, 0x80 }, // Output format is 16 bit SDR ITU-656 Mode 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; { IO_ADDR, 0x19, 0x89 }, // LLC DLL phase, changed to improve setup/hold time&lt;/P&gt;&lt;P&gt;#else&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; { IO_ADDR, 0x03, 0x00 }, // Output format is 8 bit SDR ITU-656&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; { IO_ADDR, 0x19, 0xC3 }, // LLC DLL phase&lt;/P&gt;&lt;P&gt;#endif&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In ioctl_g_ifparm&lt;/P&gt;&lt;P&gt;#ifdef ADV7610_16BIT&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; p-&amp;gt;if_type = V4L2_IF_TYPE_BT1120;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; p-&amp;gt;u.bt1120.mode = V4L2_IF_TYPE_BT1120_MODE_BT_8BIT;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; p-&amp;gt;u.bt1120.clock_curr = (V4L2_DV_INTERLACED == adv_data.timings.bt.interlaced) ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0 : adv_data.timings.bt.pixelclock;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; p-&amp;gt;u.bt1120.nobt_hs_inv = 0;&amp;nbsp; // horizontal sync invert&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; p-&amp;gt;u.bt1120.nobt_vs_inv = 0;&amp;nbsp; // vertical sync invert&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; p-&amp;gt;u.bt1120.frame_start_on_rising_vs = 0; // VS rising indicates a start&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; // of a new frame&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; p-&amp;gt;u.bt1120.latch_clk_inv = 0;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; p-&amp;gt;u.bt1120.bt_sync_correct = 0;&lt;/P&gt;&lt;P&gt;#else&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; p-&amp;gt;if_type = V4L2_IF_TYPE_BT656;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; p-&amp;gt;u.bt656.mode = V4L2_IF_TYPE_BT656_MODE_BT_8BIT;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; p-&amp;gt;u.bt656.clock_curr = (V4L2_DV_INTERLACED == adv_data.timings.bt.interlaced) ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0 : adv_data.timings.bt.pixelclock;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; p-&amp;gt;u.bt656.nobt_hs_inv = 0;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; p-&amp;gt;u.bt656.nobt_vs_inv = 0;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; p-&amp;gt;u.bt656.latch_clk_inv = 0;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; p-&amp;gt;u.bt656.frame_start_on_rising_vs = 0;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; p-&amp;gt;u.bt656.bt_sync_correct = 0;&lt;/P&gt;&lt;P&gt;#endif&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Nov 2014 16:42:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380080#M54758</guid>
      <dc:creator>donfreiling</dc:creator>
      <dc:date>2014-11-03T16:42:00Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7610 CSI0 input</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380081#M54759</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Don-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks very much for your response.&amp;nbsp; I actually did get the ADV7610 working in BT656 with an 8-bit bus, but I'm looking to get it working in the 16-bit setup.&lt;/P&gt;&lt;P&gt;I've patched mxc_v4l2_capture.c and v4l2-int-device.h, updated my dtb, and included your suggestions in my adv7610.c.&amp;nbsp; I'm stuck at the dqueue timeout again, unfortunately.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I notice that you set&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12px; background-color: #f6f6f6;"&gt;p-&amp;gt;u.bt1120.mode = V4L2_IF_TYPE_BT1120_MODE_BT_8BIT;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12px; background-color: #f6f6f6;"&gt;in your 16-bit configuration, is there any reason that you did that instead of &lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12px; background-color: #f6f6f6;"&gt;V4L2_IF_TYPE_BT1120_MODE_BT_16BIT;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12px; background-color: #f6f6f6;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12px; background-color: #f6f6f6;"&gt;Also, in your physical interface, I'm assuming you're using CSI0_DATA02-&amp;gt;CSI0_DATA09 and CSI0_DATA12-&amp;gt;CSI0_DATA19.&amp;nbsp; In the i.MX6 datasheet, CSI0_DATA00, CSI_DATA01, CSI_DATA10 and CSI_DATA11 are listed as "0" instead of "-", so I'm wondering if you pull those pins low?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12px; background-color: #f6f6f6;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12px; background-color: #f6f6f6;"&gt;Lastly, to use the V4L2_IF_TYPE_BT1120 are you using patches from this post? &lt;A _jive_internal="true" class="loading" href="https://community.nxp.com/thread/295157" title="https://community.freescale.com/thread/295157"&gt;https://community.freescale.com/thread/295157&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12px; background-color: #f6f6f6;"&gt;I've incorporated what I believe are the relevant portions of mxc_v4l2_capture.c and v4l2-int-device.h, but I'm not sure if there is more thats needed to be done.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12px; background-color: #f6f6f6;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12px; background-color: #f6f6f6;"&gt;Thanks!&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12px; background-color: #f6f6f6;"&gt;-Allan&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 14 Dec 2014 02:27:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380081#M54759</guid>
      <dc:creator>allanmatthew</dc:creator>
      <dc:date>2014-12-14T02:27:15Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7610 CSI0 input</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380082#M54760</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Got it working actually!&amp;nbsp; I used the interface described in "&lt;A _jive_internal="true" data-containerid="2004" data-containertype="14" data-content-finding="Community" data-objectid="314211" data-objecttype="1" href="https://community.nxp.com/thread/314211" style="font-weight: inherit; font-style: inherit; font-family: inherit; color: #6a737b;"&gt;https://community.freescale.com/thread/314211&lt;/A&gt;" and used internal pulldowns to pull DATA0,1, 10 and 11 low.&amp;nbsp; Using the exisitng CCIR codes seemed to work as well.&amp;nbsp; Thanks!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Allan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Dec 2014 15:52:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380082#M54760</guid>
      <dc:creator>allanmatthew</dc:creator>
      <dc:date>2014-12-15T15:52:39Z</dc:date>
    </item>
    <item>
      <title>Re: ADV7610 CSI0 input</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380083#M54761</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Allan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am looking for iMX6Q CSI1 parallel interface with BT1120 interlace and I also have the dequeue timeout issue. Now I refer the link &lt;A href="https://community.nxp.com/message/408116"&gt;Re: 16bit BT1120 does not work on MX6Q&lt;/A&gt; , so I have these acts as below:&lt;/P&gt;&lt;P&gt;(1) mxc_v4l2_capture.c&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; csi_param.clk_mode = IPU_CSI_CLK_MODE_CCIR1120_INTERLACED_SDR&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; csi_param.data_width = IPU_CSI_DATA_WIDTH_8&lt;/P&gt;&lt;P&gt;(2) ipu_capture.c(for CCIR1120_INTERLACED_SDR or CCIR1120_INTERLACED_DDR)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ipu_csi_write(ipu, csi, 0xD07DF, CSI_CCIR_CODE_1);&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ipu_csi_write(ipu, csi, 0x40596, CSI_CCIR_CODE_2);&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ipu_csi_write(ipu, csi, 0xFF0000, CSI_CCIR_CODE_3);&lt;/P&gt;&lt;P&gt;(3) Pull DATA0, 1, 10, 11 to low by HW&lt;/P&gt;&lt;P&gt;(4) Connected CSI1_DATA02~09 to decoder "C" data and CSI1_DATA12~19 to decoder "Y" data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Did you mind to describe your settings actually that ioctl_g_ifparm(), values of CSI_CCIR_CODE_1~3 and clk_mode?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you pretty much.&lt;/P&gt;&lt;P&gt;Chirk&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Jun 2015 09:01:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/ADV7610-CSI0-input/m-p/380083#M54761</guid>
      <dc:creator>wuchirk</dc:creator>
      <dc:date>2015-06-30T09:01:48Z</dc:date>
    </item>
  </channel>
</rss>

