From: Billy Tsai <billy_tsai@aspeedtech.com>
To: <lee@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <joel@jms.id.au>,
<andrew@codeconstruct.com.au>, <linus.walleij@linaro.org>,
<brgl@bgdev.pl>, <billy_tsai@aspeedtech.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-aspeed@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
<openbmc@lists.ozlabs.org>, <linux-gpio@vger.kernel.org>,
<BMC-SW@aspeedtech.com>
Subject: [PATCH v2 0/4] Add pinctrl support for AST2700 SoC
Date: Thu, 4 Sep 2025 18:33:57 +0800 [thread overview]
Message-ID: <20250904103401.88287-1-billy_tsai@aspeedtech.com> (raw)
Document and add the pinctrl driver for AST2700 SoC.
Changes since v1:
- Update pinctrl aspeed binding files.
- Update the commit message for pinctrl binding patch.
Billy Tsai (4):
dt-bindings: mfd: aspeed,ast2x00-scu: Support ast2700 pinctrl
dt-bindings: pinctrl: aspeed: Add support for AST27xx
pinctrl: aspeed: Add AST2700 pinmux support
arm64: dts: add AST27xx pinctrl configuration nodes
.../bindings/mfd/aspeed,ast2x00-scu.yaml | 2 +
.../pinctrl/aspeed,ast2700-soc0-pinctrl.yaml | 115 +
.../pinctrl/aspeed,ast2700-soc1-pinctrl.yaml | 435 +++
.../boot/dts/aspeed/aspeed-g7-pinctrl.dtsi | 1359 +++++++++
drivers/pinctrl/aspeed/Kconfig | 8 +
drivers/pinctrl/aspeed/Makefile | 1 +
.../pinctrl/aspeed/pinctrl-aspeed-g7-soc0.c | 503 ++++
.../pinctrl/aspeed/pinctrl-aspeed-g7-soc1.c | 2523 +++++++++++++++++
drivers/pinctrl/aspeed/pinctrl-aspeed.c | 47 +
drivers/pinctrl/aspeed/pinctrl-aspeed.h | 11 +-
drivers/pinctrl/aspeed/pinmux-aspeed.h | 35 +-
11 files changed, 5034 insertions(+), 5 deletions(-)
create mode 100644 Documentation/devicetree/bindings/pinctrl/aspeed,ast2700-soc0-pinctrl.yaml
create mode 100644 Documentation/devicetree/bindings/pinctrl/aspeed,ast2700-soc1-pinctrl.yaml
create mode 100644 arch/arm64/boot/dts/aspeed/aspeed-g7-pinctrl.dtsi
create mode 100644 drivers/pinctrl/aspeed/pinctrl-aspeed-g7-soc0.c
create mode 100644 drivers/pinctrl/aspeed/pinctrl-aspeed-g7-soc1.c
--
2.25.1
next reply other threads:[~2025-09-04 10:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 10:33 Billy Tsai [this message]
2025-09-04 10:33 ` [PATCH v2 1/4] dt-bindings: mfd: aspeed,ast2x00-scu: Support ast2700 pinctrl Billy Tsai
2025-09-05 8:13 ` Krzysztof Kozlowski
2025-09-04 10:33 ` [PATCH v2 2/4] dt-bindings: pinctrl: aspeed: Add support for AST27xx Billy Tsai
2025-09-05 8:16 ` Krzysztof Kozlowski
2025-09-04 10:34 ` [PATCH v2 3/4] pinctrl: aspeed: Add AST2700 pinmux support Billy Tsai
2025-09-06 15:59 ` kernel test robot
2025-09-25 4:48 ` Andrew Jeffery
2025-11-11 2:24 ` Billy Tsai
2025-09-04 10:34 ` [PATCH v2 4/4] arm64: dts: add AST27xx pinctrl configuration nodes Billy Tsai
2025-09-04 14:26 ` Rob Herring
2025-09-05 8:12 ` [PATCH v2 0/4] Add pinctrl support for AST2700 SoC Krzysztof Kozlowski
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=20250904103401.88287-1-billy_tsai@aspeedtech.com \
--to=billy_tsai@aspeedtech.com \
--cc=BMC-SW@aspeedtech.com \
--cc=andrew@codeconstruct.com.au \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--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