[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGrhNMyAofsnwKYMk+60GyvpaW9pMtoJf_2Q_Tc82G8QCFOiFA@mail.gmail.com>
Date: Mon, 22 Jul 2013 14:11:44 -0700
From: Felipe Tonello <eu@...ipetonello.com>
To: Mark Brown <broonie@...nel.org>
Cc: alsa-devel@...a-project.org, LiamGirdwoodlgirdwood@...il.com,
JaroslavKyselaperex@...ex.cz, TakashiIwaitiwai@...e.de,
linux-kernel@...r.kernel.org,
"Felipe F. Tonello" <ftonello@...cacor.com>
Subject: Re: [PATCH] ALSA: SoC: Added jack detection kcontrol support
Hi Mark,
On Sun, Jul 21, 2013 at 5:01 PM, Mark Brown <broonie@...nel.org> wrote:
> On Fri, Jul 19, 2013 at 05:59:22PM -0700, Felipe F. Tonello wrote:
>> From: "Felipe F. Tonello" <ftonello@...cacor.com>
>>
>> It adds soc jack support for alsa kcontrol.
>>
>> This support is necessary since the new kcontrol is used by user-space
>> daemons, such as PulseAudio(>=2.0), to do jack detection.
>>
>> Signed-off-by: Felipe F. Tonello <ftonello@...cacor.com>
>> ---
>> include/sound/soc.h | 1 +
>> sound/soc/Kconfig | 1 +
>> sound/soc/soc-jack.c | 22 ++++++++++++++++++++++
>> 3 files changed, 24 insertions(+)
>
> No, this makes no sense at all as an ASoC specific feature - it should
> be a standard feature of ALSA jacks. The whole point of having ALSA
> core infrastructure for jacks is to avoid having to go round doing make
> work stuff like this.
I agree. I added as a ASoC feature because I followed the example of
HDA implementation.
My question is: Why ALSA Jack support uses evdev input events to
notify user-space? Is there any user-space relying on that? If no, I
would like to change ALSA Jack implementation to only use KControl and
remove specific implementations.
At least the only daemon that I know that supports jack detection,
which is PulseAudio, uses this new ALSA KControl for Jacks.
Regards,
Felipe Tonello
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists