From: Daniel Baluta <daniel.baluta@nxp.com>
To: perex@perex.cz, tiwai@suse.com, broonie@kernel.org,
kuninori.morimoto.gx@renesas.com
Cc: lgirdwood@gmail.com, robh+dt@kernel.org,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-imx@nxp.com,
Daniel Baluta <daniel.baluta@nxp.com>
Subject: [RFC PATCH 2/2] ASoC: simple-card: Add documentation for force-dpcm property
Date: Sun, 13 Oct 2019 22:00:14 +0300 [thread overview]
Message-ID: <20191013190014.32138-3-daniel.baluta@nxp.com> (raw)
In-Reply-To: <20191013190014.32138-1-daniel.baluta@nxp.com>
This property can be global in which case all links created will be DPCM
or present in certian dai-link subnode in which case only that specific
link is forced to be DPCM.
Signed-off-by: Daniel Baluta <daniel.baluta@nxp.com>
---
Documentation/devicetree/bindings/sound/simple-card.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/sound/simple-card.txt b/Documentation/devicetree/bindings/sound/simple-card.txt
index 79954cd6e37b..15e6f5329857 100644
--- a/Documentation/devicetree/bindings/sound/simple-card.txt
+++ b/Documentation/devicetree/bindings/sound/simple-card.txt
@@ -63,6 +63,7 @@ Optional dai-link subnode properties:
- mclk-fs : Multiplication factor between stream
rate and codec mclk, applied only for
the dai-link.
+- force-dpcm : Indicates dai-link is always DPCM.
For backward compatibility the frame-master and bitclock-master
properties can be used as booleans in codec subnode to indicate if the
--
2.17.1
next prev parent reply other threads:[~2019-10-13 19:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-13 19:00 [RFC PATCH 0/2] Introduce for-dpcm DT property Daniel Baluta
2019-10-13 19:00 ` [RFC PATCH 1/2] ASoC: simple-card: Introduce force-dpcm " Daniel Baluta
2019-10-13 19:00 ` Daniel Baluta [this message]
2019-10-14 11:56 ` [RFC PATCH 2/2] ASoC: simple-card: Add documentation for force-dpcm property Mark Brown
2019-10-14 13:17 ` [alsa-devel] " Daniel Baluta
2019-10-14 16:10 ` Mark Brown
2019-10-15 1:02 ` Kuninori Morimoto
2019-10-15 1:18 ` Kuninori Morimoto
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=20191013190014.32138-3-daniel.baluta@nxp.com \
--to=daniel.baluta@nxp.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robh+dt@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).