<?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: Possible bug in mxs-regulator</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Possible-bug-in-mxs-regulator/m-p/333876#M45273</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Stefan! Thanks for the posting!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you explain-me how I can correct the code portion?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;Christian&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 23 Sep 2014 22:29:17 GMT</pubDate>
    <dc:creator>chrdcv</dc:creator>
    <dc:date>2014-09-23T22:29:17Z</dc:date>
    <item>
      <title>Possible bug in mxs-regulator</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Possible-bug-in-mxs-regulator/m-p/333874#M45271</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think i've found a bug in the current mxs-regulator implementation ( imx_2.6.35_maintain ).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the file &lt;A href="http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/tree/?h=imx_2.6.35_maintain" rel="nofollow noopener noreferrer" target="_blank"&gt;root&lt;/A&gt;/&lt;A href="http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/tree/arch?h=imx_2.6.35_maintain" rel="nofollow noopener noreferrer" target="_blank"&gt;arch&lt;/A&gt;/&lt;A href="http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/tree/arch/arm?h=imx_2.6.35_maintain" rel="nofollow noopener noreferrer" target="_blank"&gt;arm&lt;/A&gt;/&lt;A href="http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/tree/arch/arm/mach-mx28?h=imx_2.6.35_maintain" rel="nofollow noopener noreferrer" target="_blank"&gt;mach-mx28&lt;/A&gt;/&lt;A href="http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/tree/arch/arm/mach-mx28/power.c?h=imx_2.6.35_maintain" rel="nofollow noopener noreferrer" target="_blank"&gt;power.c&lt;/A&gt; the mode handling is only correct for vddio. The current implementation uses bit 17 for all regulators (vddio, vdda, vddd) to get and set regulator mode. But that's wrong, according to the reference manual DISABLE_STEPPING is different for each regulator.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __default_attr="c++" __jive_macro_name="code" class="jive_text_macro _jivemacro_uid_14112163792154332 jive_macro_code" jivemacro_uid="_14112163792154332" modifiedtitle="true"&gt;
&lt;P&gt;&lt;CODE&gt;static int set_mode(struct mxs_regulator *sreg, int mode)
{
 int ret = 0;
 u32 val;

 switch (mode) {
 case REGULATOR_MODE_FAST:
 val = __raw_readl(sreg-&amp;gt;rdata-&amp;gt;control_reg);
 __raw_writel(val | (1 &amp;lt;&amp;lt; &lt;SPAN style="color: #ff0000;"&gt;17)&lt;/SPAN&gt;, sreg-&amp;gt;rdata-&amp;gt;control_reg);
 break;

 case REGULATOR_MODE_NORMAL:
 val = __raw_readl(sreg-&amp;gt;rdata-&amp;gt;control_reg);
 __raw_writel(val &amp;amp; ~(1&amp;lt;&amp;lt;&lt;SPAN style="color: #ff0000;"&gt;17&lt;/SPAN&gt;), sreg-&amp;gt;rdata-&amp;gt;control_reg);
 break;

 default:
 ret = -EINVAL;
 break;
 }
 return ret;
}

static int get_mode(struct mxs_regulator *sreg)
{
 u32 val = __raw_readl(sreg-&amp;gt;rdata-&amp;gt;control_reg) &amp;amp; (1 &amp;lt;&amp;lt; &lt;SPAN style="color: #ff0000;"&gt;17&lt;/SPAN&gt;);

 return val ? REGULATOR_MODE_FAST : REGULATOR_MODE_NORMAL;
}&lt;/CODE&gt;&lt;/P&gt;
&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone confirm?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 20 Sep 2014 12:42:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Possible-bug-in-mxs-regulator/m-p/333874#M45271</guid>
      <dc:creator>lategoodbye</dc:creator>
      <dc:date>2014-09-20T12:42:38Z</dc:date>
    </item>
    <item>
      <title>Re: Possible bug in mxs-regulator</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Possible-bug-in-mxs-regulator/m-p/333875#M45272</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Stefan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;yes your finding is true, i.MX28 DISABLE_STEPPING bit &lt;/P&gt;&lt;P&gt;has different position for regulators.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;igor&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>Mon, 22 Sep 2014 01:55:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Possible-bug-in-mxs-regulator/m-p/333875#M45272</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2014-09-22T01:55:47Z</dc:date>
    </item>
    <item>
      <title>Re: Possible bug in mxs-regulator</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Possible-bug-in-mxs-regulator/m-p/333876#M45273</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Stefan! Thanks for the posting!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you explain-me how I can correct the code portion?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;Christian&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Sep 2014 22:29:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Possible-bug-in-mxs-regulator/m-p/333876#M45273</guid>
      <dc:creator>chrdcv</dc:creator>
      <dc:date>2014-09-23T22:29:17Z</dc:date>
    </item>
    <item>
      <title>Re: Re: Possible bug in mxs-regulator</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Possible-bug-in-mxs-regulator/m-p/333877#M45274</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Christian,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for sure. Currently i'm porting the mxs-regulator for mainline. Here is the bugfix for my porting:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://github.com/lategoodbye/mxs-regulator/commit/19ec59c871afd7666e40b4bd2209b7ede7ebf1d1"&gt;https://github.com/lategoodbye/mxs-regulator/commit/19ec59c871afd7666e40b4bd2209b7ede7ebf1d1&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;May be, you can adapt it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Stefan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Sep 2014 06:52:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Possible-bug-in-mxs-regulator/m-p/333877#M45274</guid>
      <dc:creator>lategoodbye</dc:creator>
      <dc:date>2014-09-24T06:52:38Z</dc:date>
    </item>
    <item>
      <title>Re: Re: Possible bug in mxs-regulator</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Possible-bug-in-mxs-regulator/m-p/333878#M45275</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Stefan! I will try patches my files and see what happens!&lt;/P&gt;&lt;P&gt;Could you please see my post about troubles into the IMX287 PMU? &lt;A _jive_internal="true" class="loading" href="https://community.nxp.com/thread/331410" title="https://community.freescale.com/thread/331410"&gt;https://community.freescale.com/thread/331410&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;Christian&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Sep 2014 16:10:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Possible-bug-in-mxs-regulator/m-p/333878#M45275</guid>
      <dc:creator>chrdcv</dc:creator>
      <dc:date>2014-09-24T16:10:47Z</dc:date>
    </item>
  </channel>
</rss>

