<?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>topic Ronbo panel broken after Yocto update in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Ronbo-panel-broken-after-Yocto-update/m-p/995194#M147694</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey guys,&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;We recently updated the Yocto version we use (from 4.9-rocko to 4.14-sumo) and now our display panel just shows a white screen. The driver we're using is identical and the relevant sections of the DTB are the same, the only reason we updated was to fix some issues we were having with the UUU tool. Are there any breaking changes in the drm/display subsystem I'm unaware of?&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;We're using the iMX8MQ-EVK board.&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;Oli&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 01 Nov 2019 13:32:24 GMT</pubDate>
    <dc:creator>oli1</dc:creator>
    <dc:date>2019-11-01T13:32:24Z</dc:date>
    <item>
      <title>Ronbo panel broken after Yocto update</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Ronbo-panel-broken-after-Yocto-update/m-p/995194#M147694</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey guys,&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;We recently updated the Yocto version we use (from 4.9-rocko to 4.14-sumo) and now our display panel just shows a white screen. The driver we're using is identical and the relevant sections of the DTB are the same, the only reason we updated was to fix some issues we were having with the UUU tool. Are there any breaking changes in the drm/display subsystem I'm unaware of?&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;We're using the iMX8MQ-EVK board.&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;Oli&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Nov 2019 13:32:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Ronbo-panel-broken-after-Yocto-update/m-p/995194#M147694</guid>
      <dc:creator>oli1</dc:creator>
      <dc:date>2019-11-01T13:32:24Z</dc:date>
    </item>
    <item>
      <title>Re: Ronbo panel broken after Yocto update</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Ronbo-panel-broken-after-Yocto-update/m-p/995195#M147695</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Oli&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;one can try to rebuild all image from scratch, use software from source.codeaurora.org/external/imx,&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;pay attention that uboot also should be changed v.2018.03 for L4.14:&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;A class="link-titled" href="https://source.codeaurora.org/external/imx/uboot-imx/tree/?h=imx_v2018.03_4.14.98_2.2.0" title="https://source.codeaurora.org/external/imx/uboot-imx/tree/?h=imx_v2018.03_4.14.98_2.2.0"&gt;uboot-imx - i.MX U-Boot&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Nov 2019 23:49:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Ronbo-panel-broken-after-Yocto-update/m-p/995195#M147695</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2019-11-01T23:49:17Z</dc:date>
    </item>
    <item>
      <title>Re: Ronbo panel broken after Yocto update</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Ronbo-panel-broken-after-Yocto-update/m-p/995196#M147696</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Igor,&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;Thanks for the swift reply.&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;I can confirm that we are using u-boot v2018.03 and kernel 4.14.98. I also attempted a full clean build. This did not fix our issue.&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;Oli&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 02 Nov 2019 16:12:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Ronbo-panel-broken-after-Yocto-update/m-p/995196#M147696</guid>
      <dc:creator>oli1</dc:creator>
      <dc:date>2019-11-02T16:12:44Z</dc:date>
    </item>
    <item>
      <title>Re: Ronbo panel broken after Yocto update</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Ronbo-panel-broken-after-Yocto-update/m-p/995197#M147697</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Oli&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;SPAN&gt;L4.14 added filtering unsupported frequencies in "int valid_clocks[]"&lt;BR /&gt;&lt;A class="link-titled" href="https://source.codeaurora.org/external/imx/linux-imx/tree/drivers/gpu/drm/bridge/nwl-dsi.c?h=imx_4.14.98_2.1.0" title="https://source.codeaurora.org/external/imx/linux-imx/tree/drivers/gpu/drm/bridge/nwl-dsi.c?h=imx_4.14.98_2.1.0"&gt;nwl-dsi.c\bridge\drm\gpu\drivers - linux-imx - i.MX Linux kernel&lt;/A&gt;&amp;nbsp;&lt;BR /&gt;It wasn't mentioned in kernel 4.9.88: &lt;/SPAN&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;SPAN&gt; &lt;A class="link-titled" href="https://source.codeaurora.org/external/imx/linux-imx/tree/drivers/gpu/drm/bridge/nwl-dsi.c?h=imx_4.9.88_2.0.0_ga" title="https://source.codeaurora.org/external/imx/linux-imx/tree/drivers/gpu/drm/bridge/nwl-dsi.c?h=imx_4.9.88_2.0.0_ga"&gt;nwl-dsi.c\bridge\drm\gpu\drivers - linux-imx - i.MX Linux kernel&lt;/A&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;SPAN&gt; One can try workarounds provided on&lt;/SPAN&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://community.nxp.com/thread/513899"&gt;https://community.nxp.com/thread/513899&lt;/A&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 03 Nov 2019 11:57:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Ronbo-panel-broken-after-Yocto-update/m-p/995197#M147697</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2019-11-03T11:57:31Z</dc:date>
    </item>
  </channel>
</rss>

