From: Sven Peter <sven@kernel.org>
To: Janne Grunau <j@jannau.net>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Neal Gompa <neal@gompa.dev>, Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
asahi@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: interrupt-controller: apple,aic2: Add AICv3
Date: Fri, 6 Feb 2026 15:44:30 +0100 [thread overview]
Message-ID: <0cc9bd0a-958b-4e63-b2ed-959a3ea43440@kernel.org> (raw)
In-Reply-To: <20260205221918.GA71415@robin.jannau.net>
On 05.02.26 23:19, Janne Grunau wrote:
> On Thu, Feb 05, 2026 at 07:01:51PM +0100, Sven Peter wrote:
>> Hi,
>>
>> On 05.02.26 13:50, Krzysztof Kozlowski wrote:
>>> On Wed, Jan 28, 2026 at 09:57:08AM +0100, Janne Grunau wrote:
>>>> AIC version 3 as found on the Apple M3 (t8122) is very similar to AICv2
>>>> in its base functionality. It can use the same device tree bindings as
>>>> AICv2 so add it to the AICv2 bindings.
>>>> This interrupt controller is used on all Apple SoCs starting with M3 up
>>>> to at least M5.
>>>> The only apparent difference is the increased IRQ config offset. Apple's
>>>> device tree codes this new offset as property of the "aic" node but the
>>>> value stayed constant for all SoCs with "aic,3". Since the SoC specific
>>>> compatible "apple,t8122-aic3" will be used in the driver this offset can
>>>> remain a driver implementation detail.
>>>>
>>>> Signed-off-by: Janne Grunau <j@jannau.net>
>>>> ---
>>>> .../bindings/interrupt-controller/apple,aic2.yaml | 45 +++++++++++++++++-----
>>>> 1 file changed, 36 insertions(+), 9 deletions(-)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/interrupt-controller/apple,aic2.yaml b/Documentation/devicetree/bindings/interrupt-controller/apple,aic2.yaml
>>>> index ee5a0dfff437816056bda0de5523bf38be4f49ba..a6e2251fcc111340c0a27ab6912452f6b1255be2 100644
>>>> --- a/Documentation/devicetree/bindings/interrupt-controller/apple,aic2.yaml
>>>> +++ b/Documentation/devicetree/bindings/interrupt-controller/apple,aic2.yaml
>>>> @@ -4,10 +4,10 @@
>>>> $id: http://devicetree.org/schemas/interrupt-controller/apple,aic2.yaml#
>>>> $schema: http://devicetree.org/meta-schemas/core.yaml#
>>>>
>>>> -title: Apple Interrupt Controller 2
>>>> +title: Apple Interrupt Controller 2 and 3
>>>>
>>>> maintainers:
>>>> - - Hector Martin <marcan@marcan.st>
>>>> + - Janne Grunau <j@jannau.net>
>>>>
>>>> description: |
>>>> The Apple Interrupt Controller 2 is a simple interrupt controller present on
>>>> @@ -28,14 +28,24 @@ description: |
>>>> which do not go through a discrete interrupt controller. It also handles
>>>> FIQ-based Fast IPIs.
>>>>
>>>> + The Apple Interrupt Controller 3 is in its base functionality very similar to
>>>> + the Apple Interrupt Controller 2 and uses the same device tree bindings. It is
>>>> + found on Apple ARM SoCs platforms starting with t8122 (M3).
>>>> +
>>>> properties:
>>>> compatible:
>>>> - items:
>>>> - - enum:
>>>> - - apple,t8112-aic
>>>> - - apple,t6000-aic
>>>> - - apple,t6020-aic
>>>> - - const: apple,aic2
>>>> + oneOf:
>>>> + - items:
>>>> + - enum:
>>>> + - apple,t8112-aic
>>>> + - apple,t6000-aic
>>>> + - apple,t6020-aic
>>>
>>> If you are re-shuffling these, you can as well sort alphanumerically.
>>
>> I don't have a strong opinion here but the last time this came up we
>> agreed that we'd go with release order IIRC for consistency since that
>> order is used in every other binding for this platform.
>
> The intended scheme as documented in some commit messages is first base
> Mx SoCs in release order and then Mx Pro/Max/Ultra SoCs in release
> order. This scheme isn't used consistently though. I think I fixed that
> in one or two bindings already but there are other using a different
> order.
> I think these unecessarily complex rules are guaranteed to lead to
> inconsistencies. I'll resort the entries alphabetically as that's the
> only rule with a chance of consistent use.
Sure, I'm totally fine with just using alphanumeric order everywhere as
well.
Sven
next prev parent reply other threads:[~2026-02-06 14:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 8:57 [PATCH v2 0/2] Add Apple interrupt controller 3 support Janne Grunau
2026-01-28 8:57 ` [PATCH v2 1/2] dt-bindings: interrupt-controller: apple,aic2: Add AICv3 Janne Grunau
2026-01-30 8:03 ` Thomas Gleixner
2026-02-05 12:50 ` Krzysztof Kozlowski
2026-02-05 18:01 ` Sven Peter
2026-02-05 22:19 ` Janne Grunau
2026-02-06 14:44 ` Sven Peter [this message]
2026-01-28 8:57 ` [PATCH v2 2/2] irqchip/apple-aic: Add support for "apple,t8122-aic3" Janne Grunau
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=0cc9bd0a-958b-4e63-b2ed-959a3ea43440@kernel.org \
--to=sven@kernel.org \
--cc=asahi@lists.linux.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j@jannau.net \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neal@gompa.dev \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
/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