From: mcoquelin.stm32@gmail.com (Maxime Coquelin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 4/4] ARM: dts: stm32f429: Adopt STM32F4 clock driver
Date: Sat, 30 May 2015 11:38:47 +0200 [thread overview]
Message-ID: <55698527.1050504@gmail.com> (raw)
In-Reply-To: <1432972448-10332-5-git-send-email-daniel.thompson@linaro.org>
On 05/30/2015 09:54 AM, Daniel Thompson wrote:
> New bindings and driver have been created for STM32F42xxx series parts.
> This patch integrates these changes.
>
> Note: Earlier device tree blobs (those without st,stm32f42xxx
> compatibles for the rcc) could still be used to boot basic
> systems. Such systems rely on the bootloader to configure the
> clock gates for vital periperhals.
>
> Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>
> ---
> arch/arm/boot/dts/stm32f429-disco.dts | 4 ++
> arch/arm/boot/dts/stm32f429.dtsi | 79 +++++++++++------------------------
> 2 files changed, 28 insertions(+), 55 deletions(-)
>
>
Reviewed-by: Maxime Coquelin <mcoquelin.stm32@gmail.com>
Thanks!
Maxime
next prev parent reply other threads:[~2015-05-30 9:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 20:41 [RFC PATCH 0/3] clk: stm32: Add clock driver for STM32F4[23]xxx devices Daniel Thompson
2015-05-22 20:41 ` [RFC PATCH 1/3] dt-bindings: Document the STM32F4 clock bindings Daniel Thompson
2015-05-22 20:41 ` [RFC PATCH 2/3] clk: stm32: Add clock driver for STM32F4[23]xxx devices Daniel Thompson
2015-06-04 22:07 ` Stephen Boyd
2015-06-05 9:36 ` Daniel Thompson
2015-06-06 0:10 ` Stephen Boyd
2015-05-22 20:41 ` [RFC PATCH 3/3] ARM: dts: stm32f429: Adopt STM32F4 clock driver Daniel Thompson
2015-05-26 16:41 ` [RFC PATCH 0/3] clk: stm32: Add clock driver for STM32F4[23]xxx devices Maxime Coquelin
2015-05-27 8:36 ` Daniel Thompson
2015-05-30 7:54 ` [PATCH v2 0/4] " Daniel Thompson
2015-05-30 7:54 ` [PATCH v2 1/4] ARM: stm32: Enable clock source Daniel Thompson
2015-05-30 7:54 ` [PATCH v2 2/4] dt-bindings: Document the STM32F4 clock bindings Daniel Thompson
2015-05-30 9:21 ` Maxime Coquelin
2015-06-01 7:46 ` Daniel Thompson
2015-05-30 7:54 ` [PATCH v2 3/4] clk: stm32: Add clock driver for STM32F4[23]xxx devices Daniel Thompson
2015-05-30 9:15 ` Maxime Coquelin
2015-06-01 7:18 ` Daniel Thompson
2015-05-30 7:54 ` [PATCH v2 4/4] ARM: dts: stm32f429: Adopt STM32F4 clock driver Daniel Thompson
2015-05-30 9:38 ` Maxime Coquelin [this message]
2015-05-30 8:40 ` [PATCH v2 0/4] clk: stm32: Add clock driver for STM32F4[23]xxx devices Maxime Coquelin
2015-06-10 20:09 ` [PATCH v3 0/3] " Daniel Thompson
2015-06-10 20:09 ` [PATCH v3 1/3] dt-bindings: Document the STM32F4 clock bindings Daniel Thompson
2015-06-12 7:25 ` Maxime Coquelin
2015-06-22 22:47 ` Stephen Boyd
2015-06-10 20:09 ` [PATCH v3 2/3] clk: stm32: Add clock driver for STM32F4[23]xxx devices Daniel Thompson
2015-06-22 22:48 ` Stephen Boyd
2015-06-22 23:21 ` Stephen Boyd
2015-06-23 8:25 ` Daniel Thompson
2015-06-10 20:09 ` [PATCH v3 3/3] ARM: dts: stm32f429: Adopt STM32F4 clock driver Daniel Thompson
2015-07-07 9:38 ` Maxime Coquelin
2015-06-22 22:48 ` [PATCH v3 0/3] clk: stm32: Add clock driver for STM32F4[23]xxx devices Stephen Boyd
2015-06-23 8:22 ` Daniel Thompson
2015-06-23 9:24 ` Maxime Coquelin
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=55698527.1050504@gmail.com \
--to=mcoquelin.stm32@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).