On Fri 19 Sep 2008 05:35, [EMAIL PROTECTED] pondered: > * branches/2008R1/sound/soc/blackfin/Kconfig > * branches/2008R1/sound/soc/blackfin/bf5xx-ssm2602.c > > Diff > > > Modified: branches/2008R1/sound/soc/blackfin/Kconfig (5315 => 5316) > > > --- branches/2008R1/sound/soc/blackfin/Kconfig 2008-09-19 00:57:37 UTC > (rev 5315) > +++ branches/2008R1/sound/soc/blackfin/Kconfig 2008-09-19 09:35:06 UTC > (rev 5316) > @@ -51,6 +51,16 @@ > help > Say Y if you want to add support for SoC audio on BF527-EZKIT. > > +config SND_BF5XX_SOC_SSM2602_ADDR > + hex "I2c address to SSM2602 on a BF527" > + default 0x1b > + range 0x1a 0x1b > + depends on SND_BF5XX_SOC_SSM2602 > + help > + Set the address of the SSM 2602 to 0x1a or 0x1b based on the power-up condition > + on CSB where CSB high at startup is 0x1b. > + > + Defaults to 0x1b matching the BF527_EZKIT hardware. > > config SND_BF5XX_SOC_BF5xx > tristate "SoC AC97 Audio support for BF5xx"
I think we decided that putting hardware descriptions (like which the CSB pin is strapped) into the Kconfig was a bad idea, and thing should either actively probe things (try both addresses), or be in arch/blackfin/mach-bf527/boards/ezkit.c with the other parts of the hardware description... _______________________________________________ Linux-kernel-commits mailing list [email protected] http://blackfin.uclinux.org/mailman/listinfo/linux-kernel-commits
