alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@bitmer.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Liam Girdwood <lrg@ti.com>, Tony Lindgren <tony@atomide.com>,
	alsa-devel@alsa-project.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/3] ASoC: tpa6130a2: model handling cleanup
Date: Tue, 30 Aug 2011 16:38:50 +0300	[thread overview]
Message-ID: <4E5CE7EA.4000101@bitmer.com> (raw)
In-Reply-To: <1314704394-31298-1-git-send-email-peter.ujfalusi@ti.com>

On 08/30/2011 02:39 PM, Peter Ujfalusi wrote:
> Hello,
>
> Small cleanup for the tpa6130a2 driver for model handling:
> Remove the model_id from platform_data, and use the device name/device_data
> to distinguish between the supported models of TPA.
>
> Regards,
> Peter
> ---
> Peter Ujfalusi (3):
>    ASoC: tpa6130a2: Model support cleanup
>    OMAP: RX51: No need to configure the tpa_model
>    ASoC: tpa6130a2: Remove model_id from platform data
>
>   arch/arm/mach-omap2/board-rx51-peripherals.c |    1 -
>   include/sound/tpa6130a2-plat.h               |    6 ------
>   sound/soc/codecs/tpa6130a2.c                 |   12 +++++++++---
>   3 files changed, 9 insertions(+), 10 deletions(-)
Tested-by: Jarkko Nikula <jarkko.nikula@bitmer.com>


  parent reply	other threads:[~2011-08-30 13:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-30 11:39 [PATCH 0/3] ASoC: tpa6130a2: model handling cleanup Peter Ujfalusi
2011-08-30 11:39 ` [PATCH 1/3] ASoC: tpa6130a2: Model support cleanup Peter Ujfalusi
2011-08-30 11:39 ` [PATCH 2/3] OMAP: RX51: No need to configure the tpa_model Peter Ujfalusi
2011-08-30 11:39 ` [PATCH 3/3] ASoC: tpa6130a2: Remove model_id from platform data Peter Ujfalusi
2011-08-30 13:38 ` Jarkko Nikula [this message]
2011-09-21 15:03   ` [PATCH 0/3] ASoC: tpa6130a2: model handling cleanup Mark Brown
2011-09-13 12:11 ` [alsa-devel] " Péter Ujfalusi
2011-09-13 12:27   ` Mark Brown
2011-09-13 14:53     ` Liam Girdwood

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=4E5CE7EA.4000101@bitmer.com \
    --to=jarkko.nikula@bitmer.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=tony@atomide.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).