[alsa-devel] Jack event API - decision needed

Mark Brown broonie at opensource.wolfsonmicro.com
Tue Jun 28 18:20:44 CEST 2011

On Mon, Jun 27, 2011 at 06:01:55PM +0100, Colin Guthrie wrote:

> I'm not 100% sure what elements of a sink is used to do this matching
> but I'd take a wild stab in the dark guess at the "device.bus_path"
> entry in the proplis which can look something like:
>   device.bus_path = "pci-0000:00:1d.7-usb-0:7.1:1.0"

Ah, if it's doing that that's not going to work in general - the jack
may not be part of the same device as the thing we're reporting on.

> > I'm also concerned that an implicit system may be hard to use from
> > userspace, if only in terms of figuring out what the rules are for
> > matching things up.

> I doubt this will be much of a problem once a few clean examples are out
> there. The logic to match things up should be pretty trivial.

One of my biggest concerns here is people even finding the relevant bit
of the stack, let alone working out what to do with it - bear in mind
that my main focus is on the embedded side so people may not be familiar
with Linux or using the standard desktop stack at all.

More information about the Alsa-devel mailing list