From: Gabriel Fernandez <gabriel.fernandez@st.com>
To: 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>,
alexandre torgue <alexandre.torgue@st.com>
Cc: <linux-clk@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
Gabriel Fernandez <gabriel.fernandez@st.com>
Subject: [PATCH 0/2] clk: stm32: STM32F769 clocks
Date: Fri, 5 Apr 2019 09:53:30 +0200 [thread overview]
Message-ID: <20190405075332.28530-1-gabriel.fernandez@st.com> (raw)
STM32F769 board is a derived of STM32F746 board.
Concerning clocks, main differences are:
- new source clock for SAI1 and SAI2 (HSI or HSE)
- Add DFSDM & DSI clock
Gabriel Fernandez (2):
clk: stm32: Introduce clocks of STM32F769 board
ARM: dts: stm32: Enable STM32F769 clock driver
.../bindings/clock/st,stm32-rcc.txt | 6 +
arch/arm/boot/dts/stm32f769-disco.dts | 4 +
drivers/clk/clk-stm32f4.c | 307 +++++++++++++++++-
include/dt-bindings/clock/stm32fx-clock.h | 7 +-
4 files changed, 314 insertions(+), 10 deletions(-)
--
2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Gabriel Fernandez <gabriel.fernandez@st.com>
To: 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>,
alexandre torgue <alexandre.torgue@st.com>
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
Gabriel Fernandez <gabriel.fernandez@st.com>
Subject: [PATCH 0/2] clk: stm32: STM32F769 clocks
Date: Fri, 5 Apr 2019 09:53:30 +0200 [thread overview]
Message-ID: <20190405075332.28530-1-gabriel.fernandez@st.com> (raw)
STM32F769 board is a derived of STM32F746 board.
Concerning clocks, main differences are:
- new source clock for SAI1 and SAI2 (HSI or HSE)
- Add DFSDM & DSI clock
Gabriel Fernandez (2):
clk: stm32: Introduce clocks of STM32F769 board
ARM: dts: stm32: Enable STM32F769 clock driver
.../bindings/clock/st,stm32-rcc.txt | 6 +
arch/arm/boot/dts/stm32f769-disco.dts | 4 +
drivers/clk/clk-stm32f4.c | 307 +++++++++++++++++-
include/dt-bindings/clock/stm32fx-clock.h | 7 +-
4 files changed, 314 insertions(+), 10 deletions(-)
--
2.17.1
next reply other threads:[~2019-04-05 7:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 7:53 Gabriel Fernandez [this message]
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-05 7:53 ` Gabriel Fernandez
2019-04-25 18:47 ` Stephen Boyd
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-05 7:53 ` Gabriel Fernandez
2019-04-10 13:40 ` Alexandre Torgue
2019-04-10 13:40 ` 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=20190405075332.28530-1-gabriel.fernandez@st.com \
--to=gabriel.fernandez@st.com \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.