From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 04/11] fdt: Add device tree memory bindings
Date: Mon, 27 Oct 2014 10:24:11 -0400 [thread overview]
Message-ID: <20141027142411.GV25506@bill-the-cat> (raw)
In-Reply-To: <CAPnjgZ1rw7UyGbhqFzJp3+Qj7jPxTMQeAjhKsfuuj5-_6CjLDQ@mail.gmail.com>
On Fri, Oct 24, 2014 at 02:04:00PM -0600, Simon Glass wrote:
> Hi Tom,
>
> On 24 October 2014 12:49, Tom Rini <trini@ti.com> wrote:
> > On Thu, Oct 23, 2014 at 06:58:50PM -0600, Simon Glass wrote:
> >
> >> From: Michael Pratt <mpratt@chromium.org>
> >>
> >> Support a default memory bank, specified in reg, as well as
> >> board-specific memory banks in subtree board-id nodes.
> >>
> >> This allows memory information to be provided in the device tree,
> >> rather than hard-coded in, which will make it simpler to handle
> >> similar devices with different memory banks, as the board-id values
> >> or masks can be used to match devices.
> > [snip]
> >> +++ b/doc/device-tree-bindings/memory/memory.txt
> >> @@ -0,0 +1,67 @@
> >> +* Memory binding
> >> +
> >> +The memory binding for U-Boot is as in the ePAPR with the following additions:
> >
> > I am wary of being different from ePAPR / Linux Kernel. What do we need
> > this for / when do we use it?
>
> This extends the existing binding. It allows the location and size of
> memory to be set by a board ID. Unfortunately on sopme hardware you
> get a hang if you try to access memory that doesn't exist, so this
> allows the range of available memory to be defined - or at least the
> maximum bound since we still probe the memory size within that range.
>
> This feature is used on several Exynos Chromebooks.
So that you can use the same DT on several disjoint boards? How does
this work with the kernel, does U-Boot then pass along only the correct
map? Patches to the kernel to also deal with this?
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20141027/b8e1029d/attachment.pgp>
next prev parent reply other threads:[~2014-10-27 14:24 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 0:58 [U-Boot] [PATCH v2 01/11] fdt: Allow ft_board_setup() to report failure Simon Glass
2014-10-24 0:58 ` [U-Boot] [PATCH v2 02/11] fdt: Report failure of ft_board_setup() Simon Glass
2014-10-24 15:15 ` Anatolij Gustschin
2014-10-24 18:05 ` Tom Rini
2014-11-21 3:24 ` Simon Glass
2014-10-24 0:58 ` [U-Boot] [PATCH v2 03/11] fdt: Export the fdt_find_or_add_subnode() function Simon Glass
2014-10-24 16:48 ` Anatolij Gustschin
2014-10-24 18:05 ` Tom Rini
2014-11-21 3:24 ` Simon Glass
2014-10-24 0:58 ` [U-Boot] [PATCH v2 04/11] fdt: Add device tree memory bindings Simon Glass
2014-10-24 18:49 ` Tom Rini
2014-10-24 20:04 ` Simon Glass
2014-10-27 14:24 ` Tom Rini [this message]
2014-10-27 18:50 ` Simon Glass
2014-11-12 15:13 ` Simon Glass
2014-11-12 21:42 ` Tom Rini
2014-11-12 22:14 ` Simon Glass
2014-11-20 14:37 ` Tom Rini
2014-11-20 17:42 ` Simon Glass
2014-12-10 5:31 ` Simon Glass
2014-10-24 0:58 ` [U-Boot] [PATCH v2 05/11] fdt: Use the correct return types for fdtdec_decode_region() Simon Glass
2014-10-24 18:07 ` Tom Rini
2014-11-21 3:25 ` Simon Glass
2014-10-24 0:58 ` [U-Boot] [PATCH v2 06/11] fdt: Enhance flashmap function to deal with region properties Simon Glass
2014-10-24 18:08 ` Tom Rini
2014-11-21 3:25 ` Simon Glass
2014-10-24 0:58 ` [U-Boot] [PATCH v2 07/11] fdt: Tidy up error handling in image_setup_libfdt() Simon Glass
2014-10-24 18:09 ` Tom Rini
2014-11-21 3:25 ` Simon Glass
2014-10-24 0:58 ` [U-Boot] [PATCH v2 08/11] fdt: Add ft_system_setup() function for system device tree additions Simon Glass
2014-10-24 18:50 ` Tom Rini
2014-11-13 2:40 ` Simon Glass
2014-11-21 3:25 ` Simon Glass
2014-10-24 0:58 ` [U-Boot] [PATCH v2 09/11] fdt: Change fdt_pack_reg() to static and fix types Simon Glass
2014-10-24 18:49 ` Tom Rini
2014-11-21 3:25 ` Simon Glass
2014-10-24 0:58 ` [U-Boot] [PATCH v2 10/11] fdt: Add a function to decode a named memory region Simon Glass
2014-10-24 18:49 ` Tom Rini
2014-11-21 3:26 ` Simon Glass
2014-10-24 0:58 ` [U-Boot] [PATCH v2 11/11] fdt: Try to use fdt_address_cells()/fdt_size_cells() Simon Glass
2014-10-24 18:49 ` Tom Rini
2014-11-21 3:26 ` Simon Glass
2014-10-24 15:50 ` [U-Boot] [PATCH v2 01/11] fdt: Allow ft_board_setup() to report failure Anatolij Gustschin
2014-10-24 18:04 ` Tom Rini
2014-10-24 19:56 ` Simon Glass
2014-11-21 3:24 ` 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=20141027142411.GV25506@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