devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Fabien Dessenne <fabien.dessenne@foss.st.com>,
	Rob Herring <robh+dt@kernel.org>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	<devicetree@vger.kernel.org>,
	<linux-stm32@st-md-mailman.stormreply.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: stm32: add EXTI interrupt-parent to pinctrl node on stm32mp131
Date: Tue, 3 May 2022 15:48:06 +0200	[thread overview]
Message-ID: <1be925e8-5eeb-2928-d9c8-95d41102ddf9@foss.st.com> (raw)
In-Reply-To: <20220503090621.483567-1-fabien.dessenne@foss.st.com>

On 5/3/22 11:06, Fabien Dessenne wrote:
> Add interrupt-parent property in pinctrl node to use GPIO as IRQ.
> 
> Signed-off-by: Amelie Delaunay <amelie.delaunay@foss.st.com>
> Signed-off-by: Fabien Dessenne <fabien.dessenne@foss.st.com>
> ---
>   arch/arm/boot/dts/stm32mp131.dtsi | 2 ++
>   1 file changed, 2 insertions(+)
> 
> diff --git a/arch/arm/boot/dts/stm32mp131.dtsi b/arch/arm/boot/dts/stm32mp131.dtsi
> index 58647396704f..f9ebc47e6421 100644
> --- a/arch/arm/boot/dts/stm32mp131.dtsi
> +++ b/arch/arm/boot/dts/stm32mp131.dtsi
> @@ -259,6 +259,8 @@ pinctrl: pinctrl@50002000 {
>   			#size-cells = <1>;
>   			compatible = "st,stm32mp135-pinctrl";
>   			ranges = <0 0x50002000 0x8400>;
> +			interrupt-parent = <&exti>;
> +			st,syscfg = <&exti 0x60 0xff>;
>   			pins-are-numbered;
>   
>   			gpioa: gpio@50002000 {

Applied on stm32-next.

Thanks.
Alex

      reply	other threads:[~2022-05-03 13:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03  9:06 [PATCH] ARM: dts: stm32: add EXTI interrupt-parent to pinctrl node on stm32mp131 Fabien Dessenne
2022-05-03 13:48 ` Alexandre TORGUE [this message]

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=1be925e8-5eeb-2928-d9c8-95d41102ddf9@foss.st.com \
    --to=alexandre.torgue@foss.st.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabien.dessenne@foss.st.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).