linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] ALSA: ARM: add Raumfeld audio support
Date: Fri, 27 Nov 2009 11:34:49 +0000	[thread overview]
Message-ID: <20091127113449.GB29821@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1259258341-31114-3-git-send-email-daniel@caiaq.de>

On Thu, Nov 26, 2009 at 06:59:00PM +0100, Daniel Mack wrote:

> +static struct regulator_consumer_supply audio_va_consumer_supply =
> +	REGULATOR_SUPPLY("va", "soc-audio.0");

I hadn't spotted this in your cs4270 patches but the device used should
be the I2C device, not the soc-audio device.  I'd also expect to see
this regulator setup done in arch/arm - the stuff I'd expect to see in
here is the resource claiming stuff.  Having it here is also fine, it's
just a little surprising.

> +static int raumfeld_ak4104_init(struct snd_soc_codec *codec)
> +{
> +	return 0;
> +}

Remove empty functions like this (I think this is the only one that's
left).

> +static int __init raumfeld_audio_init(void)
> +{
> +	int ret;
> +
> +	if (!machine_is_raumfeld_speaker() &&
> +	    !machine_is_raumfeld_connector())
> +		return 0;
> +
> +	max9486_client = i2c_new_device(i2c_get_adapter(0),
> +					&max9486_hwmon_info);
> +
> +	if (!max9486_client)
> +		return -ENOMEM;

I'd still really prefer to see this as a regular I2C device driver with
the code in arch/arm (even if the driver itself ends up embedded in this
file, which is what GTA01 did for a similar situation) but I guess I'm
OK.  max9486_hwmon_info could be renamed, though.

> +       platform_add_devices(regulator_devices, ARRAY_SIZE(regulator_devices));

Nothing ever reverses this (one of the reasons to shove this bit into
arch/arm :) ).

  parent reply	other threads:[~2009-11-27 11:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-26 17:58 ARM: pxa: add support for Raumfeld audio devices [v2] Daniel Mack
2009-11-26 17:58 ` [PATCH 1/3] ARM: pxa/raumfeld: add platform support Daniel Mack
2009-11-26 17:59   ` [PATCH 2/3] ALSA: ARM: add Raumfeld audio support Daniel Mack
2009-11-26 17:59     ` [PATCH 3/3] ARM: pxa/raumfeld: Add defconfig Daniel Mack
2009-11-27 11:34     ` Mark Brown [this message]
2009-11-27 12:42       ` [PATCH 2/3] ALSA: ARM: add Raumfeld audio support Daniel Mack
2009-11-26 19:13   ` [PATCH 1/3] ARM: pxa/raumfeld: add platform support Marek Vasut
2009-11-26 19:17     ` Daniel Mack
2009-11-26 19:18     ` Russell King - ARM Linux
2009-11-26 22:11       ` Marek Vasut
2009-11-26 22:19         ` Russell King - ARM Linux
2009-11-27  1:49           ` Marek Vasut
2009-11-27  8:50             ` Russell King - ARM Linux
2009-11-27  5:46   ` Eric Miao
2009-11-27 10:27     ` Daniel Mack
  -- strict thread matches above, loose matches on Subject: below --
2009-11-27 12:47 ARM: pxa: add support for Raumfeld audio devices [v3] Daniel Mack
2009-11-27 12:47 ` [PATCH 1/3] ARM: pxa/raumfeld: add platform support Daniel Mack
2009-11-27 12:47   ` [PATCH 2/3] ALSA: ARM: add Raumfeld audio support Daniel Mack
2009-11-27 16:48     ` 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=20091127113449.GB29821@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).