From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: sudeep.holla@arm.com, cristian.marussi@arm.com,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, Oleksii_Moisieiev@epam.com,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [RFC 4/4] dt-bindings: gpio: Add bindings for SCMI pinctrl based gpio
Date: Wed, 4 Oct 2023 16:08:23 +0900 [thread overview]
Message-ID: <ZR0PZ+RHzfbrlbnI@octopus> (raw)
In-Reply-To: <CACRpkdZgmwhGYH43iAq=cERaGO9a-mVHXG8sQ2htPw0DcrnuNA@mail.gmail.com>
On Tue, Oct 03, 2023 at 03:16:49PM +0200, Linus Walleij wrote:
> Hi Takahiro,
>
> first, thanks for working on this important and crucial driver!
>
> I'll try to clarify and also explain something of what the others
> are saying (unless I misunderstand them...)
Ah, thank you.
> On Mon, Oct 2, 2023 at 4:17???AM AKASHI Takahiro
> <takahiro.akashi@linaro.org> wrote:
>
> > A dt binding for SCMI pinctrl based gpio driver is defined in this
> > commit. It basically conforms to generic pinctrl-gpio mapping framework.
> >
> > Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
>
> I think like Christian says that SCMI maybe has nothing to do
> with this binding? It is just one possible use case (though we don't know
> of any others.) The resource it is using is generic functionality that exist
> in any pin controller that provides ways to drive lines high and low
> etc.
>
> Would it be named a generic pin control-based GPIO?
If you like :)
As I said, I was not confident that the driver be applicable
to other pinctrl-gpio cases.
> (...)
> > +++ b/Documentation/devicetree/bindings/gpio/arm,scmi-gpio.yaml
> (...)
> > +$id: http://devicetree.org/schemas/gpio/arm,scmi-gpio.yaml#
>
> So no ARM, no scmi, just pin-control-gpio.yaml, be bold!
I'm not so ambitious.
> (I like this long unabbreviated name)
>
> > +title: SCMI pinctrl based generic GPIO controller
>
> Pin control-based generic GPIO controller
>
> Add
>
> description:
> The pin control-based GPIO will facilitate a pin controllers ability
> to drive electric lines high/low and other generic properties of a
> pin controller to perform general-purpose one-bit binary I/O.
>
> (At least I think this is the idea, I hope I understand correctly.)
Okay.
> > +properties:
> > + $nodename:
> > + pattern: "^scmi_gpio(@[0-9a-f]+)$"
>
> These nodes are always just named gpio@...
> the resource marker is "this is a GPIO" that's all it means.
By following other gpio drivers' bindings, I will drop this rule.
> > + compatible:
> > + const: arm,scmi-gpio-generic
>
> const: pin-control-gpio
>
> Other than that I am aboard with the solution!
Hope that the driver works on real hardware :)
-Takahiro Akashi
> Yours,
> Linus Walleij
prev parent reply other threads:[~2023-10-04 7:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 2:15 [RFC 0/4] gpio: add SCMI pinctrl based driver AKASHI Takahiro
2023-10-02 2:15 ` [RFC 1/4] pinctrl: define PIN_CONFIG_INPUT AKASHI Takahiro
2023-10-03 20:49 ` Linus Walleij
2023-10-04 6:54 ` AKASHI Takahiro
2023-10-02 2:16 ` [RFC 2/4] pinctrl: add pinctrl_gpio_get_config() AKASHI Takahiro
2023-10-03 20:52 ` Linus Walleij
2023-10-02 2:16 ` [RFC 3/4] gpio: scmi: add SCMI pinctrl based gpio driver AKASHI Takahiro
2023-10-03 21:35 ` Linus Walleij
2023-10-04 6:53 ` AKASHI Takahiro
2023-10-04 8:35 ` Linus Walleij
2023-10-05 2:42 ` AKASHI Takahiro
2023-10-02 2:16 ` [RFC 4/4] dt-bindings: gpio: Add bindings for SCMI pinctrl based gpio AKASHI Takahiro
2023-10-02 3:25 ` Rob Herring
2023-10-02 14:41 ` Rob Herring
2023-10-02 14:58 ` Cristian Marussi
2023-10-03 1:34 ` AKASHI Takahiro
2023-10-03 0:41 ` AKASHI Takahiro
2023-10-03 8:43 ` Krzysztof Kozlowski
2023-10-03 13:16 ` Linus Walleij
2023-10-04 7:08 ` AKASHI Takahiro [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZR0PZ+RHzfbrlbnI@octopus \
--to=takahiro.akashi@linaro.org \
--cc=Oleksii_Moisieiev@epam.com \
--cc=conor+dt@kernel.org \
--cc=cristian.marussi@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sudeep.holla@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).