From: leonard.crestez@nxp.com (Leonard Crestez)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: imx6sx-sdb: Remove cpufreq OPP override
Date: Tue, 25 Apr 2017 20:23:24 +0300 [thread overview]
Message-ID: <1493141004.3557.8.camel@nxp.com> (raw)
In-Reply-To: <CAOMZO5CKUsEr1yf5RrsPLipNtLC_6sK0dPjT2M-eN-uo8hEbrQ@mail.gmail.com>
On Tue, 2017-04-25 at 14:02 -0300, Fabio Estevam wrote:
> On Tue, Apr 25, 2017 at 2:02 PM, Fabio Estevam <festevam@gmail.com> wrote:
> >
> > Hi Leonard,
> >
> > On Tue, Apr 25, 2017 at 1:57 PM, Leonard Crestez
> > <leonard.crestez@nxp.com> wrote:
> > >
> > > The board file for imx6sx-dbg overrides cpufreq operating points to use
> > > higher voltages. This is done because the board has a shared rail for
> > > VDD_ARM_IN and VDD_SOC_IN and when using LDO bypass the shared voltage
> > > needs to be a value suitable for both ARM and SOC.
> > >
> > > This was introduced in:
> > >
> > > commit 54183bd7f766 ("ARM: imx6sx-sdb: add revb board and make it default")
> > >
> > > This only only applies to LDO bypass mode, a feature not present in
> > > upstream. When LDOs are enabled the effect is to use higher voltages than
> > > necesarry for no good reason.
> > >
> > > Setting these higher voltages can make some boards fail to boot with ugly
> > > semi-random crashes, reminiscent of memory corruption. These failures
> > > happen the first time the lowest idle state is used. Remove the OPP
> > > override in order to fix those crashes.
> > >
> > > Signed-off-by: Leonard Crestez <leonard.crestez@nxp.com>
> > >
> > > ---
> > > It's not clear exactly why the crashes happen. Perhaps waking up from idle
> > > draws more power than is available? Removing this override is a correct
> > > change anyway so maybe there is no need to investigate deeper.
> > Marek just sent a similar one a few minutes ago:
> > http://lists.infradead.org/pipermail/linux-arm-kernel/2017-April/503230.html
> Forgot to add Marek.
Wow, that was literally 15 minutes before my patch. In my defense I did
search the archives before starting to format the patch but it had not
arrived yet.
Anyway, that version also sets the supply for reg_arm and reg_soc. It
is not necessary for fixing the crash I'm seeing but is good because it
will result in the minimum voltage on VDD_ARM_SOC_IN rather than a fix
1375mv. I tested Marek's patch and it works fine on my rev B board
(which otherwise fails to boot upstream).
--?
Regards,
Leonard
next prev parent reply other threads:[~2017-04-25 17:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 16:57 [PATCH] ARM: dts: imx6sx-sdb: Remove cpufreq OPP override Leonard Crestez
2017-04-25 17:02 ` Fabio Estevam
2017-04-25 17:02 ` Fabio Estevam
2017-04-25 17:23 ` Leonard Crestez [this message]
2017-04-25 17:26 ` Fabio Estevam
2017-04-25 17:28 ` Marek Vasut
2017-05-03 13:57 ` Shawn Guo
2017-05-03 14:26 ` Marek Vasut
2017-05-03 14:32 ` Marek Vasut
2017-05-03 14:41 ` Shawn Guo
2017-05-03 14:51 ` Marek Vasut
2017-05-03 14:58 ` Leonard Crestez
2017-05-03 15:59 ` Marek Vasut
2017-05-03 17:58 ` Leonard Crestez
2017-05-03 19:33 ` Marek Vasut
2017-05-04 9:42 ` Leonard Crestez
2017-05-04 10:06 ` Marek Vasut
2017-05-04 12:44 ` Shawn Guo
2017-05-04 13:08 ` Marek Vasut
2017-05-04 13:41 ` Shawn Guo
2017-05-04 14:34 ` Marek Vasut
2017-05-05 1:18 ` Shawn Guo
2017-05-05 10:11 ` Leonard Crestez
2017-04-27 1:17 ` Peter Chen
2017-05-04 11:43 ` Shawn Guo
2017-05-04 11:46 ` Fabio Estevam
2017-05-04 12:50 ` Shawn Guo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1493141004.3557.8.camel@nxp.com \
--to=leonard.crestez@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).