From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] arm: tegra20: implement early pmic rail configuration
Date: Mon, 24 Aug 2015 10:28:16 -0600 [thread overview]
Message-ID: <55DB4620.9090100@wwwdotorg.org> (raw)
In-Reply-To: <b2e60f83-aec3-4ff7-8d91-9ccc85cb52fa@email.android.com>
On 08/20/2015 05:06 PM, Marcel Ziswiler wrote:
> On 20 Aug 2015 22:00, Stephen Warren <swarren@wwwdotorg.org> wrote:
>
> > Does the CORE rail get adjusted by DVFS? Hopefully if it does, it is
> > never set so low that AVP operation at reset is impossible...
>
> Exactly.
>
> > > + udelay(1000);
> >
> > all the delays in this patch seem very large. What drove the choice of
> > the delay values?
>
> Three things: I2C transfers at that speed will take at least around some
> 3 to 4 hundred us to complete so we stay at the save side.
The I2C transfers should have already synchronously completed, so there
should be no need to wait for those. If that's not true, there's a
serious bug that needs to be fixed.
> Plus the T30
> equivalent file uses the exact same delays so it can't be that wrong. My
> testing also showed that setting it anywhere much lower will cause
> reliability issues.
OK, consistency with other code seems reasonable. I still think there's
little point in such long delays though, but that could be fixed later.
next prev parent reply other threads:[~2015-08-24 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 23:06 [U-Boot] [PATCH 1/3] arm: tegra20: implement early pmic rail configuration Marcel Ziswiler
2015-08-24 16:28 ` Stephen Warren [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-20 7:52 [U-Boot] [PATCH 0/3] arm: tegra20/colibri_t20: " Marcel Ziswiler
2015-08-20 7:52 ` [U-Boot] [PATCH 1/3] arm: tegra20: implement " Marcel Ziswiler
2015-08-20 20:01 ` 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=55DB4620.9090100@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