On Tue, Nov 10, 2015 at 02:24:13PM +0000, Opensource [Adam Thomson] wrote: > On November 10, 2015 14:15, Mark Brown wrote: > > So this *isn't* a normal mic detection feature? What's the userspace > > interface for reporting then? > By mic detection you thought this was to detect if a mic was present or not? That and button detection. > It's to detect the noise level on a mic and raise an event if the captured > sound is above a specific threshold level. Apologies if that wasn't clear. > In the driver code I'm using KEY_VOICECOMMAND, and simulating a press and > release of this key, to indicate to user-space. This seemed like the obvious > choice for this feature to me, although I'd happily get your opinion on this. That seems like a particularly unfortunate choice given that VOICECOMMAND is used in the standard Google headset mapping (see ts3a227e for an example, that's a device specifically aimed at providing accessory detection in Chromebooks). There's also been some pushback against using the input devices due to the difficulty in enabling apps to access input devices - ALSA controls were preferred instead but that's less helpful for tinyalsa. Perhaps that can be added relatively easily, or a uevent or something. Not sure what the best way forward here is, the other implementations of this that I'm aware of do more of the detection in offload and present streams of detected audio to userspace via normal capture. I would at least suggest moving this into a separate patch and doing the integration separately.
Attachment:
signature.asc
Description: PGP signature
