From: Rob Herring <robh@kernel.org>
To: Aniket Limaye <a-limaye@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
u-kumar1@ti.com, Nishanth Menon <nm@ti.com>,
Tero Kristo <kristo@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
Thomas Gleixner <tglx@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
j-mcarthur@ti.com, 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: ti,sci-intr: Per-line interrupt-types
Date: Wed, 21 Jan 2026 09:56:02 -0600 [thread overview]
Message-ID: <20260121155602.GA3196596-robh@kernel.org> (raw)
In-Reply-To: <20260120-ul-driver-i2c-j722s-v2-1-832097c6b64f@ti.com>
On Tue, Jan 20, 2026 at 04:13:46PM +0530, Aniket Limaye wrote:
> Update the bindings to allow setting per-line interrupt-types.
>
> Some Interrupt Router instances can only work with a specific trigger
> type (edge or level), while others act as simple passthroughs that
> preserve the source interrupt type unchanged.
>
> In addition to existing edge or level interrupt setting, add a third
> enum value 15 (IRQ_TYPE_DEFAULT) for "ti,intr-trigger-type" property, to
> indicate that the router acts as a passthrough. When set to 15,
> "#interrupt-cells" must be 2 to allow each interrupt source to specify
> its trigger type per-line.
>
> Signed-off-by: Aniket Limaye <a-limaye@ti.com>
> ---
> Changes in v2:
> - Reword Commit msg to better describe the patch
> - Link to v1: https://lore.kernel.org/r/20260116-ul-driver-i2c-j722s-v1-1-c28e8ba38a9e@ti.com
> ---
> .../bindings/interrupt-controller/ti,sci-intr.yaml | 42 +++++++++++++++++++---
> 1 file changed, 37 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/interrupt-controller/ti,sci-intr.yaml b/Documentation/devicetree/bindings/interrupt-controller/ti,sci-intr.yaml
> index c99cc7323c71..59c01f327f3b 100644
> --- a/Documentation/devicetree/bindings/interrupt-controller/ti,sci-intr.yaml
> +++ b/Documentation/devicetree/bindings/interrupt-controller/ti,sci-intr.yaml
> @@ -15,8 +15,7 @@ allOf:
> description: |
> The Interrupt Router (INTR) module provides a mechanism to mux M
> interrupt inputs to N interrupt outputs, where all M inputs are selectable
> - to be driven per N output. An Interrupt Router can either handle edge
> - triggered or level triggered interrupts and that is fixed in hardware.
> + to be driven per N output.
>
> Interrupt Router
> +----------------------+
> @@ -52,11 +51,12 @@ properties:
>
> ti,intr-trigger-type:
> $ref: /schemas/types.yaml#/definitions/uint32
> - enum: [1, 4]
> + enum: [1, 4, 15]
> description: |
> Should be one of the following.
> 1 = If intr supports edge triggered interrupts.
> 4 = If intr supports level triggered interrupts.
> + 15 = If intr preserves the source interrupt type.
Why do you need this property in this case? #interrupt-cells == 2 means
preserve the source type and this is redundant. Just disallow
ti,intr-trigger-type when #interrupt-cells == 2.
Rob
next prev parent reply other threads:[~2026-01-21 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 10:43 [PATCH v2 0/2] ti-sci-intr: Support level+pulse interrupt sources together Aniket Limaye
2026-01-20 10:43 ` [PATCH v2 1/2] dt-bindings: interrupt-controller: ti,sci-intr: Per-line interrupt-types Aniket Limaye
2026-01-21 15:56 ` Rob Herring [this message]
2026-01-22 11:05 ` Aniket Limaye
2026-01-20 10:43 ` [PATCH v2 2/2] irqchip/ti-sci-intr: Allow parsing interrupt-types per-line Aniket Limaye
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=20260121155602.GA3196596-robh@kernel.org \
--to=robh@kernel.org \
--cc=a-limaye@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j-mcarthur@ti.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=ssantosh@kernel.org \
--cc=tglx@kernel.org \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.