[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f8d8557b-39bb-265c-9fa7-2034a0364594@metafoo.de>
Date: Tue, 7 Mar 2017 14:47:54 +0100
From: Lars-Peter Clausen <lars@...afoo.de>
To: Jerome Brunet <jbrunet@...libre.com>,
Mark Brown <broonie@...nel.org>
Cc: Kevin Hilman <khilman@...libre.com>, alsa-devel@...a-project.org,
Neil Armstrong <narmstrong@...libre.com>,
Liam Girdwood <lgirdwood@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: [alsa-devel] [PATCH 2/3] ASoC: dio2125: add dio2125 amp driver
On 03/07/2017 02:13 PM, Jerome Brunet wrote:
> On Tue, 2017-03-07 at 13:36 +0100, Mark Brown wrote:
>> On Mon, Mar 06, 2017 at 06:44:50PM +0100, Jerome Brunet wrote:
>>
>>> + gpiod_set_value(priv->gpiod_enable, val);
>>
>> You should use gpiod_set_value_cansleep() so that the driver can work
>> with all GPIOs unless there's a specific need to have GPIOs you can
>> control in interrupt (which should be the case for anything you're
>> using
>> for DAPM control).
>
> Indeed, Thanks for pointing this out.
> I have question regarding this DAPM control.
> Here, I put the control in DAPM so it can help with the pop noise
> reduction, but I think it would be nice if the user could force the
> mute if he wants to.
>
> Would it be OK to add a user control and some logic so the output is
> enabled only if DAPM and the user agree it should ?
You could put a DAPM switch on the path. This way DAPM will take care of
muting the output if the user toggles the control and other DAPM widgets
connected to the output of the AMP will also be aware that it is off.
Powered by blists - more mailing lists