[alsa-devel] Dynamic HDMI PCM creation
david.henningsson at canonical.com
Mon Sep 17 12:15:23 CEST 2012
On 09/10/2012 03:01 PM, Takashi Iwai wrote:
> Hi David,
> as we discussed at Plumbers, I tried some hack to create/delete
> HDMI/DP PCM stream per hotplug/unplug. Test patches are found in
> sound-unstable git tree topic/hdmi-dynamic-pcm branch
> The patches are all small and easy, but it's still in a pretty rough
> cut. It won't handle some cases, e.g. unplug during suspend, or
> such, I'm afraid. After all, it's just a test.
> With these patches, the PCM device appears and disappears properly
> upon HDMI/DP hotplug/unplug on my system. On mine, it appears as
> /dev/snd/pcmC0D8 as it's an Intel on-board. So far, so good.
> Now the problem is that PA gets confused when this happens. It can
> switch to HDMI/DP, but then the analog output disappears from PA's
> profile. You cannot switch back to analog output after that, even
> after you unplug HDMI/DP cable.
> Or, it might be my PA version... I'll check newer one.
> But it'd be good if you also check in your side.
As you probably know, PA does extensively test opening device strings at
startup, and then never again.
As such, I can understand that PA gets confused if you start adding and
removing PCM devices, because that changes whether and how different
device strings can be opened.
Looking forward, with HDMI, it's a reality that this will happen. And
therefore we need to deal with it in PA somehow, even if this is
non-trivial. So the first question would be - what notification
mechanism should we have to trigger "reprobing"? Are we recommended to
use the jack detection kcontrol API, or is there something else that
tells us that suddenly "hdmi:1,2" will actually be worth trying again?
David Henningsson, Canonical Ltd.
More information about the Alsa-devel