From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] rockchip: sdram: Fix register layout for Linux
Date: Fri, 15 Jul 2016 13:14:04 -0400 [thread overview]
Message-ID: <20160715171404.GS7260@bill-the-cat> (raw)
In-Reply-To: <20160715163323.2475-1-john@metanate.com>
On Fri, Jul 15, 2016 at 05:33:23PM +0100, John Keeping wrote:
> The ChromeOS kernel reads the RAM settings from PMU_SYS_REG2 and expects
> the bootloader to store the necessary information there. We're using
> the same register to pass the same information between the SPL and
> U-Boot but in a slightly different format.
>
> Change this to use the format expected by the Linux DMC driver so that
> the system doesn't hang in Linux by misconfiguring the RAM.
>
> This is almost the same as commit b5788dc ("rockchip: rk3288: correct
> sdram setting") which was reverted in commit b525556 ("Revert "rockchip:
> rk3288: correct sdram setting"") but parenthese have been added to apply
> the mask correctly when reading the "bw" setting and a couple of minor
> style issues have been fixed to keep check_patch.pl happy.
>
> Signed-off-by: John Keeping <john@metanate.com>
>
Thanks!
Reviewed-by: Tom Rini <trini@konsulko.com>
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160715/18cc3eb7/attachment.sig>
next prev parent reply other threads:[~2016-07-15 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 15:24 [U-Boot] [PATCH] Revert "Revert "rockchip: rk3288: correct sdram setting"" John Keeping
2016-07-15 16:16 ` Tom Rini
2016-07-15 16:33 ` [U-Boot] [PATCH v2] rockchip: sdram: Fix register layout for Linux John Keeping
2016-07-15 17:14 ` Tom Rini [this message]
2016-07-17 14:13 ` Simon Glass
2016-07-18 12:20 ` Simon Glass
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=20160715171404.GS7260@bill-the-cat \
--to=trini@konsulko.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