All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH 1/4] ASoC: ssm2602: Split SPI and I2C code into different modules
Date: Tue, 18 Feb 2014 10:02:13 +0900	[thread overview]
Message-ID: <20140218010213.GM2669@sirena.org.uk> (raw)
In-Reply-To: <1392639416-11293-1-git-send-email-lars@metafoo.de>


[-- Attachment #1.1: Type: text/plain, Size: 1317 bytes --]

On Mon, Feb 17, 2014 at 01:16:53PM +0100, Lars-Peter Clausen wrote:
> There are a few known (minor) problems with having the support code for both I2C
> and SPI in the same module:
>     * We need to be extra careful to make sure to not build the driver into the
>       kernel if one of the subsystems is build as a module (Currently only SPI
>       can be build as a module).

I2C not SPI.

> This patch splits the AD193X driver into 3 modules. One core module that
> implements the device logic, but is independent of the bus method used. And one
> module for SPI and I2C each that registers the drivers and sets up the regmap
> struct for the bus.

No it doesn't, it splits the ssm2602 driver.

> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
> ---
>  sound/soc/blackfin/Kconfig     |   3 +-
>  sound/soc/codecs/Kconfig       |  11 ++-
>  sound/soc/codecs/Makefile      |   4 ++
>  sound/soc/codecs/ssm2602-i2c.c |  57 +++++++++++++++
>  sound/soc/codecs/ssm2602-spi.c |  41 +++++++++++
>  sound/soc/codecs/ssm2602.c     | 158 ++++++-----------------------------------
>  sound/soc/codecs/ssm2602.h     |  14 ++++

There also seem to be a bunch of arch/blackfin references to do this -
they should stay OK due to the select but it might be worth updating
them.

I'll apply this with the commit log edited.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



      parent reply	other threads:[~2014-02-18  1:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-17 12:16 [PATCH 1/4] ASoC: ssm2602: Split SPI and I2C code into different modules Lars-Peter Clausen
2014-02-17 12:16 ` [PATCH 2/4] ASoC: ad193x: " Lars-Peter Clausen
2014-02-18  1:06   ` Mark Brown
2014-02-17 12:16 ` [PATCH 3/4] ASoC: adav80x: Use devm_kzalloc() Lars-Peter Clausen
2014-02-18  1:08   ` Mark Brown
2014-02-17 12:16 ` [PATCH 4/4] ASoC: adav80x: Split SPI and I2C code into different modules Lars-Peter Clausen
2014-02-18  1:30   ` Mark Brown
2014-02-18  1:02 ` 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=20140218010213.GM2669@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.