public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] am335x:Handle worst case scenario for Errata 1.0.24
Date: Mon, 22 Jul 2013 11:23:17 -0400	[thread overview]
Message-ID: <20130722152317.GC11722@bill-the-cat> (raw)
In-Reply-To: <51ED49D0.6030407@ti.com>

On Mon, Jul 22, 2013 at 08:33:44PM +0530, Lokesh Vutla wrote:
> On Monday 22 July 2013 08:12 PM, Tom Rini wrote:
> > From: Steve Kipisz <s-kipisz2@ti.com>
> > 
> > In Errata 1.0.24, if the board is running at OPP50 and has a warm reset,
> > the boot ROM sets the frequencies for OPP100. This patch attempts to
> > drop the frequencies back to OPP50 as soon as possible in the SPL. Then
> > later the voltages and frequencies up set higher.
> > 
> > Cc: Enric Balletbo i Serra <eballetbo@iseebcn.com>
> > Cc: Lars Poeschel <poeschel@lemonage.de>
> > Signed-off-by: Steve Kipisz <s-kipisz2@ti.com>
> > [trini: Adapt to current framework]
> > Signed-off-by: Tom Rini <trini@ti.com>
> Doesn't this patch gives a conflict with recent cleanup series 
> for Am33xx ?
> http://patchwork.ozlabs.org/patch/253831/

Yes, and in a non-trivial fashion since we need to be able to
give an initial configuration to the clock, and then change it again,
and I don't see how to do that with your cleanup.  In fact, the other
series I posted, for scaling up the MPU clock also won't work with your
cleanup.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20130722/31026eec/attachment.pgp>

  reply	other threads:[~2013-07-22 15:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22 14:42 [U-Boot] [PATCH] am335x:Handle worst case scenario for Errata 1.0.24 Tom Rini
2013-07-22 15:03 ` Lokesh Vutla
2013-07-22 15:23   ` Tom Rini [this message]
2013-07-23 18:52 ` Dan Murphy

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=20130722152317.GC11722@bill-the-cat \
    --to=trini@ti.com \
    --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