From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fdt_support: Use CONFIG_NR_DRAM_BANKS if defined
Date: Tue, 30 Apr 2013 17:14:16 -0400 [thread overview]
Message-ID: <51803428.1070507@ti.com> (raw)
In-Reply-To: <CAD=FV=XSfCORuiYVtZmPKBwM+xZ3=Q0G+DYO2GQDh+v6eXwgLw@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/30/2013 04:49 PM, Doug Anderson wrote:
> Tom,
>
> On Tue, Apr 30, 2013 at 1:35 PM, Tom Rini <trini@ti.com> wrote:
>> And I guess having this knowledge correct for the kernel is
>> useful in other contexts like when we want to power down some
>> banks of memory but not others? I mean, there's "lots" of
>> platforms that lie and say 1 bank since we require contiguous
>> mapping. Thanks!
>
> Thanks for the review!
>
> At the moment I'm _not_ convinced that there's a good reason to
> specify 8 banks. We appear to have lied and said 1 bank on
> exynos5250-snow (ARM Chromebook) and I don't know of any bad side
> effects.
>
> The code I'm looking at right now indicates 8 banks. We need to
> track down why someone did that but it doesn't seem totally crazy
> to allow specifying the proper number of banks so I figured I'd
> send this patch up.
>
> If you prefer, we can leave this patch hanging until we actually
> track down if specifying 8 banks was really needed.
Yes please, lets hold. Thanks!
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJRgDQoAAoJENk4IS6UOR1WztkP+QEs7IvExh9Dq0AHrj81wQ9Q
Ml29BZGsdJ5mLIt6jhJ7HSr310cu3FODgbVuNt01Aj0Q2X+C1mCRYqhoIDwfcSUJ
EWVhUaphlmiBd2OrMH+3HPUwQ+kFfjt5LNFuXwRei0tgz+sy6NTQ+QZFuZ9FiBJD
UKtavOsvd3XipdklU5UEGoBj6OJxU6hBOyehZ3Cckwgfeg0L/1uV07Vd8kSFFc5e
xoWXN7O+QkdlNkWeruxPF7uq1MeM2VusCuvGWK4srrED+WSAKFhqsi7t3N66iNny
lXDhYPtuSr5HF5xua4kwWdbM/GneVd5m0p979TvIwvwhM1bMr00mfIoH9HEjzNF6
Bvq0wcCwIEZLwBFNNpn9X9zIzwXIgUKbMqjHQXiuizY8LROdXXnkg53k9o2pDO5+
uGO8cKZMXJYEU4zW+wbSlI/Cz7WoylsXhSBPfF5gkRSIxKtYmcS/iQn/nKMgebVO
TaGx76/r8xOvA5WY+wCs7HMEJip5UU00rG7MvjokwxOSUf/2rVHiDWl0MEAlh7M4
4KAMzb61P/fUiXrZv5K9Z6sgPmGynjItKnw0UigTWKG6DvRy0HuOlF//O8qAuWKH
+eyjg2F24pS9cGRMni3M9cUBH1W6secIpZkqs3goxeNVZyfb29kswolymfbcU4GC
zXmnz8gBTLDKGtTzLlXC
=s42z
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-04-30 21:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 20:22 [U-Boot] [PATCH] fdt_support: Use CONFIG_NR_DRAM_BANKS if defined Doug Anderson
2013-04-30 20:35 ` Tom Rini
2013-04-30 20:49 ` Doug Anderson
2013-04-30 21:14 ` Tom Rini [this message]
2013-05-15 15:58 ` Vadim Bendebury
2013-05-15 16:46 ` Tom Rini
2013-05-15 16:51 ` Doug Anderson
2013-05-17 16:26 ` Doug Anderson
2013-05-17 16:40 ` Tom Rini
2013-05-17 16:48 ` Doug Anderson
2013-05-17 16:52 ` Tom Rini
2013-05-17 16:59 ` Doug Anderson
2013-05-17 18:05 ` Tom Rini
2013-05-17 18:13 ` Jerry Van Baren
2013-05-22 14:59 ` [U-Boot] " Tom Rini
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=51803428.1070507@ti.com \
--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.