From: Jani Nikula <jani.nikula@linux.intel.com>
To: Raymond Yau <superquad.vortex2@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>, "Lu, Han" <han.lu@intel.com>,
alsa-devel@alsa-project.org,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Girdwood, Liam R" <liam.r.girdwood@intel.com>
Subject: Re: [alsa-devel] [PATCH 3/4] snd: add support for displayport multi-stream to hda codec.
Date: Fri, 03 Jul 2015 11:54:49 +0300 [thread overview]
Message-ID: <87si957h9i.fsf@intel.com> (raw)
In-Reply-To: <CAN8ccian-kupvzhRPPin6t2oPtOESoZEE1=i6CN4r_zc3Zhjew@mail.gmail.com>
On Fri, 03 Jul 2015, Raymond Yau <superquad.vortex2@gmail.com> wrote:
> 2015-6-29 下午3:58於 "Jani Nikula" <jani.nikula@linux.intel.com>寫道:
>>
>> On Sat, 27 Jun 2015, Raymond Yau <superquad.vortex2@gmail.com> wrote:
>> >> > >
>> >> > > Shall we move or cc this discussion on audio driver side to ALSA
> ML?
>> >> >
>> >> > Oops I thought I had cc'ed these patches to alsa-devel as well when I
>> > sent them.
>> >> >
>> >> > > I think we also need to decide how to manage PCM devices for DP
> MST.
>> >> > > Now the HD-A driver create a PCM device for each pin, and the
>> > substream
>> >> > > number is 1 for each PCM. Now with DP MST enabled, each pin can
>> > support
>> >> > > multiple streams (e.g. 3 on Intel HSW/BDW/SKL).
>> >> > >
>> >> > > There may be 2 options:
>> >> > > -#1: Let an HDMI codec specify number of substreams, same as the
>> > number
>> >> > > of device entries on a pin. We can specify 3 for HSW/BDW/SKL. Other
>> >> > > vendors can also specify a value according to actual HW
> capabilities.
>> >> > >
>> >> > > So for HSW, we have 3x3 subtreams totally. But we only have 3
>> > convertors
>> >> > > (for 3 display pipelines), so we can open up to 3 substreams at the
>> > same
>> >> > > time. When the audio driver finds all 3 convertors are used when
>> > opening
>> >> > > a new substream, it will fail.
>> >> >
>> >> > One thing I noticed is the number of devices on a PIN is only updated
>> > when
>> >> > the MST device is plugged in so normally pins 5,6,7 have 0 devices,
> and
>> > when
>> >> > I plug in MST device, I get the 3 devices on port 6. So it seems
> dynamic
>> >> > enough at this point, though I guess it'll always be 0 or 3.
>> >> > >
>> >> > > - #2: Create PCM device dynamically. Only create a PCM devices for
> a
>> > device
>> >> > > entry which connects to monitor with audio support. When the
> monitor
>> >> > > is removed, the PCM device will be disconnected, closed and
> removed,
>> >> > > similar to the USB case.
>> >
>> > Do the driver really need dynamic PCM since display ports are dasiy
> chained
>> > and the locations within the dasiy chain are fixed ?
>
> http://www.intel.com/support/motherboards/desktop/sb/CS-034199.htm
>
> Do the first display always support sound since hdmi can connect to tv
> using dvi ?
I don't see the relevance.
> As Pulseaudio does not support multi streaming ( playing different audio
> streams to headphone and rear panel speakers , how can pulseaudion support
> displayport MST ?
Even if it couldn't support multiple streams at the same time, there has
to be a way to choose one of the audio capable sinks in the DP MST
topology (which will change dynamically).
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-07-03 8:52 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 4:01 haswell displayport MST audio support Dave Airlie
2015-06-17 4:01 ` [PATCH 1/4] dp/mst: add SDP stream support Dave Airlie
2015-06-17 4:01 ` [PATCH 2/4] i915: add support for GPU side of MST audio Dave Airlie
2015-06-17 8:07 ` Chris Wilson
2015-06-17 11:54 ` Jani Nikula
2015-06-17 11:56 ` Jani Nikula
2015-06-19 6:27 ` Lin, Mengdong
2015-06-17 11:27 ` Daniel Vetter
2015-06-17 4:01 ` [PATCH 3/4] snd: add support for displayport multi-stream to hda codec Dave Airlie
2015-06-19 9:54 ` Lin, Mengdong
2015-06-19 10:33 ` Dave Airlie
2015-06-19 11:15 ` Takashi Iwai
2015-06-22 12:54 ` Daniel Vetter
2015-06-22 13:23 ` Takashi Iwai
2015-06-22 13:29 ` Liam Girdwood
2015-06-22 15:21 ` Kaskinen, Tanu
2015-06-22 15:44 ` Takashi Iwai
2015-06-23 7:51 ` [Intel-gfx] " Kaskinen, Tanu
2015-06-23 8:06 ` Takashi Iwai
2015-06-24 12:41 ` [Intel-gfx] " Kaskinen, Tanu
2015-06-24 13:06 ` [alsa-devel] " Liam Girdwood
2015-06-24 20:47 ` Kaskinen, Tanu
2015-06-25 9:44 ` [alsa-devel] " Liam Girdwood
2015-06-26 10:14 ` [alsa-devel] [Intel-gfx] " Kaskinen, Tanu
2015-06-26 10:50 ` Kaskinen, Tanu
2015-06-26 18:45 ` Liam Girdwood
2015-06-26 16:27 ` [Intel-gfx] " Kaskinen, Tanu
2015-06-27 6:09 ` [alsa-devel] " Raymond Yau
2015-06-29 8:00 ` Jani Nikula
2015-07-03 3:45 ` Raymond Yau
2015-07-03 8:54 ` Jani Nikula [this message]
2015-06-25 8:22 ` Raymond Yau
2015-06-25 12:52 ` David Weinehall
2015-06-17 4:01 ` [PATCH 4/4] snd/hdmi: hack out haswell codec workaround Dave Airlie
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=87si957h9i.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=han.lu@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=liam.r.girdwood@intel.com \
--cc=superquad.vortex2@gmail.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