From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Olivier Moysan <olivier.moysan@foss.st.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.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 1/1] arm64: dts: st: add spdifrx support on stm32mp251
Date: Mon, 9 Dec 2024 17:18:22 +0100 [thread overview]
Message-ID: <4075e04d-dab3-40f2-9a64-760081cf47ee@foss.st.com> (raw)
In-Reply-To: <20241105162141.712073-1-olivier.moysan@foss.st.com>
Hi Oliver
On 11/5/24 17:21, Olivier Moysan wrote:
> Add S/PDIFRX support to STM32MP25 SoC family.
>
> Signed-off-by: Olivier Moysan <olivier.moysan@foss.st.com>
> ---
> arch/arm64/boot/dts/st/stm32mp251.dtsi | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/st/stm32mp251.dtsi b/arch/arm64/boot/dts/st/stm32mp251.dtsi
> index 6fe12e3bd7dd..34970be2e0b3 100644
> --- a/arch/arm64/boot/dts/st/stm32mp251.dtsi
> +++ b/arch/arm64/boot/dts/st/stm32mp251.dtsi
> @@ -267,6 +267,20 @@ spi3: spi@400c0000 {
> status = "disabled";
> };
>
> + spdifrx: audio-controller@400d0000 {
> + compatible = "st,stm32h7-spdifrx";
> + #sound-dai-cells = <0>;
> + reg = <0x400d0000 0x400>;
> + clocks = <&rcc CK_KER_SPDIFRX>;
> + clock-names = "kclk";
> + interrupts = <GIC_SPI 170 IRQ_TYPE_LEVEL_HIGH>;
> + dmas = <&hpdma 71 0x43 0x212>,
> + <&hpdma 72 0x43 0x212>;
> + dma-names = "rx", "rx-ctrl";
> + access-controllers = <&rifsc 30>;
> + status = "disabled";
> + };
> +
> usart2: serial@400e0000 {
> compatible = "st,stm32h7-uart";
> reg = <0x400e0000 0x400>;
Applied on stm32-next.
Thanks!!
Alex
prev parent reply other threads:[~2024-12-09 16:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 16:21 Olivier Moysan
2024-12-09 16:18 ` 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=4075e04d-dab3-40f2-9a64-760081cf47ee@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.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@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
all inboxes | Powered by JetHome®