From: Lennart Poettering <mznyfn@0pointer.de>
To: alsa-devel@alsa-project.org
Subject: Re: Device creation order
Date: Sun, 5 Apr 2009 16:40:42 +0200 [thread overview]
Message-ID: <20090405144041.GA31963@tango.0pointer.de> (raw)
In-Reply-To: <20090405131605.GA31915@localhost>
On Sun, 05.04.09 21:16, Wu Fengguang (fengguang.wu@intel.com) wrote:
> > I'll ignore this for now since Jaroslav mentioned drivers doing this
> > are still experimental. But eventually we'd need to know some kind of
> > 'end notification' for this as well: i..e if the reconfiguration
> > causes multiple device nodes to disappear/appear we also need to know
> > when they are all complete. A possible simple fix would be to issue an
> > udev 'change' event on the control device after the reconfiguration
> > finished.
>
> btw, HDMI sink devices could be taught to generate more event types:
>
> - hotplug
> The user connected/disconnected a HDMI device.
Wouldn't that overlap with the jack sensing API?
> - reconfiguration
> The update of HDMI audio capabilities due to some user actions.
>
> - pause/play of audio stream
> An advanced feature in Consumer Electronics Control (CEC) for
> high-level user control of HDMI-connected devices.
What would these be?
>
> The HDMI audio devices will be created at module loading time, and
> won't be dynamically created/tear down on hotplug events. I wonder
> if PA is interested in the HDMI current-connectivity state?
Yes, we certainly are. I am not entirely sure though how to best
expose this.
Lennart
--
Lennart Poettering Red Hat, Inc.
lennart [at] poettering [dot] net ICQ# 11060553
http://0pointer.net/lennart/ GnuPG 0x1A015CC4
next prev parent reply other threads:[~2009-04-05 14:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 1:54 Device creation order Lennart Poettering
2009-04-03 7:12 ` Jaroslav Kysela
2009-04-03 7:20 ` Daniel Mack
2009-04-03 7:31 ` Jaroslav Kysela
2009-04-03 7:40 ` Daniel Mack
2009-04-03 10:34 ` Colin Guthrie
2009-04-03 11:51 ` Lennart Poettering
2009-04-03 11:43 ` Lennart Poettering
2009-04-03 7:38 ` Clemens Ladisch
2009-04-03 7:50 ` Jaroslav Kysela
2009-04-03 11:58 ` Lennart Poettering
2009-04-03 11:56 ` Lennart Poettering
2009-04-05 13:16 ` Wu Fengguang
2009-04-05 14:40 ` Lennart Poettering [this message]
2009-04-05 20:29 ` Mark Brown
2009-04-03 11:42 ` Lennart Poettering
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=20090405144041.GA31963@tango.0pointer.de \
--to=mznyfn@0pointer.de \
--cc=alsa-devel@alsa-project.org \
/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