From: David Henningsson <david.henningsson@canonical.com>
To: "Yang, Libin" <libin.yang@intel.com>, Takashi Iwai <tiwai@suse.de>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>,
"airlied@linux.ie" <airlied@linux.ie>,
"Lin, Mengdong" <mengdong.lin@intel.com>,
"Nikula, Jani" <jani.nikula@intel.com>,
"Girdwood, Liam R" <liam.r.girdwood@intel.com>,
"Lu, Han" <han.lu@intel.com>,
Raymond Yau <superquad.vortex2@gmail.com>,
"tanuk@iki.fi" <tanuk@iki.fi>
Subject: Re: DP1.2 MST audio support discussion
Date: Thu, 5 Nov 2015 10:07:03 +0100 [thread overview]
Message-ID: <563B1C37.4010400@canonical.com> (raw)
In-Reply-To: <96A12704CE18D347B625EE2D4A099D19765611@SHSMSX103.ccr.corp.intel.com>
On 2015-11-04 15:17, Yang, Libin wrote:
> + Jani, who is from Intel gfx team.
>
>> -----Original Message-----
>> From: David Henningsson [mailto:david.henningsson@canonical.com]
>> Sent: Monday, November 02, 2015 3:55 PM
>> To: Yang, Libin; Takashi Iwai
>> Cc: Lin, Mengdong; Raymond Yau; airlied@linux.ie; tanuk@iki.fi; ALSA
>> Development Mailing List; Girdwood, Liam R; Lu, Han
>> Subject: Re: [alsa-devel] DP1.2 MST audio support discussion
>>
>>
>>
>> On 2015-11-02 08:30, Yang, Libin wrote:
>>>
>>>>> 4. power management
>>>>> If we close the PCM when disconnecting monitor, the driver will
>>>> return
>>>>> -ENODEV, and we assume user space will close the PCM at once .
>>>> ... if we implement it. Actually this behavior (returning -ENODEV) is
>>>> not mandatory and needs investigation beforehand, whether this
>>>> breaks
>>>> any applications, especially PA.
>>> Yes. I heard that PA has dummy PCM and when there is no HW to
>>> play the audio, PA can smoothly move the PCM from HW to dummy
>>> PCM. If it's true, stopping PCM will not break PA, I think.
>>
>> Well, in most cases (not all) there will be an analog output available,
>> so we're more likely to move there than to a dummy PCM. The
>> problem is
>> that PA does not currently figure out that a -ENODEV means that one
>> should switch from a digital to an analog profile. So, at least at this
>> point, don't expect a "smooth move".
>>
>> I'm not sure if this is a good idea or not, but just brainstorming here:
>>
>> If PA (or other application) tries to play back to a PCM, and that PCM
>> is currently unassigned. What would happen if we actually assigned a
>> converter node at that point, but no pin node connected to that
>> converter node? Would that give a backwards compatible behaviour? I
>> e,
>> audio userspace could successfully play back audio through the
>> converter
>> node, but then the audio goes nowhere because there is no pin node
>> assigned?
>
> GFX team hope us that if there is no monitor connected, audio
> should release gfx so gfx driver can enter power save mode.
> Based on the requirement, audio driver may need stop playback
> as soon as the monitor is disconnected.
I'm not talking about continuous playback here, so power consumption
should not be a big concern. E g, if it takes a second or so before PA
reroutes audio somewhere else, it's not a big deal from a power save
perspective.
So I'm asking my question again. What would happen (on Intel hardware),
if you stream audio to a converter node on the audio codec, and there is
no pin node connected to that converter node?
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
next prev parent reply other threads:[~2015-11-05 9:07 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
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 [this message]
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=563B1C37.4010400@canonical.com \
--to=david.henningsson@canonical.com \
--cc=airlied@linux.ie \
--cc=alsa-devel@alsa-project.org \
--cc=han.lu@intel.com \
--cc=jani.nikula@intel.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 \
--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