All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: [PATCH 0/2] Support for button reporting on jacks
Date: Wed, 17 Mar 2010 18:22:43 +0000	[thread overview]
Message-ID: <20100317182242.GA990@rakim.wolfsonmicro.main> (raw)

This patch series adds support for key reporting to the generic ALSA
jack API.  Currently a series of switches are supported, with the jack
implementation assuming that only switches will be used.  This isn't
ideal for things like the simple buttons implemented in headsets which
are used in the same way as keyboard keys and physically resemble them
more closely than switches.

If this is applied I'd like if possible to merge the topic into the ASoC
tree so that I can use it in machine drivers there.

The following changes since commit 57d54889cd00db2752994b389ba714138652e60c:
  Linus Torvalds (1):
        Linux 2.6.34-rc1

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound-2.6.git topic/jack

Mark Brown (2):
      ALSA: Rename jack switch table in preparation for button support
      ALSA: Add support for key reporting via the jack interface

 include/sound/jack.h |    8 +++++
 sound/core/jack.c    |   71 +++++++++++++++++++++++++++++++++++++++++++++----
 2 files changed, 73 insertions(+), 6 deletions(-)

             reply	other threads:[~2010-03-17 18:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-17 18:22 Mark Brown [this message]
2010-03-17 18:23 ` [PATCH 1/2] ALSA: Rename jack switch table in preparation for button support Mark Brown
2010-03-17 18:23 ` [PATCH 2/2] ALSA: Add support for key reporting via the jack interface Mark Brown
2010-03-18 16:45 ` [PATCH 0/2] Support for button reporting on jacks Takashi Iwai

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=20100317182242.GA990@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.