[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqLR9sm+GRU8EP4eO_Ln2UhD=ztdAU834CzP8RSv2s2jQg@mail.gmail.com>
Date: Mon, 27 Feb 2023 11:17:41 -0600
From: Rob Herring <robh+dt@...nel.org>
To: Frank Rowand <frowand.list@...il.com>
Cc: Clément Léger <clement.leger@...tlin.com>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Lizhi Hou <lizhi.hou@...inx.com>,
Allan Nielsen <allan.nielsen@...rochip.com>,
Horatiu Vultur <horatiu.vultur@...rochip.com>,
Steen Hegelund <steen.hegelund@...rochip.com>,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>
Subject: Re: [PATCH v3 1/2] of: create of_root if no dtb provided
On Thu, Feb 23, 2023 at 3:34 PM Frank Rowand <frowand.list@...il.com> wrote:
>
> When enabling CONFIG_OF on a platform where of_root is not populated by
> firmware, we end up without a root node. In order to apply overlays and
> create subnodes of the root node, we need one. Create this root node
> by unflattening an empty builtin dtb.
>
> If firmware provides a flattened device tree (FDT) then the FDT is
> unflattened via setup_arch(). Otherwise, setup_of() which is called
> immediately after setup_arch(), and will create the default root node
> if it does not exist.
Why do we need a hook after setup_arch() rather than an initcall?
Rob
Powered by blists - more mailing lists