Re: Jack event API - decision needed

Mark Brown
2011-06-20T16:47:17Z

On Mon, Jun 20, 2011 at 04:19:51PM +0200, Kay Sievers wrote:

> Domain-specific events should not be 'faked' as 'input' devices. No
> non-input subsystem should do that if it can be avoided. That 'input'
> supports nice and easy events to userspace should not be a reason to
> misuse it for pretty much unrelated things.

OK, but since jacks aren't at all audio specific (the most obvious
additional thing that goes over them is video for cases like composite
out on mic and the modern digital standards like HDMI) that wouldn't
address the issue. There's also things like docking stations which can
present very much like big fancy jacks.

> There are patches to have the ALSA control device emit these ALSA
> related events natively. That's would be just better, simpler and more
> correct than any additionally created input device.

That's not really terribly clever for the non-audio users, they'd have
to implement ALSA support.

> If we can't have the native ALSA events anytime soon for some reason,
> we might need to merge the input device support, but I would like to
> avoid that.

The input device usage has been present and in use in a basic form since
2.6.18, the ALSA integration of it since 2.6.27 so this isn't terribly
new.

It might be nice to have the information available via ALSA but it
doesn't seem reasonable to expect anything that might need the
information to have to go through ALSA.