From: Zhu Ling <1536943441@qq.com>
To: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linus.walleij@linaro.org,
brgl@bgdev.pl, andy@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
chenbaozi@phytium.com.cn, Zhu Ling <1536943441@qq.com>
Subject: [PATCH v1 0/3] gpio: Add Phytium platform GPIO controller support
Date: Mon, 2 Mar 2026 17:51:44 +0800 [thread overview]
Message-ID: <tencent_3D2D916753B073166B6392D71A1F4B371908@qq.com> (raw)
This series adds support for the Phytium platform GPIO controller.
It includes:
- devicetree binding for "phytium,gpio" and vendor prefix registration
- core and platform GPIO driver support
- MAINTAINERS entry
This submission intentionally covers only the platform GPIO path.
Phytium PCI GPIO and SGPIO support are not included in this series.
Validation:
- dt_binding_check passed for Documentation/devicetree/bindings/gpio/phytium,gpio.yaml
- build tested with ARCH=arm64 cross compile
- runtime tested on a Phytium arm64 board with DT boot
Zhu Ling (3):
dt-bindings: gpio: add Phytium GPIO controller
gpio: add support for Phytium platform GPIO controller
MAINTAINERS: add entry for Phytium platform GPIO driver
.../bindings/gpio/phytium,gpio.yaml | 134 ++++++
.../devicetree/bindings/vendor-prefixes.yaml | 2 +
MAINTAINERS | 10 +
drivers/gpio/Kconfig | 16 +
drivers/gpio/Makefile | 2 +
drivers/gpio/gpio-phytium-core.c | 444 ++++++++++++++++++
drivers/gpio/gpio-phytium-core.h | 90 ++++
drivers/gpio/gpio-phytium-platform.c | 226 +++++++++
8 files changed, 924 insertions(+)
create mode 100644 Documentation/devicetree/bindings/gpio/phytium,gpio.yaml
create mode 100644 drivers/gpio/gpio-phytium-core.c
create mode 100644 drivers/gpio/gpio-phytium-core.h
create mode 100644 drivers/gpio/gpio-phytium-platform.c
--
2.34.1
next reply other threads:[~2026-03-02 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 9:51 Zhu Ling [this message]
2026-03-02 10:01 ` Andy Shevchenko
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=tencent_3D2D916753B073166B6392D71A1F4B371908@qq.com \
--to=1536943441@qq.com \
--cc=andy@kernel.org \
--cc=brgl@bgdev.pl \
--cc=chenbaozi@phytium.com.cn \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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®