From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/3] arm: tegra20/colibri_t20: early pmic rail configuration
Date: Mon, 24 Aug 2015 10:26:52 -0600 [thread overview]
Message-ID: <55DB45CC.1060103@wwwdotorg.org> (raw)
In-Reply-To: <d4095d0b-55bd-4e39-9f54-9a26067c2427@email.android.com>
On 08/20/2015 04:59 PM, Marcel Ziswiler wrote:
> On 20 Aug 2015 21:58, Stephen Warren <swarren@wwwdotorg.org> wrote:
>
> > Is there any guarantee that the voltage levels are high enough for the
> > AVP to run correctly before the CORE rail is adjusted? It sounds to me
> > like a HW design issue; the SoC reset output should reset the PMIC too.
>
> If by guarantee you mean whether it is impossible by software to
> completely screw the rail configuration no there is no such guarantee.
> But even on T30 where usually some PMIC GPIOs are used to switch to a
> sane default software could mess up the configuration of that as well.
> To prevent any of that I guess a higher level of trusted computing stuff
> would be required. At the end we just have to assume that regular DVFS
> operation should never leave it in a completely unbootable state.
That almost sounds like there's no need for this patch/series then,
since we're assuming that SW won't leave the HW in a bad state. If SW
can leave HW in a bad state, the only choice is to fix the issue in HW.
However, perhaps you mean there are some states that are worse than
others; we assume that the rails required for the AVP are always in a
good state but the rails required for the CPU/CCPLEX may not be?
next prev parent reply other threads:[~2015-08-24 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 22:59 [U-Boot] [PATCH 0/3] arm: tegra20/colibri_t20: early pmic rail configuration Marcel Ziswiler
2015-08-24 16:26 ` Stephen Warren [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-24 22:19 Marcel Ziswiler
2015-08-20 7:52 Marcel Ziswiler
2015-08-20 19:59 ` Stephen Warren
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=55DB45CC.1060103@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/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