[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZSdIlaom+QO8IlKW@octopus>
Date: Thu, 12 Oct 2023 10:15:01 +0900
From: AKASHI Takahiro <takahiro.akashi@...aro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: sudeep.holla@....com, cristian.marussi@....com, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
linus.walleij@...aro.org, Oleksii_Moisieiev@...m.com,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org
Subject: Re: [RFC v2 5/5] dt-bindings: gpio: Add bindings for pinctrl based
generic gpio driver
On Thu, Oct 05, 2023 at 09:48:09PM +0200, Krzysztof Kozlowski wrote:
> On 05/10/2023 04:58, AKASHI Takahiro wrote:
> > A dt binding for pin controller based generic gpio driver is defined in
> > this commit. One usable device is Arm's SCMI.
> >
> > Signed-off-by: AKASHI Takahiro <takahiro.akashi@...aro.org>
>
> > +
> > +required:
> > + - compatible
> > + - gpio-controller
> > + - "#gpio-cells"
> > + - gpio-ranges
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > + - |
> > + gpio0: gpio@0 {
>
> No reg, so no unit address.
My intention was to allow for multiple nodes (instances) of
pinctrl based gpio devices. But I don't care the naming.
> Drop also unused label.
Okay, I already dropped an example consumer device and have no need
for the label any longer.
-Takahiro Akashi
>
> > + compatible = "pin-control-gpio";
> > + gpio-controller;
>
> Best regards,
> Krzysztof
>
Powered by blists - more mailing lists