From: Takashi Iwai <tiwai@suse.de>
To: "Lin, Mengdong" <mengdong.lin@intel.com>
Cc: "Yang, Libin" <libin.yang@intel.com>,
ALSA Development Mailing List <alsa-devel@alsa-project.org>,
"airlied@linux.ie" <airlied@linux.ie>,
"Girdwood, Liam R" <liam.r.girdwood@intel.com>,
Raymond Yau <superquad.vortex2@gmail.com>,
"tanuk@iki.fi" <tanuk@iki.fi>,
David Henningsson <david.henningsson@canonical.com>
Subject: Re: DP1.2 MST audio support discussion
Date: Fri, 23 Oct 2015 10:44:04 +0200 [thread overview]
Message-ID: <s5hfv12ug8b.wl-tiwai@suse.de> (raw)
In-Reply-To: <F46914AEC2663F4A9BB62374E5EEF8F84B862EAD@shsmsx102.ccr.corp.intel.com>
On Fri, 23 Oct 2015 10:35:26 +0200,
Lin, Mengdong wrote:
>
> > -----Original Message-----
> > From: Takashi Iwai [mailto:tiwai@suse.de]
> > Sent: Friday, October 23, 2015 1:54 PM
> >
> > On Fri, 23 Oct 2015 07:30:12 +0200,
> > Lin, Mengdong wrote:
> > >
> > > > -----Original Message-----
> > > > From: David Henningsson [mailto:david.henningsson@canonical.com]
> > > > Sent: Thursday, October 22, 2015 4:53 PM
> > >
> > > [snip]
> > >
> > > > I'll try to explain my suggestion (which I believe Takashi's buying
> > > > too) one more time then:
> > > >
> > > > First, when a monitor is plugged in, we need to dynamically assign
> > > > this monitor to five PCM devices. I believe this scheme will be best:
> > > >
> > > > For a monitor at pin nid 0x05, dev index 0, it will prefer PCM 3.
> > > > For a monitor at pin nid 0x06, dev index 0, it will prefer PCM 7.
> > > > For a monitor at pin nid 0x07, dev index 0, it will prefer PCM 8.
> > > > For a monitor at dev index 1 (any pin), it will prefer PCM 9.
> > > > For a monitor at dev index 2 (any pin), it will prefer PCM 10.
> > > >
> > > > For monitors at dev indices > 2 (can that happen?), or if the PCM is
> > > > already assigned to something else, try PCMs in this order: 9, 10, 3, 7, 8.
> > > > (Subject to discussion perhaps, I don't think the order matters too
> > > > much, because conflicts will be rare in practice.)
> > >
> > > Hi David,
> > >
> > > Would you please clarify why PA needs such a fixed binding between PCM
> > 3,7, 8 and pin 0x05,6,7?
> >
> > It's not PA's requirement. The only concern here is for people who uses
> > ALSA device directly, e.g. via aplay -Dhdmi:2. The first monitor is
> > guaranteed to be mapped to the compatible position for such people.
>
> Excuse me, could you share more background info here?
> Even before DP MST support, it seems that such people need to know what pin is used to connect a monitor. Why?
On the existing machines, if you connect to a certain DP port, it's
always assigned to the same device. This is guaranteed, so it's
perfectly fine to use this device statically for your purpose.
> The user can enumerate the PCM devices, and the PCM's jack ioctl can show whether a monitor is available behind this PCM device, no matter the driver uses fixed or dynamic binding between the PCM and pins.
> So people can always choose a PCM to use a monitor. I feel they need not care which pin is used for the monitor.
People *can* choose, but it doesn't mean people *must* reselect
another number out of sudden. If they have to, it may be called a
regression.
Takashi
next prev parent reply other threads:[~2015-10-23 8:44 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
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 [this message]
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=s5hfv12ug8b.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