From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: <gabriel.fernandez@foss.st.com>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>
Cc: <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 0/3] SCMI Update for STM32MP15 boards
Date: Fri, 1 Jul 2022 13:44:39 +0200 [thread overview]
Message-ID: <157d783b-156a-72fb-542a-87c483ca2411@foss.st.com> (raw)
In-Reply-To: <20220624092715.1397827-1-gabriel.fernandez@foss.st.com>
Hi Gabriel
On 6/24/22 11:27, gabriel.fernandez@foss.st.com wrote:
> From: Gabriel Fernandez <gabriel.fernandez@foss.st.com>
>
> Update for SCMI version of ST boards:
> - delete fixed clocks because there are now provided by SCMI
> - add missing SCMI impact for DSI IP on DK1/ED1 STM32 board
> - fix peripheral clock for CEC
>
> Gabriel Fernandez (3):
> ARM: dts: stm32: use the correct clock source for CEC on stm32mp151
> ARM: dts: stm32: DSI should use LSE SCMI clock on DK1/ED1 STM32 board
> ARM: dts: stm32: delete fixed clock node on STM32MP15-SCMI
>
> arch/arm/boot/dts/stm32mp15-scmi.dtsi | 6 ++++++
> arch/arm/boot/dts/stm32mp151.dtsi | 2 +-
> arch/arm/boot/dts/stm32mp157a-dk1-scmi.dts | 4 ++++
> arch/arm/boot/dts/stm32mp157c-ed1-scmi.dts | 4 ++++
> 4 files changed, 15 insertions(+), 1 deletion(-)
>
Series applied in stm32-fixes.
Alex
prev parent reply other threads:[~2022-07-01 11:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 9:27 [PATCH 0/3] SCMI Update for STM32MP15 boards gabriel.fernandez
2022-06-24 9:27 ` [PATCH 1/3] ARM: dts: stm32: use the correct clock source for CEC on stm32mp151 gabriel.fernandez
2022-06-24 9:27 ` [PATCH 2/3] ARM: dts: stm32: DSI should use LSE SCMI clock on DK1/ED1 STM32 board gabriel.fernandez
2022-06-24 9:27 ` [PATCH 3/3] ARM: dts: stm32: delete fixed clock node on STM32MP15-SCMI gabriel.fernandez
2022-07-01 11:44 ` 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=157d783b-156a-72fb-542a-87c483ca2411@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=gabriel.fernandez@foss.st.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.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).