<?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 Re: Value Change after Suspend to RAM in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Value-Change-after-Suspend-to-RAM/m-p/636632#M96941</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Deepanraj&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;seems this is common linux problem as described on&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://www.kernel.org/doc/Documentation/timers/timekeeping.txt" title="https://www.kernel.org/doc/Documentation/timers/timekeeping.txt"&gt;https://www.kernel.org/doc/Documentation/timers/timekeeping.txt&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, 15 Feb 2017 23:12:35 GMT</pubDate>
    <dc:creator>igorpadykov</dc:creator>
    <dc:date>2017-02-15T23:12:35Z</dc:date>
    <item>
      <title>Value Change after Suspend to RAM</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Value-Change-after-Suspend-to-RAM/m-p/636631#M96940</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our is a custom board based on iMx6 and we are using Linux 3.10.53 kernel.The loops per jiffy value which is calibrated in kernel is getting change once the system resumes from suspend to ram, Because of which the delay which we have programmed in the driver gets changed and there is instability in the interface corresponding to the driver.What could be the reason for the change of loops per jiffy value after resuming from suspend to RAM.Please reply as soon as possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Deepanraj.A&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Feb 2017 07:46:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Value-Change-after-Suspend-to-RAM/m-p/636631#M96940</guid>
      <dc:creator>deepanrajanbara</dc:creator>
      <dc:date>2017-02-15T07:46:06Z</dc:date>
    </item>
    <item>
      <title>Re: Value Change after Suspend to RAM</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Value-Change-after-Suspend-to-RAM/m-p/636632#M96941</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Deepanraj&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;seems this is common linux problem as described on&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://www.kernel.org/doc/Documentation/timers/timekeeping.txt" title="https://www.kernel.org/doc/Documentation/timers/timekeeping.txt"&gt;https://www.kernel.org/doc/Documentation/timers/timekeeping.txt&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, 15 Feb 2017 23:12:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Value-Change-after-Suspend-to-RAM/m-p/636632#M96941</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2017-02-15T23:12:35Z</dc:date>
    </item>
  </channel>
</rss>

