From: Frank Rowand <frowand.list@gmail.com>
To: Rob Herring <robh@kernel.org>, devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] of/fdt: Scan the root node properties earlier
Date: Tue, 4 Sep 2018 18:49:47 -0700 [thread overview]
Message-ID: <b86ed9cf-d5fd-09fb-eb82-0143c759f5cf@gmail.com> (raw)
In-Reply-To: <20180830190523.31474-2-robh@kernel.org>
On 08/30/18 12:05, Rob Herring wrote:
> Scan the root node properties (#{size,address}-cells) earlier,
^^^^^^^
before mdesc->dt_fixup() is called
> so that
> the dt_root_addr_cells and dt_root_size_cells variables are initialized
> and can be used.
by mdesc->dt_fixup()
>
> Cc: Frank Rowand <frowand.list@gmail.com>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> drivers/of/fdt.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
Moving early_init_dt_scan_root() to inside early_init_dt_verify()
puts something that has nothing to do with verifying the fdt
into a function whose purpose is the verify. It hides the side
effect of initializing the dt_root_addr_cells and dt_root_size_cells
variables.
I suggest creating a new function early_init_dt_scan_init_pre_dt_fixup(),
move the chunk of code there instead of to early_init_dt_scan_nodes(),
and call the new function from setup_machine_fdt(), just before
calling mdesc->dt_fixup(). This would be a little bit more code,
but more clearly showing the intent.
-Frank
> diff --git a/drivers/of/fdt.c b/drivers/of/fdt.c
> index 800ad252cf9c..49abe18f1bde 100644
> --- a/drivers/of/fdt.c
> +++ b/drivers/of/fdt.c
> @@ -1215,6 +1215,10 @@ bool __init early_init_dt_verify(void *params)
> initial_boot_params = params;
> of_fdt_crc32 = crc32_be(~0, initial_boot_params,
> fdt_totalsize(initial_boot_params));
> +
> + /* Initialize {size,address}-cells info */
> + of_scan_flat_dt(early_init_dt_scan_root, NULL);
> +
> return true;
> }
>
> @@ -1224,9 +1228,6 @@ void __init early_init_dt_scan_nodes(void)
> /* Retrieve various information from the /chosen node */
> of_scan_flat_dt(early_init_dt_scan_chosen, boot_command_line);
>
> - /* Initialize {size,address}-cells info */
> - of_scan_flat_dt(early_init_dt_scan_root, NULL);
> -
> /* Setup memory, calling early_init_dt_add_memory_arch */
> of_scan_flat_dt(early_init_dt_scan_memory, NULL);
> }
>
next prev parent reply other threads:[~2018-09-05 1:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 19:05 [PATCH 0/3] of: root #{size,address}-cells clean-ups Rob Herring
2018-08-30 19:05 ` [PATCH 1/3] of/fdt: Scan the root node properties earlier Rob Herring
2018-09-05 1:49 ` Frank Rowand [this message]
2018-09-05 11:51 ` Rob Herring
2018-09-05 18:18 ` Frank Rowand
2018-09-05 20:06 ` Rob Herring
2018-09-05 21:10 ` Frank Rowand
2018-09-05 21:31 ` Rob Herring
2018-09-06 21:03 ` Frank Rowand
2018-08-30 19:05 ` [PATCH 2/3] of/fdt: avoid re-parsing '#{address,size}-cells' in of_fdt_limit_memory Rob Herring
2018-09-01 2:41 ` kbuild test robot
2018-09-05 1:54 ` Frank Rowand
2018-08-30 19:05 ` [PATCH 3/3] of: make default address and size cells sizes private Rob Herring
2018-09-05 1:55 ` Frank Rowand
2018-09-05 4:37 ` Mark Cave-Ayland
2018-09-05 12:12 ` Rob Herring
2018-09-05 16:01 ` Mark Cave-Ayland
2018-09-05 1:56 ` [PATCH 0/3] of: root #{size,address}-cells clean-ups Frank Rowand
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=b86ed9cf-d5fd-09fb-eb82-0143c759f5cf@gmail.com \
--to=frowand.list@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).