From: libin.yang@intel.com
To: alsa-devel@alsa-project.org, tiwai@suse.de
Cc: libin.yang@intel.com, mengdong.lin@intel.com
Subject: [PATCH v4 3/3] ALSA: Documentation about HDA DP MST pin init and connection
Date: Tue, 6 Dec 2016 10:48:39 +0800 [thread overview]
Message-ID: <1480992519-108079-4-git-send-email-libin.yang@intel.com> (raw)
In-Reply-To: <1480992519-108079-1-git-send-email-libin.yang@intel.com>
From: Libin Yang <libin.yang@intel.com>
Add the documentation about HD-audio DP MST:
1. pin initialization
2. device entry connection list
Signed-off-by: Libin Yang <libin.yang@intel.com>
---
Documentation/sound/hd-audio/dp-mst.rst | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/Documentation/sound/hd-audio/dp-mst.rst b/Documentation/sound/hd-audio/dp-mst.rst
index 58b7243..1617459 100644
--- a/Documentation/sound/hd-audio/dp-mst.rst
+++ b/Documentation/sound/hd-audio/dp-mst.rst
@@ -19,6 +19,23 @@ PCM
===
To be added
+Pin Initialization
+==================
+Each pin may have several device entries (virtual pins). On Intel platform,
+the device entries number is dynamically changed. If DP MST hub is connected,
+it is in DP MST mode, and the device entries number is 3. Otherwise, the
+device entries number is 1.
+
+To simplify the implementation, all the device entries will be initialized
+when bootup no matter whether it is in DP MST mode or not.
+
+Connection list
+===============
+DP MST reuses connection list code. The code can be reused because
+device entries on the same pin have the same connection list.
+
+This means DP MST gets the device entry connection list without the
+device entry setting.
Jack
====
--
2.7.4
next prev parent reply other threads:[~2016-12-06 2:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 2:48 [PATCH v4 0/3] support DP MST audio libin.yang
2016-12-06 2:48 ` [PATCH v4 1/3] ALSA: hda - add DP mst verb support libin.yang
2016-12-06 2:48 ` [PATCH v4 2/3] ALSA: hda - add DP MST audio support libin.yang
2016-12-06 2:48 ` libin.yang [this message]
2016-12-06 2:58 ` [PATCH v4 0/3] support DP MST audio Yang, Libin
2016-12-06 7:20 ` Takashi Iwai
2016-12-06 7:51 ` [alsa-devel] " Daniel Vetter
2016-12-06 8:11 ` Takashi Iwai
2017-01-09 6:22 ` Yang, Libin
2017-01-10 8:19 ` Takashi Iwai
2017-01-10 8:45 ` Yang, Libin
2017-01-10 8:49 ` Takashi Iwai
2017-01-11 7:39 ` Daniel Vetter
2017-01-11 8:00 ` Takashi Iwai
2017-01-11 8:35 ` Daniel Vetter
2017-01-11 8:44 ` Yang, Libin
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=1480992519-108079-4-git-send-email-libin.yang@intel.com \
--to=libin.yang@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=mengdong.lin@intel.com \
--cc=tiwai@suse.de \
/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).