<?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: Assistance debugging DVI/I2C issue</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Assistance-debugging-DVI-I2C-issue/m-p/1637339#M204530</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;The iMX6 have &lt;SPAN&gt;The CONFIG_FB_MXS_SII902X option provides support for the Sii902x HDMI video driver and can be selected&lt;/SPAN&gt;&lt;BR role="presentation" /&gt;&lt;SPAN class=""&gt;with Device Drivers &amp;gt; Support for frame buffer devices &amp;gt; Si Image SII9022 &lt;SPAN class="highlight selected appended"&gt;DVI&lt;/SPAN&gt;/HDMI Interface Chip&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;and you can check the current driver of i2c on &lt;SPAN&gt;drivers/i2c/busses/imx-i2c.c&lt;/SPAN&gt; .&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
    <pubDate>Thu, 20 Apr 2023 14:47:51 GMT</pubDate>
    <dc:creator>Bio_TICFSL</dc:creator>
    <dc:date>2023-04-20T14:47:51Z</dc:date>
    <item>
      <title>Assistance debugging DVI/I2C issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Assistance-debugging-DVI-I2C-issue/m-p/1637295#M204525</link>
      <description>&lt;P&gt;We have a custom board using the i.MX6DL chip. Our board leverages the NXP base kernel provided with the Saber board, with updates to device trees and whatnot to fit our design.&lt;/P&gt;&lt;P&gt;Recently we've been having issues with communication loss between the display and the board, and we're trying to diagnose the issue. We use a DVI connection (communication over the DVI's I2C) to our display.&lt;/P&gt;&lt;P&gt;We've seen issues where the display isn't responding to touch events anymore and remains a "black screen". We are trying to track down if this is a display issues, or an issue with the DVI/I2C driver.&lt;/P&gt;&lt;P&gt;Would anyone have some hints or input as to what we can track/log to help determine the cause of this issue? I'm hoping there is something in the FB or mxc_hdmi that could simply be enabled, but I'm not opposed to making minor code changes if need be.&lt;/P&gt;</description>
      <pubDate>Thu, 20 Apr 2023 13:06:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Assistance-debugging-DVI-I2C-issue/m-p/1637295#M204525</guid>
      <dc:creator>michaelworster</dc:creator>
      <dc:date>2023-04-20T13:06:38Z</dc:date>
    </item>
    <item>
      <title>Re: Assistance debugging DVI/I2C issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Assistance-debugging-DVI-I2C-issue/m-p/1637339#M204530</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;The iMX6 have &lt;SPAN&gt;The CONFIG_FB_MXS_SII902X option provides support for the Sii902x HDMI video driver and can be selected&lt;/SPAN&gt;&lt;BR role="presentation" /&gt;&lt;SPAN class=""&gt;with Device Drivers &amp;gt; Support for frame buffer devices &amp;gt; Si Image SII9022 &lt;SPAN class="highlight selected appended"&gt;DVI&lt;/SPAN&gt;/HDMI Interface Chip&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;and you can check the current driver of i2c on &lt;SPAN&gt;drivers/i2c/busses/imx-i2c.c&lt;/SPAN&gt; .&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Thu, 20 Apr 2023 14:47:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Assistance-debugging-DVI-I2C-issue/m-p/1637339#M204530</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2023-04-20T14:47:51Z</dc:date>
    </item>
  </channel>
</rss>

