From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Fabien Dessenne <fabien.dessenne@foss.st.com>,
Rob Herring <robh+dt@kernel.org>,
Jassi Brar <jassisinghbrar@gmail.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
<linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>
Subject: Re: [PATCH 2/2] ARM: dts: stm32: remove the IPCC "wakeup" IRQ on stm32mp151
Date: Mon, 13 Jun 2022 09:39:47 +0200 [thread overview]
Message-ID: <5b3e7b59-5853-a466-11de-22ef6e80b0d6@foss.st.com> (raw)
In-Reply-To: <20220503145606.525875-1-fabien.dessenne@foss.st.com>
Hi Fabien
On 5/3/22 16:56, Fabien Dessenne wrote:
> The stm32 ipcc mailbox driver supports only two interrupts (rx and tx), so
> remove the unsupported "wakeup" one.
> Note that the EXTI interrupt 61 has two roles : it is hierarchically linked
> to the GIC IPCC "rx" interrupt, and it acts as a wakeup source.
>
> Signed-off-by: Fabien Dessenne <fabien.dessenne@foss.st.com>
> ---
> arch/arm/boot/dts/stm32mp151.dtsi | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm/boot/dts/stm32mp151.dtsi b/arch/arm/boot/dts/stm32mp151.dtsi
> index 7fdc324b3cf9..edc0a1641c7b 100644
> --- a/arch/arm/boot/dts/stm32mp151.dtsi
> +++ b/arch/arm/boot/dts/stm32mp151.dtsi
> @@ -1117,10 +1117,9 @@ ipcc: mailbox@4c001000 {
> reg = <0x4c001000 0x400>;
> st,proc-id = <0>;
> interrupts-extended =
> - <&intc GIC_SPI 100 IRQ_TYPE_LEVEL_HIGH>,
> - <&intc GIC_SPI 101 IRQ_TYPE_LEVEL_HIGH>,
> - <&exti 61 1>;
> - interrupt-names = "rx", "tx", "wakeup";
> + <&exti 61 1>,
> + <&intc GIC_SPI 101 IRQ_TYPE_LEVEL_HIGH>;
> + interrupt-names = "rx", "tx";
> clocks = <&rcc IPCC>;
> wakeup-source;
> status = "disabled";
Applied on stm32-next.
Thanks.
Alex
prev parent reply other threads:[~2022-06-13 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 14:56 [PATCH 2/2] ARM: dts: stm32: remove the IPCC "wakeup" IRQ on stm32mp151 Fabien Dessenne
2022-06-13 7:39 ` 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=5b3e7b59-5853-a466-11de-22ef6e80b0d6@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=fabien.dessenne@foss.st.com \
--cc=jassisinghbrar@gmail.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).