public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 08/11] fdt: Add ft_system_setup() function for system device tree additions
Date: Sat, 18 Oct 2014 00:20:43 +0200	[thread overview]
Message-ID: <20141018002043.7a76c93e@crub> (raw)
In-Reply-To: <1413360341-25828-8-git-send-email-sjg@chromium.org>

Hi Simon,

On Wed, 15 Oct 2014 02:05:38 -0600
Simon Glass <sjg@chromium.org> wrote:

> Add an additional function for adding information to the device tree before
> booting. This permits additions which are not board-specific.
> 
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
> 
>  README                |  9 ++++++++-
>  common/cmd_fdt.c      | 15 +++++++++++++++
>  common/image-fdt.c    |  6 ++++++
>  include/fdt_support.h | 12 ++++++++++++
>  include/image.h       |  6 ++++++
>  5 files changed, 47 insertions(+), 1 deletion(-)

One minor comment below. Otherwise

Acked-by: Anatolij Gustschin <agust@denx.de>

> diff --git a/README b/README
> index 46def00..6ecb3e0 100644
> --- a/README
> +++ b/README
> @@ -670,6 +670,13 @@ The following options need to be configured:
>  		Board code has addition modification that it wants to make
>  		to the flat device tree before handing it off to the kernel
>  
> +		CONFIG_OF_SYSTEM_SETUP
> +
> +		Other code has addition modification that it wants to make
> +		to the flat device tree before handing it off to the kernel
> +		This causes ft_board_setup() to be called before booting the

ft_system_setup()

Thanks,

Anatolij

  reply	other threads:[~2014-10-17 22:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-15  8:05 [U-Boot] [PATCH 01/11] fdt: Allow ft_board_setup() to report failure Simon Glass
2014-10-15  8:05 ` [U-Boot] [PATCH 02/11] fdt: Report failure of ft_board_setup() Simon Glass
2014-10-17 20:23   ` Anatolij Gustschin
2014-10-15  8:05 ` [U-Boot] [PATCH 03/11] fdt: Export the fdt_find_or_add_subnode() function Simon Glass
2014-10-17 21:25   ` Anatolij Gustschin
2014-10-15  8:05 ` [U-Boot] [PATCH 04/11] fdt: Add device tree memory bindings Simon Glass
2014-10-15  8:05 ` [U-Boot] [PATCH 05/11] fdt: Use the correct return types for fdtdec_decode_region() Simon Glass
2014-10-17 21:57   ` Anatolij Gustschin
2014-10-15  8:05 ` [U-Boot] [PATCH 06/11] fdt: Enhance flashmap function to deal with region properties Simon Glass
2014-10-17 21:57   ` Anatolij Gustschin
2014-10-15  8:05 ` [U-Boot] [PATCH 07/11] fdt: Tidy up error handling in image_setup_libfdt() Simon Glass
2014-10-18  8:02   ` Anatolij Gustschin
2014-10-15  8:05 ` [U-Boot] [PATCH 08/11] fdt: Add ft_system_setup() function for system device tree additions Simon Glass
2014-10-17 22:20   ` Anatolij Gustschin [this message]
2014-10-15  8:05 ` [U-Boot] [PATCH 09/11] fdt: Change fdt_pack_reg() to static and fix types Simon Glass
2014-10-17 22:16   ` Anatolij Gustschin
2014-10-15  8:05 ` [U-Boot] [PATCH 10/11] fdt: Add a function to decode a named memory region Simon Glass
2014-10-15  8:05 ` [U-Boot] [PATCH 11/11] fdt: Try to use fdt_address_cells()/fdt_size_cells() Simon Glass
2014-10-17 20:19 ` [U-Boot] [PATCH 01/11] fdt: Allow ft_board_setup() to report failure Anatolij Gustschin
2014-10-21  1:51   ` Simon Glass
2014-10-24  0:59     ` 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=20141018002043.7a76c93e@crub \
    --to=agust@denx.de \
    --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