From: David Henningsson <david.henningsson@canonical.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org,
Felipe Tonello <eu@felipetonello.com>,
"Felipe F. Tonello" <ftonello@cercacor.com>,
TakashiIwaitiwai@suse.de, linux-kernel@vger.kernel.org,
lgirdwood@gmail.com, JaroslavKyselaperex@perex.cz
Subject: Re: [PATCH] ALSA: SoC: Added jack detection kcontrol support
Date: Wed, 24 Jul 2013 08:16:57 +0200 [thread overview]
Message-ID: <51EF7159.8030409@canonical.com> (raw)
In-Reply-To: <20130724001332.GW9858@sirena.org.uk>
On 07/24/2013 02:13 AM, Mark Brown wrote:
> On Tue, Jul 23, 2013 at 05:10:29PM -0700, Felipe Tonello wrote:
>> On Tue, Jul 23, 2013 at 5:40 AM, Mark Brown <broonie@kernel.org> wrote:
>
>>> This was the existing kernel API at the time that the code was added -
>>> I beleive people had been doing that for simple switches that detect the
>>> physical presence of a jack since it looks exactly like a button from a
>>> hardware point of view. See the original commit adding the code.
>
>> I saw it. I don't know what you think is the best way to go. I'm not
>> sure if someone is using this input event API, since even PulseAudio
>> even declined that implementation due KControl implementation.
>
> It's used quite a bit in embedded systems, there are actually patches
> for PulseAudio which were deployed for a while- I guess they might have
> been removed or something.
The input event implementation was only in Ubuntu (for a release or
two), and was never merged in upstream PA. (I guess one could find them
by looking in the Ubuntu archives.)
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
prev parent reply other threads:[~2013-07-24 6:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1374281962-3786-1-git-send-email-eu@felipetonello.com>
2013-07-22 0:01 ` [PATCH] ALSA: SoC: Added jack detection kcontrol support Mark Brown
2013-07-22 21:11 ` Felipe Tonello
2013-07-23 12:40 ` Mark Brown
2013-07-24 0:10 ` Felipe Tonello
2013-07-24 0:13 ` Mark Brown
2013-07-24 6:16 ` David Henningsson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51EF7159.8030409@canonical.com \
--to=david.henningsson@canonical.com \
--cc=JaroslavKyselaperex@perex.cz \
--cc=TakashiIwaitiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=eu@felipetonello.com \
--cc=ftonello@cercacor.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).