From: Takashi Iwai <tiwai@suse.de>
To: Raymond Yau <superquad.vortex2@gmail.com>
Cc: "Yang, Libin" <libin.yang@intel.com>,
ALSA Development Mailing List <alsa-devel@alsa-project.org>,
"airlied@linux.ie" <airlied@linux.ie>,
"Lin, Mengdong" <mengdong.lin@intel.com>,
"Girdwood, Liam R" <liam.r.girdwood@intel.com>,
"tanuk@iki.fi" <tanuk@iki.fi>,
David Henningsson <david.henningsson@canonical.com>
Subject: Re: DP1.2 MST audio support discussion
Date: Fri, 16 Oct 2015 08:38:05 +0200 [thread overview]
Message-ID: <s5h7fmngvxu.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAN8cciYqLBH=kXvPjrGTgGPg9p7euU5w9z=UYdvKk4Vnxf-YFw@mail.gmail.com>
On Fri, 16 Oct 2015 02:32:50 +0200,
Raymond Yau wrote:
>
> > >
> > > Do it mean that only one DP MST port and no HDMI port on the same
> graphic
> > > card ?
> >
> > No.
>
> If there is only one HDMI and one Display Port, this mean that there are
> two pin complexes
Yes, and the mapping doesn't change in this case as before.
> How about the name of jack detection kctl of three Display Port monitors
> which are created on the same pin complex but different dev_index ?
It's one of the models we've considered. Basically the number of
devices can be up to 64 (or such) per pin. For Intel case, due to the
limitation of converters, it's up to 3. For other GPUs that may drive
more simultaneous outputs, the number increases in square. If a GPU
may handle 16 outputs, it'll be 256 entries.
Although the 256 entries are certainly manageable as kctl, whether
this is the best representation for user-space is a question.
> Will three three display port monitor playback devices always play
> different stream even when the displays are in clone mode ?
The clone mode is another messy part...
> > > If DP MST are dasiy chained, the unplug of the first monitor from
> Display
> > > Port will cause all DP monitor in the dasiy chain disconnect
> >
> > Yes.
> >
>
> Do the power off of the Display Port in the middle of the dasiy chain also
> affect the last display port mointor in the dasiy chain ?
Possibly. But it's not what we really care, as this is the thing the
graphics side should handle.
Takashi
next prev parent reply other threads:[~2015-10-16 6:38 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 6:25 DP1.2 MST audio support discussion Yang, Libin
2015-10-13 6:47 ` David Henningsson
2015-10-13 7:34 ` Yang, Libin
2015-10-13 9:20 ` Takashi Iwai
2015-10-13 12:31 ` Yang, Libin
2015-10-13 14:03 ` Takashi Iwai
2015-10-13 14:12 ` Yang, Libin
2015-10-13 16:20 ` Takashi Iwai
2015-10-14 2:03 ` Yang, Libin
2015-10-13 23:52 ` Raymond Yau
2015-10-14 2:15 ` Yang, Libin
2015-10-14 6:44 ` Takashi Iwai
2015-10-16 0:32 ` Raymond Yau
2015-10-16 6:38 ` Takashi Iwai [this message]
2015-10-16 8:51 ` Yang, Libin
2015-10-16 9:00 ` Takashi Iwai
2015-10-16 11:55 ` Yang, Libin
2015-10-19 5:16 ` Yang, Libin
2015-10-22 1:31 ` Yang, Libin
2015-10-22 6:51 ` David Henningsson
2015-10-22 6:56 ` Yang, Libin
2015-10-22 7:27 ` David Henningsson
2015-10-22 7:40 ` Yang, Libin
2015-10-22 8:52 ` David Henningsson
2015-10-22 11:21 ` Yang, Libin
2015-10-22 17:42 ` Takashi Iwai
2015-10-23 5:30 ` Lin, Mengdong
2015-10-23 5:53 ` Takashi Iwai
2015-10-23 8:35 ` Lin, Mengdong
2015-10-23 8:44 ` Takashi Iwai
2015-10-23 10:15 ` Lin, Mengdong
2015-11-13 7:27 ` Raymond Yau
2015-10-23 10:55 ` David Henningsson
2015-10-23 12:35 ` Lin, Mengdong
2015-10-27 8:45 ` Yang, Libin
2015-10-30 11:27 ` Takashi Iwai
2015-11-01 8:53 ` Raymond Yau
2015-11-02 7:54 ` Yang, Libin
2015-11-02 7:30 ` Yang, Libin
2015-11-02 7:46 ` Takashi Iwai
2015-11-02 7:55 ` David Henningsson
2015-11-04 14:17 ` Yang, Libin
2015-11-04 15:04 ` Jani Nikula
2015-11-05 9:07 ` David Henningsson
2015-11-05 9:39 ` Raymond Yau
2015-11-10 6:46 ` Yang, Libin
2015-11-10 7:45 ` David Henningsson
2015-11-11 2:04 ` Yang, Libin
2015-11-11 7:58 ` Yang, Libin
2015-11-11 8:05 ` Takashi Iwai
2015-11-11 8:11 ` Yang, Libin
2015-11-11 8:26 ` Takashi Iwai
2015-11-11 8:33 ` Yang, Libin
2015-11-11 8:52 ` Takashi Iwai
2015-10-23 9:40 ` Raymond Yau
2015-10-23 13:08 ` Lin, Mengdong
2015-10-16 1:11 ` 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=s5h7fmngvxu.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=airlied@linux.ie \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.com \
--cc=liam.r.girdwood@intel.com \
--cc=libin.yang@intel.com \
--cc=mengdong.lin@intel.com \
--cc=superquad.vortex2@gmail.com \
--cc=tanuk@iki.fi \
/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