From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/5] ARM: OMAP5: clock: Add the prcm register changes required for ES2.0
Date: Thu, 31 Jan 2013 12:20:10 -0500 [thread overview]
Message-ID: <20130131172010.GF30932@bill-the-cat> (raw)
In-Reply-To: <1359612150-20076-3-git-send-email-r.sricharan@ti.com>
On Thu, Jan 31, 2013 at 11:32:27AM +0530, R Sricharan wrote:
> PRCM register addresses are changed from ES1.0 to ES2.0 due to
> PER power domain getting moved to CORE power domain.
>
> So adding the nessecary register changes for the same.
>
> Signed-off-by: R Sricharan <r.sricharan@ti.com>
Reviewed-by: Tom Rini <trini@ti.com>
--
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/20130131/61f9f9b2/attachment.pgp>
next prev parent reply other threads:[~2013-01-31 17:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 6:02 [U-Boot] [PATCH 0/5] ARM: OMAP5: Add support for OMAP543x ES2.0 Socs R Sricharan
2013-01-31 6:02 ` [U-Boot] [PATCH 1/5] ARM: OMAP5: Add silicon id support for ES2.0 revision R Sricharan
2013-01-31 17:19 ` Tom Rini
2013-01-31 6:02 ` [U-Boot] [PATCH 2/5] ARM: OMAP5: clock: Add the prcm register changes required for ES2.0 R Sricharan
2013-01-31 17:20 ` Tom Rini [this message]
2013-01-31 6:02 ` [U-Boot] [PATCH 3/5] ARM: OMAP5: clocks: Add OPP settings required for OMAP543X ES2.0 soc R Sricharan
2013-01-31 17:20 ` Tom Rini
2013-01-31 6:02 ` [U-Boot] [PATCH 4/5] ARM: OMAP5: Add DDR changes required for OMAP543X ES2.0 SOCs R Sricharan
2013-01-31 17:20 ` Tom Rini
2013-01-31 6:02 ` [U-Boot] [PATCH 5/5] ARM: OMAP5: srcomp: enable slew rate compensation cells after powerup R Sricharan
2013-01-31 17:20 ` Tom Rini
2013-02-01 8:15 ` R Sricharan
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=20130131172010.GF30932@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.