From: Mark Brown <broonie@kernel.org>
Cc: mark.rutland@arm.com, robh@kernel.org,
alsa-devel@alsa-project.org, olivier.moysan@st.com,
alexandre.torgue@st.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, arnaud.pouliquen@st.com,
tiwai@suse.com, lgirdwood@gmail.com, broonie@kernel.org,
mcoquelin.stm32@gmail.com, benjamin.gaignard@st.com,
linux-arm-kernel@lists.infradead.org, kernel@stlinux.com
Subject: Applied "ASoC: stm32: Add S/PDIF to SAI bindings" to the asoc tree
Date: Mon, 26 Feb 2018 11:20:23 +0000 [thread overview]
Message-ID: <E1eqGpT-0006EP-2M@debutante> (raw)
In-Reply-To: <1519052437-24011-2-git-send-email-olivier.moysan@st.com>
The patch
ASoC: stm32: Add S/PDIF to SAI bindings
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
>From 994f46610bafd75a5881544bce9dd3acdbe3626a Mon Sep 17 00:00:00 2001
From: Olivier Moysan <olivier.moysan@st.com>
Date: Mon, 19 Feb 2018 16:00:35 +0100
Subject: [PATCH] ASoC: stm32: Add S/PDIF to SAI bindings
Add S/PDIF IEC6958 protocol support to STM32 SAI bindings.
Signed-off-by: olivier moysan <olivier.moysan@st.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
---
Documentation/devicetree/bindings/sound/st,stm32-sai.txt | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings/sound/st,stm32-sai.txt b/Documentation/devicetree/bindings/sound/st,stm32-sai.txt
index b1acc1a256ba..f301cdf0b7e6 100644
--- a/Documentation/devicetree/bindings/sound/st,stm32-sai.txt
+++ b/Documentation/devicetree/bindings/sound/st,stm32-sai.txt
@@ -45,6 +45,12 @@ SAI subnodes Optional properties:
This property sets SAI sub-block as slave of another SAI sub-block.
Must contain the phandle and index of the sai sub-block providing
the synchronization.
+ - st,iec60958: support S/PDIF IEC6958 protocol for playback
+ IEC60958 protocol is not available for capture.
+ By default, custom protocol is assumed, meaning that protocol is
+ configured according to protocol defined in related DAI link node,
+ such as i2s, left justified, right justified, dsp and pdm protocols.
+ Note: ac97 protocol is not supported by SAI driver
The device node should contain one 'port' child node with one child 'endpoint'
node, according to the bindings defined in Documentation/devicetree/bindings/
--
2.16.1
next prev parent reply other threads:[~2018-02-26 11:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 15:00 [RFC PATCH 0/3] ASoC: stm32: add S/PDIF support to SAI Olivier Moysan
2018-02-19 15:00 ` [RFC PATCH 1/3] ASoC: stm32: Add S/PDIF to SAI bindings Olivier Moysan
2018-02-26 11:20 ` Mark Brown [this message]
2018-02-19 15:00 ` [RFC PATCH 2/3] ASoC: dmaengine_pcm: add processing support Olivier Moysan
2018-02-19 15:00 ` [RFC PATCH 3/3] ASoC: stm32: sai: Add support of S/PDIF playback Olivier Moysan
2018-02-26 11:20 ` Applied "ASoC: stm32: sai: Add support of S/PDIF playback" to the asoc tree 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=E1eqGpT-0006EP-2M@debutante \
--to=broonie@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.pouliquen@st.com \
--cc=benjamin.gaignard@st.com \
--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=olivier.moysan@st.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