From: Marek Vasut <marex@denx.de>
To: Alexandre TORGUE <alexandre.torgue@foss.st.com>,
linux-arm-kernel@lists.infradead.org
Cc: Antonio Borneo <antonio.borneo@foss.st.com>,
Guenter Roeck <linux@roeck-us.net>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Marc Zyngier <maz@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Richard Cochran <richardcochran@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v3] ARM: dts: stm32: Add IWDG2 EXTI interrupt mapping and mark as wakeup source
Date: Tue, 29 Oct 2024 20:07:38 +0100 [thread overview]
Message-ID: <e521394a-a7e1-495e-8a67-637f30d7866d@denx.de> (raw)
In-Reply-To: <43c2cd64-2c70-43f3-9470-b6f8bcaa8027@foss.st.com>
On 10/29/24 4:16 PM, Alexandre TORGUE wrote:
> Hi Marek
Hello Alexandre,
> On 6/23/24 21:51, Marek Vasut wrote:
>> The IWDG2 is capable of generating pre-timeout interrupt, which can be
>> used
>> to wake the system up from suspend to mem. Add the EXTI interrupt mapping
>> and mark the IWDG2 as wake up source.
>>
>> Signed-off-by: Marek Vasut <marex@denx.de>
>> ---
>> Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>
>> Cc: Antonio Borneo <antonio.borneo@foss.st.com>
>> Cc: Guenter Roeck <linux@roeck-us.net>
>> Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
>> Cc: Marc Zyngier <maz@kernel.org>
>> Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>
>> Cc: Richard Cochran <richardcochran@gmail.com>
>> Cc: Rob Herring <robh+dt@kernel.org>
>> Cc: Thomas Gleixner <tglx@linutronix.de>
>> Cc: Wim Van Sebroeck <wim@linux-watchdog.org>
>> 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: linux-watchdog@vger.kernel.org
>> ---
>> V2: No change
>> V3: No change
>> ---
>> arch/arm/boot/dts/st/stm32mp151.dtsi | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/st/stm32mp151.dtsi b/arch/arm/boot/dts/
>> st/stm32mp151.dtsi
>> index 1804e202eb425..68846699b26fd 100644
>> --- a/arch/arm/boot/dts/st/stm32mp151.dtsi
>> +++ b/arch/arm/boot/dts/st/stm32mp151.dtsi
>> @@ -355,6 +355,8 @@ iwdg2: watchdog@5a002000 {
>> reg = <0x5a002000 0x400>;
>> clocks = <&rcc IWDG2>, <&rcc CK_LSI>;
>> clock-names = "pclk", "lsi";
>> + interrupts-extended = <&exti 46 IRQ_TYPE_LEVEL_HIGH>;
>> + wakeup-source;
>> status = "disabled";
>> };
>
> Applied on stm32-next !!
> (late but applied ;))
Woohoo ! Thank you.
prev parent reply other threads:[~2024-10-29 20:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 19:51 [PATCH v3] ARM: dts: stm32: Add IWDG2 EXTI interrupt mapping and mark as wakeup source Marek Vasut
2024-06-27 10:36 ` Alexandre TORGUE
2024-10-29 15:16 ` Alexandre TORGUE
2024-10-29 19:07 ` Marek Vasut [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=e521394a-a7e1-495e-8a67-637f30d7866d@denx.de \
--to=marex@denx.de \
--cc=alexandre.torgue@foss.st.com \
--cc=antonio.borneo@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=maz@kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=richardcochran@gmail.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=wim@linux-watchdog.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).