From: Ahmed Naseef <naseefkm@gmail.com>
To: linux-gpio@vger.kernel.org
Cc: Ahmed Naseef <naseefkm@gmail.com>,
Benjamin Larsson <benjamin.larsson@genexis.eu>,
Christian Marangi <ansuelsmth@gmail.com>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Linus Walleij <linusw@kernel.org>,
Lorenzo Bianconi <lorenzo@kernel.org>,
Mikhail Kshevetskiy <mikhail.kshevetskiy@iopsys.eu>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org
Subject: [PATCH v2 0/3] pinctrl: airoha: add EcoNet EN7528 pin controller support
Date: Fri, 28 Aug 2026 19:35:12 +0400 [thread overview]
Message-ID: <cover.1787931313.git.naseefkm@gmail.com> (raw)
The EcoNet EN7528 is a MIPS SoC that uses the same pin controller and GPIO
IP as the Airoha SoCs, so it reuses the shared driver code introduced by
the split into per-SoC drivers. Its register layout differs from every
existing variant though: all IOMUX mode bits live in a single CHIP SCU
register plus a few spill-over bits in IOMUX Control 3, EJTAG has its own
enable register, and every pin configuration register is at a different
offset than on EN7523.
It also differs in a way the shared code did not model: only GPIO0-GPIO15
are wired to the interrupt controller, while the driver assumed all
AIROHA_NUM_PINS GPIOs could raise an interrupt. Patch 1 adds a
num_irq_pins field to the per-SoC match data to describe that, bounds the
interrupt callbacks and handler with it, and feeds it to gpiolib through
gpio_irq_chip::init_valid_mask so gpiod_to_irq() fails up front for a pin
that can never be an interrupt source. All existing SoCs pass
AIROHA_NUM_PINS and are unaffected.
Patch 2 documents the binding, patch 3 adds the driver.
The series is based on linux-pinctrl/for-next, as it depends on the
per-SoC driver split and on the CHIP SCU lookup by "airoha,chip-scu"
phandle that landed there.
Tested on a DASAN H660GM-A (EN7528, Airtel), booting OpenWrt.
Changes in v2:
- 2/3: move patternProperties after properties, and allOf to the end before
additionalProperties (Krzysztof Kozlowski).
- Rebased on linux-pinctrl/for-next.
- Link to v1:
https://lore.kernel.org/linux-gpio/cover.1786262697.git.naseefkm@gmail.com/
Ahmed Naseef (2):
pinctrl: airoha: limit GPIO interrupts to interrupt-capable pins
dt-bindings: pinctrl: Add EcoNet EN7528 pin controller
Benjamin Larsson (1):
pinctrl: airoha: add support of en7528 SoC
.../pinctrl/econet,en7528-pinctrl.yaml | 190 +++
drivers/pinctrl/airoha/Kconfig | 15 +-
drivers/pinctrl/airoha/Makefile | 1 +
drivers/pinctrl/airoha/airoha-common.h | 3 +
drivers/pinctrl/airoha/pinctrl-airoha.c | 33 +-
drivers/pinctrl/airoha/pinctrl-an7563.c | 1 +
drivers/pinctrl/airoha/pinctrl-an7581.c | 1 +
drivers/pinctrl/airoha/pinctrl-an7583.c | 1 +
drivers/pinctrl/airoha/pinctrl-en7523.c | 1 +
drivers/pinctrl/airoha/pinctrl-en7528.c | 1204 +++++++++++++++++
10 files changed, 1443 insertions(+), 7 deletions(-)
create mode 100644 Documentation/devicetree/bindings/pinctrl/econet,en7528-pinctrl.yaml
create mode 100644 drivers/pinctrl/airoha/pinctrl-en7528.c
Range-diff against v1:
1: 5a7f97adbca7 ! 1: 420a5e385cf7 pinctrl: airoha: limit GPIO interrupts to interrupt-capable pins
@@ Commit message
instead of deferring the failure to request_irq().
Signed-off-by: Ahmed Naseef <naseefkm@gmail.com>
+ Reviewed-by: Benjamin Larsson <benjamin.larsson@genexis.eu>
## drivers/pinctrl/airoha/airoha-common.h ##
@@ drivers/pinctrl/airoha/airoha-common.h: struct airoha_pinctrl {
2: 7e6150b186c2 ! 2: c20005a81b40 dt-bindings: pinctrl: Add EcoNet EN7528 pin controller
@@ Documentation/devicetree/bindings/pinctrl/econet,en7528-pinctrl.yaml (new)
+ '#interrupt-cells':
+ const: 2
+
-+allOf:
-+ - $ref: pinctrl.yaml#
-+
-+required:
-+ - compatible
-+ - airoha,chip-scu
-+ - interrupts
-+ - gpio-controller
-+ - gpio-ranges
-+ - "#gpio-cells"
-+ - interrupt-controller
-+ - "#interrupt-cells"
-+
+patternProperties:
+ '-pins$':
+ type: object
@@ Documentation/devicetree/bindings/pinctrl/econet,en7528-pinctrl.yaml (new)
+
+ additionalProperties: false
+
++required:
++ - compatible
++ - airoha,chip-scu
++ - interrupts
++ - gpio-controller
++ - gpio-ranges
++ - "#gpio-cells"
++ - interrupt-controller
++ - "#interrupt-cells"
++
++allOf:
++ - $ref: pinctrl.yaml#
++
+additionalProperties: false
+
+examples:
3: c3b785d8463e = 3: ea5b2ce92136 pinctrl: airoha: add support of en7528 SoC
base-commit: d067f0f4c96cb5402a111cf649b7bf9c5771ec74
--
2.34.1
next reply other threads:[~2026-08-28 15:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 15:35 Ahmed Naseef [this message]
2026-08-28 15:35 ` [PATCH v2 1/3] pinctrl: airoha: limit GPIO interrupts to interrupt-capable pins Ahmed Naseef
2026-08-28 15:48 ` sashiko-bot
2026-08-28 15:35 ` [PATCH v2 2/3] dt-bindings: pinctrl: Add EcoNet EN7528 pin controller Ahmed Naseef
2026-08-28 15:51 ` Conor Dooley
2026-08-29 11:47 ` Ahmed Naseef
2026-08-28 15:35 ` [PATCH v2 3/3] pinctrl: airoha: add support of en7528 SoC Ahmed Naseef
2026-08-28 15:48 ` sashiko-bot
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=cover.1787931313.git.naseefkm@gmail.com \
--to=naseefkm@gmail.com \
--cc=ansuelsmth@gmail.com \
--cc=benjamin.larsson@genexis.eu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lorenzo@kernel.org \
--cc=mikhail.kshevetskiy@iopsys.eu \
--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