From: Yao Zi <ziyao@disroot.org>
To: Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, loongarch@lists.linux.dev,
Mingcong Bai <jeffbai@aosc.io>,
Kexy Biscuit <kexybiscuit@aosc.io>, Yao Zi <ziyao@disroot.org>
Subject: [PATCH 0/3] Support pinctrl for Loongson 2K0300 SoC
Date: Mon, 11 Aug 2025 16:37:47 +0000 [thread overview]
Message-ID: <20250811163749.47028-2-ziyao@disroot.org> (raw)
This series adds support for Loongson 2K0300's pin controller, which is
much different from the previous generation's one: pin multiplexing
could be done for each pin, instead of at units of pin groups. A new
driver, pinctrl-ls2k0300.c, is introduced to handle this.
This controller is also capable of drive-strength configuration for some
functions, with a limitation that all pins configured to the the same
function share the same drive-strength. Thus drive-strength is described
as a property of function, and is handled bypassing the generic pinconf
API for less complexity, since the pinconf API is based on the pingroups.
The devicetree patch depends on v3 of "Add clock support for Loongson
2K0300 SoC"[1] for applying. Further comments, especially on handling of
the only pinconf attribute, drive-strength, will be appreciated. Thanks
again for your time and review.
[1]: https://lore.kernel.org/all/20250805150147.25909-1-ziyao@disroot.org/
Yao Zi (3):
dt-binding: pinctrl: Document Loongson 2K0300 pin controller
pinctrl: ls2k0300: Support Loongson 2K0300 SoC
LoongArch: dts: Add pinctrl configuration for Loongson 2K0300
.../pinctrl/loongson,ls2k0300-pinctrl.yaml | 92 ++++
MAINTAINERS | 7 +
arch/loongarch/boot/dts/loongson-2k0300.dtsi | 39 ++
drivers/pinctrl/Kconfig | 14 +
drivers/pinctrl/Makefile | 1 +
drivers/pinctrl/pinctrl-ls2k0300.c | 515 ++++++++++++++++++
6 files changed, 668 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pinctrl/loongson,ls2k0300-pinctrl.yaml
create mode 100644 drivers/pinctrl/pinctrl-ls2k0300.c
--
2.50.1
next reply other threads:[~2025-08-11 16:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 16:37 Yao Zi [this message]
2025-08-11 16:37 ` [PATCH 1/3] dt-binding: pinctrl: Document Loongson 2K0300 pin controller Yao Zi
2025-08-18 17:58 ` Rob Herring
2025-08-19 11:37 ` Yao Zi
2025-09-12 8:42 ` Yao Zi
2025-10-10 22:05 ` Rob Herring
2025-10-13 22:48 ` Linus Walleij
2025-10-14 2:23 ` Yao Zi
2025-10-14 10:38 ` Linus Walleij
2025-08-11 16:37 ` [PATCH 2/3] pinctrl: ls2k0300: Support Loongson 2K0300 SoC Yao Zi
2025-08-14 3:15 ` Yao Zi
2025-08-19 10:02 ` Linus Walleij
2025-08-19 12:40 ` Yao Zi
2025-08-21 11:27 ` Linus Walleij
2025-08-11 16:37 ` [PATCH 3/3] LoongArch: dts: Add pinctrl configuration for Loongson 2K0300 Yao Zi
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=20250811163749.47028-2-ziyao@disroot.org \
--to=ziyao@disroot.org \
--cc=chenhuacai@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jeffbai@aosc.io \
--cc=kernel@xen0n.name \
--cc=kexybiscuit@aosc.io \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=robh@kernel.org \
/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
all inboxes | Powered by JetHome®