alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Stephen Warren <swarren@nvidia.com>
Cc: linux-tegra@vger.kernel.org, alsa-devel@alsa-project.org,
	broonie@opensource.wolfsonmicro.com
Subject: Re: [PATCH] ARM: tegra: Add to struct harmony_audio_platform_data
Date: Tue, 01 Feb 2011 14:01:46 +0000	[thread overview]
Message-ID: <1296568906.3327.14.camel@odin> (raw)
In-Reply-To: <1296513435-14792-1-git-send-email-swarren@nvidia.com>

On Mon, 2011-01-31 at 15:37 -0700, Stephen Warren wrote:
> Add fields to describe all the audio-related GPIOs on Harmony, except for
> the codec's GPIO IRQ, which will be passed in its i2c_board_info.
> 
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
> ---
> Mark, can you please apply this to your tegra-arch branch, and merge that.
> Thanks!
> 
>  arch/arm/mach-tegra/include/mach/harmony_audio.h |    3 +++
>  1 files changed, 3 insertions(+), 0 deletions(-)
> 
> diff --git a/arch/arm/mach-tegra/include/mach/harmony_audio.h b/arch/arm/mach-tegra/include/mach/harmony_audio.h
> index 5c46391..af08650 100644
> --- a/arch/arm/mach-tegra/include/mach/harmony_audio.h
> +++ b/arch/arm/mach-tegra/include/mach/harmony_audio.h
> @@ -16,4 +16,7 @@
>  
>  struct harmony_audio_platform_data {
>  	int gpio_spkr_en;
> +	int gpio_hp_det;
> +	int gpio_int_mic_en;
> +	int gpio_ext_mic_en;
>  };


Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>
-- 
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk

  reply	other threads:[~2011-02-01 14:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-31 22:37 [PATCH] ARM: tegra: Add to struct harmony_audio_platform_data Stephen Warren
2011-02-01 14:01 ` Liam Girdwood [this message]
2011-02-01 14:17 ` 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=1296568906.3327.14.camel@odin \
    --to=lrg@slimlogic.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-tegra@vger.kernel.org \
    --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).