[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqJYNXoZbN4zydkkZHWYxJuH4ObYJGgz2L7++kMgTWC1vg@mail.gmail.com>
Date: Tue, 17 Oct 2017 08:02:12 -0500
From: Rob Herring <robh@...nel.org>
To: Sudeep Holla <sudeep.holla@....com>
Cc: "linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Arnd Bergmann <arnd@...db.de>,
Frank Rowand <frowand.list@...il.com>
Subject: Re: [RESEND][PATCH 1/4] of: platform: populate /firmware/ node from of_platform_default_populate_init()
On Thu, Sep 28, 2017 at 5:45 AM, Sudeep Holla <sudeep.holla@....com> wrote:
> Since "/firmware" does not have its own "compatible" property as it's
> just collection of nodes representing firmware interface, it's sub-nodes
> are not populated during system initialization.
>
> Currently different firmware drivers search the /firmware/ node and
> populate the sub-node devices selectively. Instead we can populate
> the /firmware/ node during init to avoid more drivers continuing to
> populate the devices selectively.
>
> To generalize the solution this patch populates the /firmware/ node
> explicitly from of_platform_default_populate_init().
>
> Cc: Arnd Bergmann <arnd@...db.de>
> Cc: Rob Herring <robh@...nel.org>
> Signed-off-by: Sudeep Holla <sudeep.holla@....com>
> ---
> drivers/of/platform.c | 4 ++++
> 1 file changed, 4 insertions(+)
Acked-by: Rob Herring <robh@...nel.org>
Powered by blists - more mailing lists