From: Alexandre Torgue <alexandre.torgue@st.com>
To: Gabriel Fernandez <gabriel.fernandez@st.com>,
michael turquette <mturquette@baylibre.com>,
stephen boyd <sboyd@kernel.org>, rob herring <robh+dt@kernel.org>,
mark rutland <mark.rutland@arm.com>,
maxime coquelin <mcoquelin.stm32@gmail.com>
Cc: <linux-clk@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH 2/2] ARM: dts: stm32: Enable STM32F769 clock driver
Date: Wed, 10 Apr 2019 15:40:59 +0200 [thread overview]
Message-ID: <5d6bc520-caa1-9dca-539d-e270562c4873@st.com> (raw)
In-Reply-To: <20190405075332.28530-3-gabriel.fernandez@st.com>
Hi Gabriel
On 4/5/19 9:53 AM, Gabriel Fernandez wrote:
> This patch enables clocks for STM32F769 boards.
>
> Signed-off-by: Gabriel Fernandez <gabriel.fernandez@st.com>
> ---
> arch/arm/boot/dts/stm32f769-disco.dts | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/arm/boot/dts/stm32f769-disco.dts b/arch/arm/boot/dts/stm32f769-disco.dts
> index 3c7216844a9b..6f1d0ac8c31c 100644
> --- a/arch/arm/boot/dts/stm32f769-disco.dts
> +++ b/arch/arm/boot/dts/stm32f769-disco.dts
> @@ -102,6 +102,10 @@
> };
> };
>
> +&rcc {
> + compatible = "st,stm32f769-rcc", "st,stm32f746-rcc", "st,stm32-rcc";
> +};
> +
> &cec {
> pinctrl-0 = <&cec_pins_a>;
> pinctrl-names = "default";
>
Even if driver part is not yet merged, this DT part can be taken as we
will run with "st,stm32f746-rcc" compatible (the current one).
So:
Applied on stm32-next.
Thanks.
Alex
prev parent reply other threads:[~2019-04-10 13:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 7:53 [PATCH 0/2] clk: stm32: STM32F769 clocks Gabriel Fernandez
2019-04-05 7:53 ` [PATCH 1/2] clk: stm32: Introduce clocks of STM32F769 board Gabriel Fernandez
2019-04-25 18:47 ` Stephen Boyd
2019-04-05 7:53 ` [PATCH 2/2] ARM: dts: stm32: Enable STM32F769 clock driver Gabriel Fernandez
2019-04-10 13:40 ` 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=5d6bc520-caa1-9dca-539d-e270562c4873@st.com \
--to=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=gabriel.fernandez@st.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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).