[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170803233334.GC29306@minitux>
Date: Thu, 3 Aug 2017 16:33:34 -0700
From: Bjorn Andersson <bjorn.andersson@...aro.org>
To: Rob Herring <robh+dt@...nel.org>
Cc: Frank Rowand <frowand.list@...il.com>,
Andy Gross <andy.gross@...aro.org>,
David Brown <david.brown@...aro.org>,
Mark Rutland <mark.rutland@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
linux-arm-msm <linux-arm-msm@...r.kernel.org>,
"open list:ARM/QUALCOMM SUPPORT" <linux-soc@...r.kernel.org>
Subject: Re: [PATCH v2 1/5] of/platform: Generalize /reserved-memory handling
On Thu 03 Aug 10:40 PDT 2017, Rob Herring wrote:
> On Wed, Aug 2, 2017 at 9:57 PM, Bjorn Andersson
> <bjorn.andersson@...aro.org> wrote:
> > diff --git a/drivers/of/platform.c b/drivers/of/platform.c
[..]
> > + rmem_nodes = of_find_node_by_path("/reserved-memory");
> > + for_each_available_child_of_node(rmem_nodes, node) {
> > + ret = of_device_compatible_match(node, rmem_compats);
> > + if (ret)
>
> I would just do:
>
> for_each_matching_node(node, ...)
> of_platform_device_create(node, NULL, NULL);
>
> I don't think the kernel has to validate that ramoops and any others
> we add are children of /reserved-memory. We should only have those
> compatibles located there and any other location would be an error.
>
Okay, looks reasonable.
Will update and resend once I know your decision on 2/5.
Regards,
Bjorn
Powered by blists - more mailing lists