From: Olivier MOYSAN <olivier.moysan@st.com>
To: Rob Herring <robh@kernel.org>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Alexandre TORGUE <alexandre.torgue@st.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Arnaud POULIQUEN <arnaud.pouliquen@st.com>,
"tiwai@suse.com" <tiwai@suse.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"mcoquelin.stm32@gmail.com" <mcoquelin.stm32@gmail.com>,
Benjamin GAIGNARD <benjamin.gaignard@st.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"kernel@stlinux.com" <kernel@stlinux.com>
Subject: Re: [PATCH 1/2] dt-bindings: Document the STM32 SPDIFRX interface
Date: Tue, 27 Jun 2017 15:23:08 +0000 [thread overview]
Message-ID: <b74e1d76-de2c-9eb3-4ea1-f63d3e8c82b7@st.com> (raw)
In-Reply-To: <20170623185514.nc3jqq6ikvwwv6sn@rob-hp-laptop>
Hello Rob,
On 06/23/2017 08:55 PM, Rob Herring wrote:
> On Fri, Jun 16, 2017 at 03:57:31PM +0200, olivier moysan wrote:
>> This adds documentation of device tree bindings for the
>> STM32 SPDIFRX interface.
>>
>> Signed-off-by: olivier moysan <olivier.moysan@st.com>
>> ---
>> .../devicetree/bindings/sound/st,stm32-spdifrx.txt | 56 ++++++++++++++++++++++
>> 1 file changed, 56 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/sound/st,stm32-spdifrx.txt
>>
>> diff --git a/Documentation/devicetree/bindings/sound/st,stm32-spdifrx.txt b/Documentation/devicetree/bindings/sound/st,stm32-spdifrx.txt
>> new file mode 100644
>> index 0000000..33826f2
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/sound/st,stm32-spdifrx.txt
>> @@ -0,0 +1,56 @@
>> +STMicroelectronics STM32 S/PDIF receiver (SPDIFRX).
>> +
>> +The SPDIFRX peripheral, is designed to receive an S/PDIF flow compliant with
>> +IEC-60958 and IEC-61937.
>> +
>> +Required properties:
>> + - compatible: should be "st,stm32h7-spdifrx"
>> + - reg: cpu DAI IP base address and size
>> + - clocks: must contain an entry for kclk (used as S/PDIF signal reference)
>> + - clock-names: must contain "kclk"
>> + - interrupts: cpu DAI interrupt line
>> + - dmas: DMA specifiers for audio data DMA and iec control flow DMA
>> + See STM32 DMA bindings, Documentation/devicetree/bindings/dma/stm32-dma.txt
>> + - dma-names: two dmas have to be defined, "rx" and "rx-ctrl"
>> +
>> +Optional properties:
>> + - resets: Reference to a reset controller asserting the SPDIFRX
>> +
>> +The device node should contain one 'port' child node with one child 'endpoint'
>> +node, according to the bindings defined in Documentation/devicetree/bindings/
>> +graph.txt.
>> +
>> +Example:
>> +spdifrx: spdifrx@40004000 {
>> + compatible = "st,stm32h7-spdifrx";
>> + reg = <0x40004000 0x400>;
>> + clocks = <&rcc SPDIFRX_CK>;
>> + clock-names = "kclk";
>> + interrupts = <97>;
>> + dmas = <&dmamux1 2 93 0x400 0x0>,
>> + <&dmamux1 3 94 0x400 0x0>;
>> + dma-names = "rx", "rx-ctrl";
>> + pinctrl-0 = <&spdifrx_pins>;
>> + pinctrl-names = "default";
>> +
>> + spdifrx_port: port {
>> + cpu_endpoint: endpoint {
>> + remote-endpoint = <&codec_endpoint>;
>> + };
>> + };
>> +};
>> +
>> +spdif_in: spdif-in {
>> + compatible = "linux,spdif-dir";
>
> What is this? It should go.
>
> Rob
>
This is the ASoC spdif stub codec. This is relevant in DT when
spdif interface is wired to a connector.
I will remove it from bindings.
BRs
olivier
next prev parent reply other threads:[~2017-06-27 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 13:57 [PATCH 0/2] ASoC: stm32: add SPDIFRX driver olivier moysan
2017-06-16 13:57 ` [PATCH 1/2] dt-bindings: Document the STM32 SPDIFRX interface olivier moysan
2017-06-21 11:16 ` Applied "ASoC: stm32: Add DT bindings for SPDIFRX interface" to the asoc tree Mark Brown
[not found] ` <1497621452-615-2-git-send-email-olivier.moysan-qxv4g6HH51o@public.gmane.org>
2017-06-23 18:55 ` [PATCH 1/2] dt-bindings: Document the STM32 SPDIFRX interface Rob Herring
2017-06-27 15:23 ` Olivier MOYSAN [this message]
2017-06-16 13:57 ` [PATCH 2/2] ASoC: stm32: Add SPDIFRX support olivier moysan
2017-06-19 16:46 ` Mark Brown
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=b74e1d76-de2c-9eb3-4ea1-f63d3e8c82b7@st.com \
--to=olivier.moysan@st.com \
--cc=alexandre.torgue@st.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.pouliquen@st.com \
--cc=benjamin.gaignard@st.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@stlinux.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh@kernel.org \
--cc=tiwai@suse.com \
/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).