[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEUnVG6tKmdTt455w8g9C2_+XXpKz5=TR7=V8Lo3uJ3DKrOvag@mail.gmail.com>
Date: Wed, 28 Jan 2015 09:46:27 -0800
From: Dylan Reid <dgreid@...omium.org>
To: Mark Brown <broonie@...nel.org>
Cc: Tomeu Vizoso <tomeu.vizoso@...labora.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Javier Martinez Canillas <javier.martinez@...labora.co.uk>,
Andrew Bresticker <abrestic@...omium.org>,
Simon Glass <sjg@...omium.org>,
Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.de>,
Stephen Warren <swarren@...dotorg.org>,
Thierry Reding <thierry.reding@...il.com>,
Alexandre Courbot <gnurou@...il.com>,
Lars-Peter Clausen <lars@...afoo.de>,
Wolfram Sang <wsa@...-dreams.de>,
"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>
Subject: Re: [PATCH v3 06/10] ASoC: tegra: Add a control for the headphone switch
On Wed, Jan 28, 2015 at 3:02 AM, Mark Brown <broonie@...nel.org> wrote:
> On Wed, Jan 28, 2015 at 11:51:04AM +0100, Tomeu Vizoso wrote:
>
>> To be used by userspace when the headphones jack is plugged in.
>
>> static const struct snd_kcontrol_new tegra_max98090_controls[] = {
>> + SOC_DAPM_PIN_SWITCH("Headphones"),
>> SOC_DAPM_PIN_SWITCH("Speakers"),
>> };
>
> Why is userspace doing this? If this is supposed to be associated with
> the jack detection I'd expect us to be doing this in kernel.
This is only related to jack detection in that seeing a jack insert or
removal can cause userspace to set or unset it depending on the
current policy.
--
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