mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Felipe Tonello <eu@felipetonello.com>
Cc: alsa-devel@alsa-project.org, LiamGirdwoodlgirdwood@gmail.com,
	JaroslavKyselaperex@perex.cz, TakashiIwaitiwai@suse.de,
	linux-kernel@vger.kernel.org,
	"Felipe F. Tonello" <ftonello@cercacor.com>
Subject: Re: [PATCH] ALSA: SoC: Added jack detection kcontrol support
Date: Tue, 23 Jul 2013 13:40:23 +0100	[thread overview]
Message-ID: <20130723124023.GX9858@sirena.org.uk> (raw)
In-Reply-To: <CAGrhNMyAofsnwKYMk+60GyvpaW9pMtoJf_2Q_Tc82G8QCFOiFA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 594 bytes --]

On Mon, Jul 22, 2013 at 02:11:44PM -0700, Felipe Tonello wrote:

> 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.

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.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-07-23 12:40 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 ` Mark Brown
2013-07-22 21:11   ` Felipe Tonello
2013-07-23 12:40     ` Mark Brown [this message]
2013-07-24  0:10       ` Felipe Tonello
2013-07-24  0:13         ` Mark Brown
2013-07-24  6:16           ` [alsa-devel] " David Henningsson

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=20130723124023.GX9858@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=JaroslavKyselaperex@perex.cz \
    --cc=LiamGirdwoodlgirdwood@gmail.com \
    --cc=TakashiIwaitiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=eu@felipetonello.com \
    --cc=ftonello@cercacor.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

all inboxes | Powered by JetHome®