Re: [alsa-devel] [RFC 2/2] ASoC: Add MICFIL SoC Digital Audio Interface driver.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Dec 17, 2018 at 2:19 PM Mark Brown <broonie@xxxxxxxxxx> wrote:
>
> On Fri, Dec 14, 2018 at 02:09:00PM -0600, Pierre-Louis Bossart wrote:
>
> > There's no mention of any buffer so it's likely plain vanilla VAD here.
> > We've seen two choices to warn userspace of a acoustic event, either use a
> > uevent or a kcontrol. I believe we ended-up chosing the latter on the Intel
> > side in the past and that was also the plan for SOF.
>
> It sounded like there were some separate audio streams somewhere along
> the line, it wasn't super clear if that just went into a DSP that did
> the VAD and wasn't visible to the rest of the system or if it's
> something the system can see.  Generally we have gone for kcontrols for
> event signalling.

Yes, it is plain vanilla VAD here. The MICFIL hardware IP sends an interrupt
when voice is detected.

Can you point us to some code that uses kcontrol interface to signal an event?
This might sound silly because I know there are a lot of places where kcontrol
interface is used but I  just want make sure that we are on the same page.
>
> > In terms of configurations for the PDM we have completely different settings
> > since we pass explicit coefficients while this solution passes qualifiers
> > (cut-off, quality, etc), not sure if there is any point in trying to unify
> > those parameters.
>
> Yes, I don't think the specific parameters are going to be joined up any
> time soon - it's more the overall shape of the solution.



[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]


  Powered by Linux