devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@leon.nu>
To: grant.likely@secretlab.ca, rdunlap@xenotime.net, lrg@ti.com,
	broonie@opensource.wolfsonmicro.com, swarren@nvidia.com,
	olof@lixom.net, ccross@android.com
Cc: devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org,
	alsa-devel@alsa-project.org, linux-tegra@vger.kernel.org,
	Leon Romanovsky <leon@leon.nu>
Subject: [PATCH 0/3] Add device tree support of audio (ALC5632) on PAZ00 board and enable headphones autodetection.
Date: Wed, 25 Jan 2012 20:48:56 +0200	[thread overview]
Message-ID: <1327517336-29662-1-git-send-email-leon@leon.nu> (raw)


The following patchset is going to add device tree support of audio (ALC5632) on 
PAZ00 board and enable headphones autodetection.

Leon Romanovsky (3):
  ARM: dt: tegra: Enable device tree audio on PAZ00 board.
  ARM: tegra: Enable the headphone detection gpio on PAZ00 board.
  ASoC: dt: tegra: Enable headphone autodetection on PAZ00 board.

 .../devicetree/bindings/sound/alc5632.txt          |   24 ++++
 .../bindings/sound/tegra-audio-alc5632.txt         |   55 ++++++++++
 arch/arm/boot/dts/tegra-paz00.dts                  |   30 ++++-
 arch/arm/mach-tegra/board-paz00-pinmux.c           |    1 +
 arch/arm/mach-tegra/board-paz00.h                  |    3 +
 sound/soc/tegra/tegra_alc5632.c                    |  114 ++++++++++++++++++--
 6 files changed, 212 insertions(+), 15 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/sound/alc5632.txt
 create mode 100644 Documentation/devicetree/bindings/sound/tegra-audio-alc5632.txt

-- 
1.7.3.4


                 reply	other threads:[~2012-01-25 18:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1327517336-29662-1-git-send-email-leon@leon.nu \
    --to=leon@leon.nu \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=ccross@android.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=olof@lixom.net \
    --cc=rdunlap@xenotime.net \
    --cc=swarren@nvidia.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;
as well as URLs for NNTP newsgroup(s).