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 wrote: > > > Some qcom platforms make some GPIOs or pins unavailable for use > > by

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 wrote: > > > Some qcom platforms make some GPIOs or pins unavailable for use > > by non-secure operating

Re: [PATCH v2 1/3] dt-bindings: pinctrl: Add a reserved-gpio-ranges property

On 3/19/18 10:36 PM, Linus Walleij wrote: This looks fine except Andy's note to rename this ranges to gpio-reserved-ranges for namespacing. Are you reposting this series as v3 with this fixed or does someone else need to pick it up? I will pick this up if Stephen wants me to. -- Qualcomm

Re: [PATCH v2 1/3] dt-bindings: pinctrl: Add a reserved-gpio-ranges property

On 3/19/18 10:36 PM, Linus Walleij wrote: This looks fine except Andy's note to rename this ranges to gpio-reserved-ranges for namespacing. Are you reposting this series as v3 with this fixed or does someone else need to pick it up? I will pick this up if Stephen wants me to. -- Qualcomm

Re: [PATCH v2 1/3] dt-bindings: pinctrl: Add a reserved-gpio-ranges property

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 wrote: > Some qcom platforms make some GPIOs or pins unavailable for use > by non-secure operating systems, and thus reading or writing the

Re: [PATCH v2 1/3] dt-bindings: pinctrl: Add a reserved-gpio-ranges property

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 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

Re: [PATCH v2 1/3] dt-bindings: pinctrl: Add a reserved-gpio-ranges property

On Thu 25 Jan 17:13 PST 2018, Stephen Boyd wrote: + Rob > 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

Re: [PATCH v2 1/3] dt-bindings: pinctrl: Add a reserved-gpio-ranges property

On Thu 25 Jan 17:13 PST 2018, Stephen Boyd wrote: + Rob > 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

Re: [PATCH v2 1/3] dt-bindings: pinctrl: Add a reserved-gpio-ranges property

On Thu, 2018-01-25 at 17:13 -0800, Stephen Boyd 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

Re: [PATCH v2 1/3] dt-bindings: pinctrl: Add a reserved-gpio-ranges property

On Thu, 2018-01-25 at 17:13 -0800, Stephen Boyd 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