Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ye Zhang <ye.zhang@rock-chips.com>
To: Ye Zhang <ye.zhang@rock-chips.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Heiko Stuebner <heiko@sntech.de>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	tao.huang@rock-chips.com
Subject: [PATCH v4 0/7] pinctrl: rockchip: Add RK3506 and RV1126B pinctrl and RMIO support
Date: Sat, 27 Dec 2025 19:49:50 +0800	[thread overview]
Message-ID: <20251227114957.3287944-1-ye.zhang@rock-chips.com> (raw)

This series adds pinctrl support for the Rockchip RK3506 and RV1126B SoC,
and adds support for RMIO (Rockchip Matrix I/O).

The series includes:
- RK3506 pinctrl driver implementation
- RV1126B pinctrl driver implementation
- RMIO controller binding and driver support
- GPIO driver update to support new version GPIO

Note on grouping:
The RV1126B support patches are included in this series because the RV1126B
pinctrl driver implementation depends on the PIN_BANK_IOMUX_FLAGS_OFFSET_DRV_FLAGS
macro, which is introduced in the RK3506 support patches. Splitting these
patches into separate series would break the build for RV1126B if applied
independently.

Changes in v4:
- Remove rockchip,rmio.yaml and drop the separate RMIO child node.
- Remove rockchip,rk3506-rmio.h
- Refactor RK3506 RMIO implementation:
  - RMIO is now handled as a separate list within the pin group, allowing
    flexible mapping (e.g., multiple RMIO configs per group).
  - The driver now retrieves the RMIO regmap via a syscon phandle defined
    in the pinctrl node.
- Add RK3506 pinctrl and rmio DTS to match the new RMIO binding format.

Changes in v3:
- Drop already merged patches (rk3506 basic support).
- Remove unhelpful mappings in rockchip,rk3506-rmio.h
- Improve YAML schema: fix constraints and examples for RMIO.

Changes in v2:
- Added RV1126B pinctrl support (patches 3 and 4)
- Updated GPIO driver to support new version GPIO (patch 5)
- Added header file for RK3506 RMIO (patch 6)
- RMIO is now implemented as a separate pinctrl device (patches 7, 8)

Ye Zhang (7):
  dt-bindings: pinctrl: Add rv1126b pinctrl support
  pinctrl: rockchip: Add rv1126b pinctrl support
  arm64: dts: rockchip: rv1126b: Add pinconf and pinctrl dtsi for
    rv1126b
  gpio: rockchip: support new version GPIO
  dt-bindings: pinctrl: rockchip: Add rk3506 rmio support
  pinctrl: rockchip: Add RK3506 RMIO support
  ARM: dts: rockchip: rk3506: Add pinctrl and rmio dtsi for rk3506

 .../bindings/pinctrl/rockchip,pinctrl.yaml    |    25 +
 .../dts/rockchip/rk3506-pinctrl-rmio.dtsi     | 25162 ++++++++++++++++
 .../arm/boot/dts/rockchip/rk3506-pinctrl.dtsi |  1795 ++
 .../boot/dts/rockchip/rv1126b-pinconf.dtsi    |   660 +
 .../boot/dts/rockchip/rv1126b-pinctrl.dtsi    |  3218 ++
 drivers/gpio/gpio-rockchip.c                  |     2 +
 drivers/pinctrl/pinctrl-rockchip.c            |   282 +-
 drivers/pinctrl/pinctrl-rockchip.h            |    20 +
 8 files changed, 31160 insertions(+), 4 deletions(-)
 create mode 100644 arch/arm/boot/dts/rockchip/rk3506-pinctrl-rmio.dtsi
 create mode 100644 arch/arm/boot/dts/rockchip/rk3506-pinctrl.dtsi
 create mode 100644 arch/arm64/boot/dts/rockchip/rv1126b-pinconf.dtsi
 create mode 100644 arch/arm64/boot/dts/rockchip/rv1126b-pinctrl.dtsi

-- 
2.34.1



             reply	other threads:[~2025-12-27 11:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-27 11:49 Ye Zhang [this message]
2025-12-27 11:49 ` [PATCH v4 1/7] dt-bindings: pinctrl: Add rv1126b pinctrl support Ye Zhang
2025-12-28 10:30   ` Krzysztof Kozlowski
2025-12-27 11:49 ` [PATCH v4 2/7] pinctrl: rockchip: " Ye Zhang
2025-12-27 11:49 ` [PATCH v4 3/7] arm64: dts: rockchip: rv1126b: Add pinconf and pinctrl dtsi for rv1126b Ye Zhang
2026-01-04 11:54   ` Linus Walleij
2025-12-27 11:49 ` [PATCH v4 4/7] gpio: rockchip: support new version GPIO Ye Zhang
2025-12-27 11:49 ` [PATCH v4 5/7] dt-bindings: pinctrl: rockchip: Add rk3506 rmio support Ye Zhang
2025-12-28 10:37   ` Krzysztof Kozlowski
2025-12-31 10:12     ` Ye Zhang
2026-01-04 11:48   ` Linus Walleij
2025-12-27 11:49 ` [PATCH v4 6/7] pinctrl: rockchip: Add RK3506 RMIO support Ye Zhang
     [not found] ` <20251227114957.3287944-8-ye.zhang@rock-chips.com>
2025-12-28 10:37   ` [PATCH v4 7/7] ARM: dts: rockchip: rk3506: Add pinctrl and rmio dtsi for rk3506 Krzysztof Kozlowski
     [not found]     ` <AGkAtwAtJy-UDFfi3M2RSaqR.3.1766993111418.Hmail.ye.zhang@rock-chips.com>
2025-12-29  8:47       ` Krzysztof Kozlowski
2025-12-31  8:12     ` Ye Zhang
2026-01-04 12:07       ` Linus Walleij
     [not found]     ` <543e7200-2126-490a-a7a8-4898362a910d@rock-chips.com>
2026-02-08 10:31       ` Krzysztof Kozlowski
2026-01-04 12:00   ` Linus Walleij

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=20251227114957.3287944-1-ye.zhang@rock-chips.com \
    --to=ye.zhang@rock-chips.com \
    --cc=brgl@bgdev.pl \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --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-rockchip@lists.infradead.org \
    --cc=robh@kernel.org \
    --cc=tao.huang@rock-chips.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