From: Rob Herring <robh@kernel.org>
To: Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Marc Zyngier <maz@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/5] dt-bindings: interrupt-controller: Update STM32 EXTI interrupt controller
Date: Thu, 16 Dec 2021 14:15:14 -0600 [thread overview]
Message-ID: <YbueUmqyzwS9rOu5@robh.at.kernel.org> (raw)
In-Reply-To: <20211215105847.2328-2-alexandre.torgue@foss.st.com>
On Wed, Dec 15, 2021 at 11:58:43AM +0100, Alexandre Torgue wrote:
> Document new entry "st,exti-mapping" which links EXTI lines with GIC
> interrupt lines and add an include file to define EXTI interrupt type.
>
> Signed-off-by: Alexandre Torgue <alexandre.torgue@foss.st.com>
>
> diff --git a/Documentation/devicetree/bindings/interrupt-controller/st,stm32-exti.yaml b/Documentation/devicetree/bindings/interrupt-controller/st,stm32-exti.yaml
> index d19c881b4abc..e08bb51e97a8 100644
> --- a/Documentation/devicetree/bindings/interrupt-controller/st,stm32-exti.yaml
> +++ b/Documentation/devicetree/bindings/interrupt-controller/st,stm32-exti.yaml
> @@ -41,6 +41,17 @@ properties:
> description:
> Interrupts references to primary interrupt controller
>
> + st,exti-mapping:
> + $ref: "/schemas/types.yaml#/definitions/uint32-matrix"
> + description: |
> + Define mapping between EXTI lines and GIC irq lines. Should be:
> + st,exti-mapping = <EXTI_LINE GIC_IRQ EXTI_TYPE>, ...;
> + With:
> + - EXTI_LINE: EXTI line number.
> + - GIC_IRQ: GIC IRQ associated to the EXTI line.
> + - EXTI_TYPE: STM32_EXTI_TYPE_CONFIGURABLE or STM32_EXTI_TYPE_DIRECT.
> + Defined in include/dt-bindings/interrupt-controller/stm32-exti.h
No custom properties for this. See[1][2][3].
Rob
[1] https://lore.kernel.org/all/20211122103032.517923-1-maz@kernel.org/
[2] https://lore.kernel.org/all/87k0g8jlmg.wl-maz@kernel.org/
[3] https://lore.kernel.org/all/CAL_JsqK2Shj6smam7HgNAmy3UG+vVQPkU3Q0OjyEHOEJB45n0A@mail.gmail.com/
next prev parent reply other threads:[~2021-12-16 20:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 10:58 [PATCH v2 0/5] Add STM32MP13 EXTI support Alexandre Torgue
2021-12-15 10:58 ` [PATCH v2 1/5] dt-bindings: interrupt-controller: Update STM32 EXTI interrupt controller Alexandre Torgue
2021-12-16 20:15 ` Rob Herring [this message]
2021-12-17 13:39 ` Alexandre TORGUE
2021-12-20 12:34 ` Marc Zyngier
2022-01-04 17:14 ` Alexandre TORGUE
2021-12-15 10:58 ` [PATCH v2 2/5] irqchip/stm32: use device tree to define EXTI-GIC mapping Alexandre Torgue
2021-12-15 10:58 ` [PATCH v2 3/5] dt-bindings: interrupt-controller: stm32-exti: document st,stm32mp13-exti Alexandre Torgue
2021-12-16 20:15 ` Rob Herring
2021-12-15 10:58 ` [PATCH v2 4/5] irqchip/stm32-exti: add STM32MP13 support Alexandre Torgue
2021-12-15 10:58 ` [PATCH v2 5/5] ARM: dts: stm32: Enable EXTI on stm32mp13 Alexandre Torgue
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=YbueUmqyzwS9rOu5@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=maz@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;
as well as URLs for NNTP newsgroup(s).