From: Rob Herring <robh@kernel.org>
To: Hector Martin <marcan@marcan.st>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Marc Zyngier <maz@kernel.org>, Sven Peter <sven@svenpeter.dev>,
Alyssa Rosenzweig <alyssa@rosenzweig.io>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/6] dt-bindings: interrupt-controller: apple,aic: Add apple,aic2 support
Date: Thu, 9 Dec 2021 11:28:32 -0600 [thread overview]
Message-ID: <YbI8wBS2mrETiTfw@robh.at.kernel.org> (raw)
In-Reply-To: <20211209043249.65474-2-marcan@marcan.st>
On Thu, Dec 09, 2021 at 01:32:44PM +0900, Hector Martin wrote:
> This new incompatible revision of the AIC peripheral introduces
> multi-die support. To handle that, we introduce an optional
> 4-argument interrupt-cells form.
>
> Also add an apple,event-reg property to specify the offset of the event
> register. Inexplicably, the capability registers allow us to compute
> other register offsets, but not this one. This allows us to keep
> forward-compatibility with future SoCs that will likely implement
> different die counts, thus shifting the event register. Apple do the
> same thing in their device tree...
>
> Signed-off-by: Hector Martin <marcan@marcan.st>
> ---
> .../interrupt-controller/apple,aic.yaml | 62 +++++++++++++++----
> 1 file changed, 49 insertions(+), 13 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/interrupt-controller/apple,aic.yaml b/Documentation/devicetree/bindings/interrupt-controller/apple,aic.yaml
> index 97359024709a..6a8dd213e59a 100644
> --- a/Documentation/devicetree/bindings/interrupt-controller/apple,aic.yaml
> +++ b/Documentation/devicetree/bindings/interrupt-controller/apple,aic.yaml
> @@ -18,38 +18,44 @@ description: |
>
> - Level-triggered hardware IRQs wired to SoC blocks
> - Single mask bit per IRQ
> - - Per-IRQ affinity setting
> + - Per-IRQ affinity setting (AICv1 only)
> - Automatic masking on event delivery (auto-ack)
> - Software triggering (ORed with hw line)
> - 2 per-CPU IPIs (meant as "self" and "other", but they are interchangeable
> - if not symmetric)
> + if not symmetric) (AICv1 only)
> - Automatic prioritization (single event/ack register per CPU, lower IRQs =
> higher priority)
> - Automatic masking on ack
> - - Default "this CPU" register view and explicit per-CPU views
> + - Default "this CPU" register view and explicit per-CPU views (AICv1 only)
>
> This device also represents the FIQ interrupt sources on platforms using AIC,
> - which do not go through a discrete interrupt controller.
> -
> -allOf:
> - - $ref: /schemas/interrupt-controller.yaml#
> + which do not go through a discrete interrupt controller. It also handles
> + FIQ-based Fast IPIs on supported chips.
>
> properties:
> compatible:
> - items:
> - - const: apple,t8103-aic
> - - const: apple,aic
> + oneOf:
> + - items:
> + - const: apple,t8103-aic
> + - const: apple,aic
> + - items:
> + - const: apple,t6000-aic
> + - const: apple,aic2
>
> interrupt-controller: true
>
> '#interrupt-cells':
> - const: 3
> + minimum: 3
> + maximum: 4
> description: |
> The 1st cell contains the interrupt type:
> - 0: Hardware IRQ
> - 1: FIQ
>
> - The 2nd cell contains the interrupt number.
> + The optional 2nd cell contains the die ID (apple,aic2 only).
> + If not present, it defaults to 0.
> +
> + The next cell contains the interrupt number.
> - HW IRQs: interrupt number
> - FIQs:
> - 0: physical HV timer
> @@ -57,7 +63,7 @@ properties:
> - 2: physical guest timer
> - 3: virtual guest timer
>
> - The 3rd cell contains the interrupt flags. This is normally
> + The last cell contains the interrupt flags. This is normally
> IRQ_TYPE_LEVEL_HIGH (4).
>
> reg:
> @@ -68,6 +74,13 @@ properties:
> power-domains:
> maxItems: 1
>
> + apple,event-reg:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description:
> + Specifies the offset of the event register, which lies after all the
> + implemented die register sets, page aligned. This is not computable from
> + capability register values, so we have to specify it explicitly.
> +
> required:
> - compatible
> - '#interrupt-cells'
> @@ -76,6 +89,29 @@ required:
>
> additionalProperties: false
>
> +allOf:
> + - $ref: /schemas/interrupt-controller.yaml#
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - apple,aic
> + then:
> + properties:
> + '#interrupt-cells':
> + const: 3
> +
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - apple,aic2
> + then:
> + required:
> + - apple,event-reg
Is this property valid for aic1? If not, you need:
else:
not:
required:
- apple,event-reg
I tend to think you should just make this a separate document. There's
not a whole lot of sharing (compared to any other interrupt controller).
> +
> examples:
> - |
> soc {
> --
> 2.33.0
>
>
next prev parent reply other threads:[~2021-12-09 17:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 4:32 [PATCH 0/6] irqchip/apple-aic: Add support for AICv2 Hector Martin
2021-12-09 4:32 ` [PATCH 1/6] dt-bindings: interrupt-controller: apple,aic: Add apple,aic2 support Hector Martin
2021-12-09 17:28 ` Rob Herring [this message]
2021-12-11 12:28 ` Hector Martin
2021-12-11 12:44 ` Marc Zyngier
2021-12-11 12:52 ` Hector Martin
2021-12-11 12:49 ` Mark Kettenis
2021-12-09 4:32 ` [PATCH 2/6] irqchip/apple-aic: Add Fast IPI support Hector Martin
2021-12-12 12:21 ` Marc Zyngier
2021-12-18 5:31 ` Hector Martin
2021-12-20 12:43 ` Marc Zyngier
2021-12-09 4:32 ` [PATCH 3/6] irqchip/apple-aic: Switch to irq_domain_create_tree and sparse hwirqs Hector Martin
2021-12-12 14:37 ` Marc Zyngier
2021-12-18 5:36 ` Hector Martin
2021-12-09 4:32 ` [PATCH 4/6] irqchip/apple-aic: Dynamically compute register offsets Hector Martin
2021-12-12 18:26 ` Marc Zyngier
2021-12-18 5:37 ` Hector Martin
2021-12-09 4:32 ` [PATCH 5/6] irqchip/apple-aic: Support multiple dies Hector Martin
2021-12-13 16:10 ` Marc Zyngier
2021-12-18 5:39 ` Hector Martin
2021-12-20 13:38 ` Marc Zyngier
2021-12-09 4:32 ` [PATCH 6/6] irqchip/apple-aic: Add support for AICv2 Hector Martin
2021-12-12 18:47 ` Marc Zyngier
2021-12-18 6:02 ` Hector Martin
2021-12-20 13:52 ` Marc Zyngier
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=YbI8wBS2mrETiTfw@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=alyssa@rosenzweig.io \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=maz@kernel.org \
--cc=sven@svenpeter.dev \
--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;
as well as URLs for NNTP newsgroup(s).