<?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のトピックBug in busfreq driver</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Bug-in-busfreq-driver/m-p/768107#M119313</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;On our custom board (imx6d + lpddr2, pop-package) we faced with kernel panic after some tome of work. After some reserces I detected that busfreq causes this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The thing is that before change ddr frequancy, driver (in function "update_lpddr2_freq_smp") compares new freq value with current and if they equals it returns 0. After that driver configures clock parents and if frequancies not configured before it (because&amp;nbsp;&lt;SPAN&gt;update_lpddr2_freq_smp doesn't actually work&lt;/SPAN&gt;) system crashes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some times in "&lt;SPAN&gt;update_lpddr2_freq_smp" curr_ddr_rate doesn't changes after previous call. Make it volatile not help. If not check&amp;nbsp;&lt;SPAN&gt;curr_ddr_rate - all works perfect.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;Why&amp;nbsp;&lt;SPAN&gt;curr_ddr_rate doesn't change sometimes? And do we need&amp;nbsp;&lt;SPAN&gt;curr_ddr_rate if all other work doings unconditionally?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 25 Apr 2018 13:47:12 GMT</pubDate>
    <dc:creator>maximkuk</dc:creator>
    <dc:date>2018-04-25T13:47:12Z</dc:date>
    <item>
      <title>Bug in busfreq driver</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Bug-in-busfreq-driver/m-p/768107#M119313</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;On our custom board (imx6d + lpddr2, pop-package) we faced with kernel panic after some tome of work. After some reserces I detected that busfreq causes this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The thing is that before change ddr frequancy, driver (in function "update_lpddr2_freq_smp") compares new freq value with current and if they equals it returns 0. After that driver configures clock parents and if frequancies not configured before it (because&amp;nbsp;&lt;SPAN&gt;update_lpddr2_freq_smp doesn't actually work&lt;/SPAN&gt;) system crashes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some times in "&lt;SPAN&gt;update_lpddr2_freq_smp" curr_ddr_rate doesn't changes after previous call. Make it volatile not help. If not check&amp;nbsp;&lt;SPAN&gt;curr_ddr_rate - all works perfect.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;Why&amp;nbsp;&lt;SPAN&gt;curr_ddr_rate doesn't change sometimes? And do we need&amp;nbsp;&lt;SPAN&gt;curr_ddr_rate if all other work doings unconditionally?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Apr 2018 13:47:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Bug-in-busfreq-driver/m-p/768107#M119313</guid>
      <dc:creator>maximkuk</dc:creator>
      <dc:date>2018-04-25T13:47:12Z</dc:date>
    </item>
    <item>
      <title>Re: Bug in busfreq driver</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Bug-in-busfreq-driver/m-p/768108#M119314</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Maxim&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;please try ddr test and use nxp bsps described on below link&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/docs/DOC-105652"&gt;i.MX6/7 DDR Stress Test Tool V2.80&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://www.nxp.com/support/developer-resources/run-time-software/i.mx-developer-resources/i.mx-software-and-development-tool-resources:IMX_SW" title="https://www.nxp.com/support/developer-resources/run-time-software/i.mx-developer-resources/i.mx-software-and-development-tool-resources:IMX_SW"&gt;i.MX Software|NXP&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://source.codeaurora.org/external/imx/linux-imx/tree/?h=imx_4.1.15_2.0.0_ga" title="https://source.codeaurora.org/external/imx/linux-imx/tree/?h=imx_4.1.15_2.0.0_ga"&gt;https://source.codeaurora.org/external/imx/linux-imx/tree/?h=imx_4.1.15_2.0.0_ga&lt;/A&gt;&lt;A class="link-titled" href="https://source.codeaurora.org/external/imx/linux-imx/tree/?h=scm-imx_4.1.15_2.0.0_ga" title="https://source.codeaurora.org/external/imx/linux-imx/tree/?h=scm-imx_4.1.15_2.0.0_ga"&gt;linux-imx - i.MX Linux kernel&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&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>Wed, 25 Apr 2018 23:31:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Bug-in-busfreq-driver/m-p/768108#M119314</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2018-04-25T23:31:57Z</dc:date>
    </item>
    <item>
      <title>Re: Bug in busfreq driver</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Bug-in-busfreq-driver/m-p/768109#M119315</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for answer and useful links!&lt;/P&gt;&lt;P&gt;It looks like I found the same solution - update curr_ddr_rate before changing ddr frequency.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Apr 2018 07:04:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Bug-in-busfreq-driver/m-p/768109#M119315</guid>
      <dc:creator>maximkuk</dc:creator>
      <dc:date>2018-04-26T07:04:05Z</dc:date>
    </item>
  </channel>
</rss>

