Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ben Dooks <ben-alsa@fluff.org>
Cc: alsa-devel@alsa-project.org, Ben Dooks <ben-linux@fluff.org>
Subject: Re: AUDIO: Split WM8750 IO routines from core for SPI
Date: Mon, 23 Jun 2008 15:42:17 +0100	[thread overview]
Message-ID: <20080623144217.GD9318@sirena.org.uk> (raw)
In-Reply-To: <20080623115406.920274505@fluff.org.uk>

On Mon, Jun 23, 2008 at 12:54:07PM +0100, Ben Dooks wrote:
> Add SPI support to the WM8750 ASoC codec by splitting
> the I2C out of the WM8750 codec and adding an standard
> SPI driver to the system.

This looks good.  My only substantial concern with it is that it means
that this driver isn't consistent with the other codec drivers since
there are now three modules built for it - one for the core and one for
each bus type.  Would it be possible to integrate the SPI support into
the main WM8750 driver or are there substantial drawbacks from doing
that?  The main thing is ending up loading SPI when it's not needed but
I'm not sure how big a cost that is or if there's anything else?

Also (very minor, but it'll get picked up on):

> -static int wm8750_suspend(struct platform_device *pdev, pm_message_t state)
> +int wm8750_suspend(struct platform_device *pdev, pm_message_t state)
>  {
>  	struct snd_soc_device *socdev = platform_get_drvdata(pdev);
>  	struct snd_soc_codec *codec = socdev->codec;
> @@ -760,7 +759,9 @@ static int wm8750_suspend(struct platfor
>  	return 0;
>  }
>  
> -static int wm8750_resume(struct platform_device *pdev)
> +EXPORT_SYMBOL_GPL(wm8750_suspend);

checkpatch will want there to be no space between the function and the
EXPORT_SYMBOL_GPL() for it.

      parent reply	other threads:[~2008-06-23 14:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23 11:54 AUDIO: Split WM8750 IO routines from core for SPI Ben Dooks
2008-06-23 12:28 ` Takashi Iwai
2008-06-23 14:42 ` Mark Brown [this message]

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=20080623144217.GD9318@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=ben-alsa@fluff.org \
    --cc=ben-linux@fluff.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