ASoC: Blackfin: allow SPI for SSM2602 parts
PATCH 1/1 ASoC: Blackfin: allow SPI for SSM2602 parts
This board has hardware switches for selecting SPI or I2C, so don't require I2C for this driver.
--- sound/soc/blackfin/Kconfig | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-)
sound/soc/blackfin/Kconfig +1 -2
@@ -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.
Signature · 1 line
1.7.5.3
Quoted 5 lines · 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 <[email protected]>---
Mark Brown
AppliedQuoted 4 lines · 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 <[email protected]>
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).
Quoted 7 lines · Mark Brown
Quoted 2 lines · Mike Frysinger
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