From: Linus Walleij <linus.walleij@linaro.org>
To: Tony Lindgren <tony@atomide.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
devicetree@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH v7 1/1] dt-bindings: pinctrl: Update pinctrl-single to use yaml
Date: Mon, 7 Aug 2023 15:33:19 +0200 [thread overview]
Message-ID: <CACRpkdbOMAGYm2WBJ_opNyfmo55MdMA5YaGiqf_DanCCwix6Ug@mail.gmail.com> (raw)
In-Reply-To: <20230721082654.27036-1-tony@atomide.com>
On Fri, Jul 21, 2023 at 10:27 AM Tony Lindgren <tony@atomide.com> wrote:
> Update binding for yaml and remove the old related txt bindings. Note that
> we are also adding the undocumented pinctrl-single,slew-rate property. And
> we only use the first example from the old binding.
>
> As we are mostly using a generic compatible across various SoCs, let's not
> start adding matches for random pin group node naming. Let's standardize on
> pin group node name ending in -pins with an optional instance number
> suffix.
>
> As a pin group may have additional pins added to it later on, let's always
> use -pins rather than -pin for the gropu name.
>
> Most of the dts files have been updated already for the pin group node
> names with a few changes still pending.
>
> Cc: Nishanth Menon <nm@ti.com>
> Cc: Vignesh Raghavendra <vigneshr@ti.com>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
> ---
>
> Changes since v6:
Phew!
Patch applied. Any remaining issues can certainly be fixed in tree.
Yours,
Linus Walleij
next prev parent reply other threads:[~2023-08-07 13:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 8:26 [PATCH v7 1/1] dt-bindings: pinctrl: Update pinctrl-single to use yaml Tony Lindgren
2023-07-24 16:02 ` Rob Herring
2023-07-31 6:19 ` Tony Lindgren
2023-08-07 13:33 ` Linus Walleij [this message]
2023-08-07 14:45 ` Tony Lindgren
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=CACRpkdbOMAGYm2WBJ_opNyfmo55MdMA5YaGiqf_DanCCwix6Ug@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.com \
--cc=vigneshr@ti.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).