From: "Arınç ÜNAL" <arinc.unal@arinc9.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Sergio Paracuellos <sergio.paracuellos@gmail.com>,
Luiz Angelo Daros de Luca <luizluca@gmail.com>
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-mips@vger.kernel.org
Subject: [PATCH 0/6] Enhance Ralink pinctrl documentation
Date: Tue, 13 Dec 2022 16:04:24 +0300 [thread overview]
Message-ID: <20221213130430.172876-1-arinc.unal@arinc9.com> (raw)
Heyo,
This series mainly enhances the Ralink pinctrl documentation, and make a
small variable name change on the subdrivers.
I've compile-tested all the subdrivers.
I've tested the dt-binding changes with:
make dt_binding_check DT_SCHEMA_FILES=pinctrl/ralink
Arınç ÜNAL (6):
pinctrl: ralink: rename variables which point out the pin group
dt-bindings: pinctrl: mt7620: add proper function muxing binding
dt-bindings: pinctrl: mt7621: add proper function muxing binding
dt-bindings: pinctrl: rt2880: add proper function muxing binding
dt-bindings: pinctrl: rt305x: add proper function muxing binding
dt-bindings: pinctrl: rt3883: add proper function muxing binding
.../bindings/pinctrl/ralink,mt7620-pinctrl.yaml | 632 +++++++++++++++++--
.../bindings/pinctrl/ralink,mt7621-pinctrl.yaml | 204 +++++-
.../bindings/pinctrl/ralink,rt2880-pinctrl.yaml | 85 ++-
.../bindings/pinctrl/ralink,rt305x-pinctrl.yaml | 235 ++++++-
.../bindings/pinctrl/ralink,rt3883-pinctrl.yaml | 204 +++++-
drivers/pinctrl/ralink/pinctrl-mt7620.c | 164 ++---
drivers/pinctrl/ralink/pinctrl-mt7621.c | 48 +-
drivers/pinctrl/ralink/pinctrl-rt2880.c | 28 +-
drivers/pinctrl/ralink/pinctrl-rt305x.c | 82 +--
drivers/pinctrl/ralink/pinctrl-rt3883.c | 44 +-
10 files changed, 1462 insertions(+), 264 deletions(-)
next reply other threads:[~2022-12-13 13:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 13:04 Arınç ÜNAL [this message]
2022-12-13 13:04 ` [PATCH 1/6] pinctrl: ralink: rename variables which point out the pin group Arınç ÜNAL
2022-12-13 13:04 ` [PATCH 2/6] dt-bindings: pinctrl: mt7620: add proper function muxing binding Arınç ÜNAL
2022-12-14 11:55 ` Krzysztof Kozlowski
2022-12-14 13:03 ` Arınç ÜNAL
2022-12-14 13:10 ` Krzysztof Kozlowski
2022-12-13 13:04 ` [PATCH 3/6] dt-bindings: pinctrl: mt7621: " Arınç ÜNAL
2022-12-14 13:13 ` Krzysztof Kozlowski
2022-12-13 13:04 ` [PATCH 4/6] dt-bindings: pinctrl: rt2880: " Arınç ÜNAL
2022-12-13 13:04 ` [PATCH 5/6] dt-bindings: pinctrl: rt305x: " Arınç ÜNAL
2022-12-13 13:04 ` [PATCH 6/6] dt-bindings: pinctrl: rt3883: " Arınç ÜNAL
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=20221213130430.172876-1-arinc.unal@arinc9.com \
--to=arinc.unal@arinc9.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=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 \
/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