From: Leon Romanovsky <leon@leon.nu>
To: broonie@opensource.wolfsonmicro.com, lrg@ti.com,
swarren@nvidia.com, alsa-devel@alsa-project.org, olof@lixom.net,
linux-tegra@vger.kernel.org
Cc: Leon Romanovsky <leon@leon.nu>
Subject: [PATCH 0/5] Add device tree support of audio (ALC5632) on PAZ00 board
Date: Tue, 31 Jan 2012 09:25:57 +0200 [thread overview]
Message-ID: <1327994757-26950-1-git-send-email-leon@leon.nu> (raw)
The following patchset is going to:
* add device tree support of audio (ALC5632) on PAZ00 board.
* enable headset autodetection.
* enable headset microphone.
---
I will update the ALC5632 codec to routing names used in documentation, in the later patches,
Leon Romanovsky (5):
ASoC: Tegra+ALC5632: Implement device tree support in board file
ASoC: ALC5632: Add device tree binding documentation
ASoC: Tegra+ALC5632 machine: Add device tree binding documentation
ASoC: dt: tegra: Enable headset autodetection on PAZ00 board.
ASoC: tegra: Remove unused DAPM route structure.
.../devicetree/bindings/sound/alc5632.txt | 24 ++++
.../bindings/sound/tegra-audio-alc5632.txt | 57 +++++++++
.../devicetree/bindings/vendor-prefixes.txt | 1 +
arch/arm/boot/dts/tegra-paz00.dts | 1 +
sound/soc/tegra/tegra_alc5632.c | 129 +++++++++++++++----
5 files changed, 185 insertions(+), 27 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
next reply other threads:[~2012-01-31 7:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 7:25 Leon Romanovsky [this message]
[not found] ` <1327994757-26950-1-git-send-email-leon-2ukJVAZIZ/Y@public.gmane.org>
2012-01-31 18:00 ` [PATCH 0/5] Add device tree support of audio (ALC5632) on PAZ00 board Stephen Warren
2012-01-31 19:42 ` Mark Brown
[not found] ` <20120131194249.GF3429-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-02-01 6:45 ` Leon Romanovsky
2012-02-01 7:12 ` Olof Johansson
2012-01-31 19:33 ` 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=1327994757-26950-1-git-send-email-leon@leon.nu \
--to=leon@leon.nu \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-tegra@vger.kernel.org \
--cc=lrg@ti.com \
--cc=olof@lixom.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).