From: Alexandre Torgue <alexandre.torgue@st.com>
To: Arnaud Pouliquen <arnaud.pouliquen@st.com>,
Rob Herring <robh@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: Fabien Dessenne <fabien.dessenne@st.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 v2] ARM: dts: stm32: add cortex-M4 pdds management in Cortex-M4 node
Date: Tue, 28 Apr 2020 18:30:46 +0200 [thread overview]
Message-ID: <21895154-7930-8354-0ddb-5c646cf6840e@st.com> (raw)
In-Reply-To: <20200401150339.7933-1-arnaud.pouliquen@st.com>
Hi Arnaud
On 4/1/20 5:03 PM, Arnaud Pouliquen wrote:
> Add declarations related to the syscon pdds for deep sleep management.
>
> Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@st.com>
> ---
> v2: patch rebasing
>
> arch/arm/boot/dts/stm32mp151.dtsi | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/arch/arm/boot/dts/stm32mp151.dtsi b/arch/arm/boot/dts/stm32mp151.dtsi
> index 5260818543e5..a40772eac487 100644
> --- a/arch/arm/boot/dts/stm32mp151.dtsi
> +++ b/arch/arm/boot/dts/stm32mp151.dtsi
> @@ -1124,6 +1124,11 @@
> };
> };
>
> + pwr_mcu: pwr_mcu@50001014 {
> + compatible = "syscon";
> + reg = <0x50001014 0x4>;
> + };
> +
> exti: interrupt-controller@5000d000 {
> compatible = "st,stm32mp1-exti", "syscon";
> interrupt-controller;
> @@ -1700,6 +1705,7 @@
> resets = <&rcc MCU_R>;
> st,syscfg-holdboot = <&rcc 0x10C 0x1>;
> st,syscfg-tz = <&rcc 0x000 0x1>;
> + st,syscfg-pdds = <&pwr_mcu 0x0 0x1>;
> status = "disabled";
> };
> };
>
Applied on stm32-next.
Thanks.
Alex
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-04-28 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 15:03 [PATCH v2] ARM: dts: stm32: add cortex-M4 pdds management in Cortex-M4 node Arnaud Pouliquen
2020-04-28 16:30 ` 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=21895154-7930-8354-0ddb-5c646cf6840e@st.com \
--to=alexandre.torgue@st.com \
--cc=arnaud.pouliquen@st.com \
--cc=devicetree@vger.kernel.org \
--cc=fabien.dessenne@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mark.rutland@arm.com \
--cc=robh@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).