[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdY=eza0TuBRDb_cWk9LM2qNQg76rZSgWa-RP4TYLL=Ppw@mail.gmail.com>
Date: Mon, 9 Oct 2023 15:13:24 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Cristian Marussi <cristian.marussi@....com>
Cc: Rob Herring <robh@...nel.org>,
AKASHI Takahiro <takahiro.akashi@...aro.org>,
sudeep.holla@....com, krzysztof.kozlowski+dt@...aro.org,
conor+dt@...nel.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 Mon, Oct 9, 2023 at 11:08 AM Cristian Marussi
<cristian.marussi@....com> wrote:
> > > + gpio0: gpio@0 {
> > > + compatible = "pin-control-gpio";
> > > + gpio-controller;
> > > + #gpio-cells = <2>;
> > > + gpio-ranges = <&scmi_pinctrl 0 10 5>,
> > > + <&scmi_pinctrl 5 0 0>;
> > > + gpio-ranges-group-names = "",
> > > + "pinmux_gpio";
> > > + };
> >
>
> Assuming the above &scmi_pinctrl refers to the protocol node as we
> usually do,
No it does not, it is a three-layer cake.
scmi <-> scmi_pinctrl <-> scmi_gpio
it refers to the scmi_pinctrl node.
There is no SCMI GPIO protocol, instead SCMI is using the
operations already available in the pin controller to exercise
GPIO. Generic pin control has operations to drive lines for
example, and Takahiro is adding the ability for a generic pin
controller to also read a line.
Yours,
Linus Walleij
Powered by blists - more mailing lists