[PATCH] ASoC: Blackfin: allow SPI for SSM2602 parts

[PATCH] ASoC: Blackfin: allow SPI for SSM2602 parts

[Mike Frysinger]

This board has hardware switches for selecting SPI or I2C, so don't
require I2C for this driver.

Signed-off-by: Mike Frysinger <vapier@gentoo.org>
---
 sound/soc/blackfin/Kconfig |    3 +--
 1 files changed, 1 insertions(+), 2 deletions(-)

diff --git a/sound/soc/blackfin/Kconfig b/sound/soc/blackfin/Kconfig
index 4d361bd..871308f 100644
--- a/sound/soc/blackfin/Kconfig
+++ b/sound/soc/blackfin/Kconfig
@@ -10,10 +10,9 @@ config SND_BF5XX_I2S
 
 config SND_BF5XX_SOC_SSM2602
 	tristate "SoC SSM2602 Audio support for BF52x ezkit"
-	depends on SND_BF5XX_I2S
+	depends on SND_BF5XX_I2S && (SPI_MASTER || I2C)
 	select SND_BF5XX_SOC_I2S
 	select SND_SOC_SSM2602
-	select I2C
 	help
 	  Say Y if you want to add support for SoC audio on BF527-EZKIT.
 
-- 
1.7.5.3

Re: [PATCH] ASoC: Blackfin: allow SPI for SSM2602 parts

[Liam Girdwood]

On 17/06/11 03:24, Mike Frysinger wrote:
> This board has hardware switches for selecting SPI or I2C, so don't
> require I2C for this driver.
> 
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
> ---

Acked-by: Liam Girdwood <lrg@ti.com>

Re: [PATCH] ASoC: Blackfin: allow SPI for SSM2602 parts

[Mark Brown]

On Thu, Jun 16, 2011 at 10:24:15PM -0400, Mike Frysinger wrote:
> This board has hardware switches for selecting SPI or I2C, so don't
> require I2C for this driver.
> 
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>

Applied, though I suspect this won't actually load as the different bus
will change the name the CODEC uses to register with the subsystem (so
we can address multiple CODECs).

Re: [uclinux-dist-devel] [PATCH] ASoC: Blackfin: allow SPI for SSM2602 parts

[Mike Frysinger]

On Fri, Jun 17, 2011 at 05:41, Mark Brown wrote:
> On Thu, Jun 16, 2011 at 10:24:15PM -0400, Mike Frysinger wrote:
>> This board has hardware switches for selecting SPI or I2C, so don't
>> require I2C for this driver.
>
> Applied, though I suspect this won't actually load as the different bus
> will change the name the CODEC uses to register with the subsystem (so
> we can address multiple CODECs).

yes, i vaguely recall having to tweak the string name to something
like "spi0.4".  i think this gets back to our discussion about pushing
things into the platform resources.
-mike