From: Rob Herring <robh@kernel.org>
To: "Arınç ÜNAL" <arinc.unal@arinc9.com>
Cc: linux-gpio@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Sergio Paracuellos <sergio.paracuellos@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Luiz Angelo Daros de Luca <luizluca@gmail.com>,
erkin.bozoglu@xeront.com, linux-mips@vger.kernel.org,
devicetree@vger.kernel.org, Joe Perches <joe@perches.com>,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v2 10/14] dt-bindings: pinctrl: rt2880: fix binding name, pin groups and functions
Date: Tue, 19 Apr 2022 13:02:19 -0500 [thread overview]
Message-ID: <Yl75K2iSlAY+9DQF@robh.at.kernel.org> (raw)
In-Reply-To: <20220414173916.5552-11-arinc.unal@arinc9.com>
On Thu, 14 Apr 2022 20:39:12 +0300, Arınç ÜNAL wrote:
> Deprecate the old property "ralink,rt2880-pinmux". Add the new property
> "ralink,rt2880-pinctrl". The old property name was inaccurate as the
> hardware block is called pinctrl across the Mediatek/Ralink architecture.
>
> Current pin group and function bindings are for MT7621. Put bindings for
> RT2880 instead.
>
> Add me as a maintainer.
>
> Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
> ---
> ...pinmux.yaml => ralink,rt2880-pinctrl.yaml} | 26 +++++++++----------
> 1 file changed, 13 insertions(+), 13 deletions(-)
> rename Documentation/devicetree/bindings/pinctrl/{ralink,rt2880-pinmux.yaml => ralink,rt2880-pinctrl.yaml} (53%)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-04-19 18:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 17:39 [PATCH v2 00/14] Refactor Ralink Pinctrl and Add Documentation Arınç ÜNAL
2022-04-14 17:39 ` [PATCH v2 01/14] pinctrl: ralink: rename MT7628(an) functions to MT76X8 Arınç ÜNAL
2022-04-14 17:39 ` [PATCH v2 02/14] pinctrl: ralink: rename pinctrl-rt2880 to pinctrl-ralink Arınç ÜNAL
2022-04-14 17:39 ` [PATCH v2 03/14] pinctrl: ralink: rename pinmux functions to pinctrl Arınç ÜNAL
2022-04-14 17:39 ` [PATCH v2 04/14] pinctrl: ralink: rename pinctrl-rt288x to pinctrl-rt2880 Arınç ÜNAL
2022-04-14 17:39 ` [PATCH v2 05/14] pinctrl: ralink: rename variable names for functions on MT7620 and MT7621 Arınç ÜNAL
2022-04-14 17:39 ` [PATCH v2 06/14] pinctrl: ralink: rename driver names to subdrivers Arınç ÜNAL
2022-04-14 17:39 ` [PATCH v2 07/14] pinctrl: ralink: add new compatible strings for each pinctrl subdriver Arınç ÜNAL
2022-04-14 17:39 ` [PATCH v2 08/14] MAINTAINERS: add Ralink pinctrl driver Arınç ÜNAL
2022-04-14 17:39 ` [PATCH v2 09/14] mips: dts: ralink: mt7621: use the new compatible string for MT7621 pinctrl Arınç ÜNAL
2022-04-14 17:39 ` [PATCH v2 10/14] dt-bindings: pinctrl: rt2880: fix binding name, pin groups and functions Arınç ÜNAL
2022-04-19 18:02 ` Rob Herring [this message]
2022-04-14 17:39 ` [PATCH v2 11/14] dt-bindings: pinctrl: add binding for Ralink MT7620 pinctrl Arınç ÜNAL
2022-04-19 18:03 ` Rob Herring
2022-04-14 17:39 ` [PATCH v2 12/14] dt-bindings: pinctrl: add binding for Ralink MT7621 pinctrl Arınç ÜNAL
2022-04-19 18:03 ` Rob Herring
2022-04-14 17:39 ` [PATCH v2 13/14] dt-bindings: pinctrl: add binding for Ralink RT305X pinctrl Arınç ÜNAL
2022-04-19 18:05 ` Rob Herring
2022-04-19 18:59 ` Arınç ÜNAL
2022-04-14 17:39 ` [PATCH v2 14/14] dt-bindings: pinctrl: add binding for Ralink RT3883 pinctrl Arınç ÜNAL
2022-04-19 18:06 ` Rob Herring
2022-04-19 5:41 ` [PATCH v2 00/14] Refactor Ralink Pinctrl and Add Documentation Sergio Paracuellos
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=Yl75K2iSlAY+9DQF@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=arinc.unal@arinc9.com \
--cc=devicetree@vger.kernel.org \
--cc=erkin.bozoglu@xeront.com \
--cc=joe@perches.com \
--cc=krzk+dt@kernel.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=linux-mediatek@lists.infradead.org \
--cc=linux-mips@vger.kernel.org \
--cc=luizluca@gmail.com \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sergio.paracuellos@gmail.com \
--cc=tsbogend@alpha.franken.de \
/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).