Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dylan Reid <dgreid@chromium.org>
To: alsa-devel@alsa-project.org
Cc: lars@metafoo.de, zhengxing@rock-chips.com, tiwai@suse.de,
	lgirdwood@gmail.com, broonie@kernel.org,
	Dylan Reid <dgreid@chromium.org>
Subject: [RFC 0/5] Add a gpio jack device
Date: Fri, 22 May 2015 15:09:18 -0700	[thread overview]
Message-ID: <1432332563-15447-1-git-send-email-dgreid@chromium.org> (raw)

The first three changes add a gpio audio jack device.  This device can
be used on systems that report headphone or mic plug through GPIOS.
There can be 0-N of these devices created per board each can report one
of several events.  For example, this allows for a single jack for
HP/Mic and a separate jack for line out.

The last two patches are an example of the jack being used on Acer's
Tegra Chromebook, those can be considered separately and might not be
worth the churn.

Dylan Reid (5):
  ALSA: Add jack types to dt-bindings
  ASoC: jack - make add_gpiods accept pre-filled descriptors
  ASoC: Add GPIO based jack device
  ASoC: tegra_max98090: Change nyan to use gpio-jack
  ARM: tegra: nyan: specify gpio-audio-jack device

 .../devicetree/bindings/sound/gpio-audio-jack.txt  |  39 +++++
 arch/arm/boot/dts/tegra124-nyan.dtsi               |  22 ++-
 include/dt-bindings/sound/audio-jack-events.h      |   9 +
 sound/soc/codecs/Kconfig                           |   4 +
 sound/soc/codecs/Makefile                          |   2 +
 sound/soc/codecs/gpio-audio-jack.c                 | 191 +++++++++++++++++++++
 sound/soc/soc-jack.c                               |   9 +-
 sound/soc/tegra/tegra_max98090.c                   | 107 +++---------
 8 files changed, 291 insertions(+), 92 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/sound/gpio-audio-jack.txt
 create mode 100644 include/dt-bindings/sound/audio-jack-events.h
 create mode 100644 sound/soc/codecs/gpio-audio-jack.c

-- 
2.2.1.62.g3f15098

             reply	other threads:[~2015-05-22 22:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-22 22:09 Dylan Reid [this message]
2015-05-22 22:09 ` [RFC 1/5] ALSA: Add jack types to dt-bindings Dylan Reid
2015-05-25 12:11   ` Mark Brown
2015-05-22 22:09 ` [RFC 2/5] ASoC: jack - add_gpiods accepts filled descriptors Dylan Reid
2015-05-25 12:12   ` Mark Brown
2015-05-22 22:09 ` [RFC 3/5] ASoC: Add GPIO based jack device Dylan Reid
2015-05-25 12:11   ` Mark Brown
2015-05-26  6:20     ` Dylan Reid
2015-05-22 22:09 ` [RFC 4/5] ASoC: tegra_max98090: Change nyan to use gpio-jack Dylan Reid
2015-05-22 22:09 ` [RFC 5/5] ARM: tegra: nyan: specify gpio-audio-jack device Dylan Reid
2015-05-25 15:17 ` [RFC 0/5] Add a gpio jack device Lars-Peter Clausen
2015-05-25 17:15   ` Mark Brown
2015-05-25 18:58     ` Dylan Reid
2015-05-26 18:43     ` Lars-Peter Clausen
2015-05-26 20:14       ` Mark Brown
2015-05-27  4:22         ` Dylan Reid
2015-05-27 11:15           ` Lars-Peter Clausen
2015-05-27 17:26           ` Mark Brown
2015-05-28  5:38             ` Dylan Reid
2015-05-28 10:17               ` Mark Brown
2015-05-27 11:12         ` Lars-Peter Clausen
2015-05-28 19:35           ` Mark Brown

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=1432332563-15447-1-git-send-email-dgreid@chromium.org \
    --to=dgreid@chromium.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=tiwai@suse.de \
    --cc=zhengxing@rock-chips.com \
    /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