[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <152158175270.198100.17839151793045734833@swboyd.mtv.corp.google.com>
Date: Tue, 20 Mar 2018 14:35:52 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>, linux-arm-msm@...r.kernel.org,
Timur Tabi <timur@...eaurora.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Grant Likely <grant.likely@...retlab.ca>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v2 1/3] dt-bindings: pinctrl: Add a reserved-gpio-ranges property
Quoting Linus Walleij (2018-03-19 20:36:35)
> Hi Stephen,
>
> thanks for the patch and hope you have a good time at your new
> workplace!
>
> On Fri, Jan 26, 2018 at 2:13 AM, Stephen Boyd <sboyd@...eaurora.org> wrote:
>
> > Some qcom platforms make some GPIOs or pins unavailable for use
> > by non-secure operating systems, and thus reading or writing the
> > registers for those pins will cause access control issues.
> > Introduce a DT property to describe the set of GPIOs that are
> > available for use so that higher level OSes are able to know what
> > pins to avoid reading/writing.
> >
> > Cc: Grant Likely <grant.likely@...retlab.ca>
> > Cc: <devicetree@...r.kernel.org>
> > Signed-off-by: Stephen Boyd <sboyd@...eaurora.org>
>
> This looks fine except Andy's note to rename this ranges
> to gpio-reserved-ranges for namespacing.
Ok! I'll rename to gpio-reserved-ranges.
>
> Are you reposting this series as v3 with this fixed or does someone
> else need to pick it up?
Yes I can do it today or tomorrow.
Powered by blists - more mailing lists