From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Olivier Moysan <olivier.moysan@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/4] ARM: dts: add audio support on stm32mp131
Date: Mon, 9 Jan 2023 17:55:26 +0100 [thread overview]
Message-ID: <1712d4cf-3315-0d38-04ab-6b55d3f1d4b9@foss.st.com> (raw)
In-Reply-To: <20221118142006.479138-1-olivier.moysan@foss.st.com>
Hi Olivier
On 11/18/22 15:20, Olivier Moysan wrote:
> Add SAI, I2S, SPDIFRX and DFSDM audio peripherals support for the
> STM32MP13 SoC family.
>
> Olivier Moysan (4):
> ARM: dts: stm32: add i2s nodes on stm32mp131
> ARM: dts: stm32: add sai nodes on stm32mp131
> ARM: dts: stm32: add spdifrx node on stm32mp131
> ARM: dts: stm32: add dfsdm node on stm32mp131
>
> arch/arm/boot/dts/stm32mp131.dtsi | 149 ++++++++++++++++++++++++++++++
> 1 file changed, 149 insertions(+)
>
Series applied on stm32-next.
Regards
Alex
prev parent reply other threads:[~2023-01-09 16:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 14:20 [PATCH 0/4] ARM: dts: add audio support on stm32mp131 Olivier Moysan
2022-11-18 14:20 ` [PATCH 1/4] ARM: dts: stm32: add i2s nodes " Olivier Moysan
2022-11-18 14:20 ` [PATCH 2/4] ARM: dts: stm32: add sai " Olivier Moysan
2022-11-18 14:20 ` [PATCH 3/4] ARM: dts: stm32: add spdifrx node " Olivier Moysan
2022-11-18 14:20 ` [PATCH 4/4] ARM: dts: stm32: add dfsdm " Olivier Moysan
2023-01-09 16:55 ` 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=1712d4cf-3315-0d38-04ab-6b55d3f1d4b9@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=devicetree@vger.kernel.org \
--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=olivier.moysan@foss.st.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).