[alsa-devel] Jack event API - decision needed

Mark Brown broonie at opensource.wolfsonmicro.com
Thu Jun 23 12:47:11 CEST 2011

On Thu, Jun 23, 2011 at 01:42:36AM -0700, Dmitry Torokhov wrote:
> On Thu, Jun 23, 2011 at 01:15:01AM +0100, Mark Brown wrote:

> > a case of reporting if things are connected, we need to group these
> > things together into bundles and link them to multiple other devices in
> > the system.

> Hmm, I am not sure I follow. We usually need to calssify and group
> devices; there is nothing new here...

Usually we do this per device type and by control path but what we need
to do here is say that a given jack has audio, video and input
functionality - it's a different grouping to our normal ones.

> > uevents are what the Android switch API uses.  I think that would have
> > some of the daemon issues that David raised, though?

> I'll have to locate original email; I am not subscribed to alsa list.

The issue was that he would really prefer PulseAudio (which runs as a
regular user) to be able to read the events directly.

More information about the Alsa-devel mailing list