From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ahmed Naseef <naseefkm@gmail.com>
Cc: linux-gpio@vger.kernel.org,
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: Re: [PATCH 2/3] dt-bindings: pinctrl: Add EcoNet EN7528 pin controller
Date: Wed, 9 Sep 2026 08:11:29 +0200 [thread overview]
Message-ID: <219e88c6-5f49-4db3-8a30-54d387711fcc@kernel.org> (raw)
In-Reply-To: <apGcOAUpb6XZ2Iud@DESKTOP-TIT0J8O.localdomain>
On 28/08/2026 16:33, Ahmed Naseef wrote:
> On Fri, Aug 28, 2026 at 08:59:57AM +0200, Krzysztof Kozlowski wrote:
>> On Sun, Aug 09, 2026 at 12:04:59PM +0400, Ahmed Naseef wrote:
>>> +maintainers:
>>> + - Lorenzo Bianconi <lorenzo@kernel.org>
>>> +
>>> +description:
>>> + The EcoNet EN7528 pin controller is used to control SoC pins. It shares the
>>> + IP with the Airoha pin controllers, but its IOMUX and pin configuration
>>> + registers have a different layout.
>>> +
>>> +properties:
>>> + compatible:
>>> + const: econet,en7528-pinctrl
>>> +
>>> + airoha,chip-scu:
>>> + description: phandle to the chip SCU syscon
>>> + $ref: /schemas/types.yaml#/definitions/phandle
>>
>> If the entire address space is part of the SCU, then this device should
>> be part of the SCU, e.g. its subnode.
>
> It is not: the registers are split over two blocks. The GPIO, interrupt
> and PWM flash-mode registers are in the block the node sits under, and
> the IOMUX and pin configuration registers are in the SCU. Both are
> needed, so whichever of the two is the parent, the other one has to come
> in by phandle.
Sure, one is parent and other is sibling. This is standard. But
non-standard is to claim to have no MMIO but then get that MMIO from
someone else...
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-09-09 6:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-09 8:04 [PATCH 0/3] pinctrl: airoha: add EcoNet EN7528 pin controller support Ahmed Naseef
2026-08-09 8:04 ` [PATCH 1/3] pinctrl: airoha: limit GPIO interrupts to interrupt-capable pins Ahmed Naseef
2026-08-09 8:18 ` sashiko-bot
2026-08-14 19:38 ` Benjamin Larsson
2026-08-18 5:17 ` Ahmed Naseef
2026-08-09 8:04 ` [PATCH 2/3] dt-bindings: pinctrl: Add EcoNet EN7528 pin controller Ahmed Naseef
2026-08-09 8:15 ` sashiko-bot
2026-08-28 7:02 ` Krzysztof Kozlowski
2026-08-28 6:59 ` Krzysztof Kozlowski
2026-08-28 14:33 ` Ahmed Naseef
2026-09-09 6:11 ` Krzysztof Kozlowski [this message]
2026-08-09 8:05 ` [PATCH 3/3] pinctrl: airoha: add support of en7528 SoC Ahmed Naseef
2026-08-10 7:23 ` [PATCH 0/3] pinctrl: airoha: add EcoNet EN7528 pin controller support Linus Walleij
2026-08-10 7:27 ` Christian Marangi (Ansuel)
2026-08-11 6:17 ` 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=219e88c6-5f49-4db3-8a30-54d387711fcc@kernel.org \
--to=krzk@kernel.org \
--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=naseefkm@gmail.com \
--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