From: Alexandre Torgue <alexandre.torgue@st.com>
To: Benjamin Gaignard <benjamin.gaignard@st.com>,
<robh+dt@kernel.org>, <mark.rutland@arm.com>
Cc: <linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] ARM: dts: stm32: remove useless clock-names from RTC node on stm32f746
Date: Mon, 9 Dec 2019 15:09:52 +0100 [thread overview]
Message-ID: <e1c2fe53-1b63-9b66-b48f-0c4dcc5e84ae@st.com> (raw)
In-Reply-To: <20191202145604.28872-2-benjamin.gaignard@st.com>
Hi Benjamin,
On 12/2/19 3:56 PM, Benjamin Gaignard wrote:
> On stm32f7 family RTC node doesn't need clock-names property.
>
> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com>
> ---
> arch/arm/boot/dts/stm32f746.dtsi | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/stm32f746.dtsi b/arch/arm/boot/dts/stm32f746.dtsi
> index d26f93f8b9c2..3a8e2dc1978c 100644
> --- a/arch/arm/boot/dts/stm32f746.dtsi
> +++ b/arch/arm/boot/dts/stm32f746.dtsi
> @@ -300,7 +300,6 @@
> compatible = "st,stm32-rtc";
> reg = <0x40002800 0x400>;
> clocks = <&rcc 1 CLK_RTC>;
> - clock-names = "ck_rtc";
> assigned-clocks = <&rcc 1 CLK_RTC>;
> assigned-clock-parents = <&rcc 1 CLK_LSE>;
> interrupt-parent = <&exti>;
>
Applied on stm32-next.
Thanks.
Alex
next prev parent reply other threads:[~2019-12-09 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 14:56 [PATCH 1/3] ARM: dts: stm32: remove useless clock-names from RTC node on stm32f429 Benjamin Gaignard
2019-12-02 14:56 ` [PATCH 2/3] ARM: dts: stm32: remove useless clock-names from RTC node on stm32f746 Benjamin Gaignard
2019-12-09 14:09 ` Alexandre Torgue [this message]
2019-12-09 14:07 ` [PATCH 1/3] ARM: dts: stm32: remove useless clock-names from RTC node on stm32f429 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=e1c2fe53-1b63-9b66-b48f-0c4dcc5e84ae@st.com \
--to=alexandre.torgue@st.com \
--cc=benjamin.gaignard@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=mark.rutland@arm.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).