Hi, On Fri, Dec 7, 2012 at 7:21 PM, Grant Likely <grant.likely@xxxxxxxxxxxx> wrote: > On Thu, 6 Dec 2012 13:11:42 +0900, Mark Brown <broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote: >> On Thu, Dec 06, 2012 at 09:31:40AM +0530, Padma Venkat wrote: >> > On Wed, Nov 28, 2012 at 4:17 PM, Padmavathi Venna <padma.v@xxxxxxxxxxx> wrote: >> >> > > Padmavathi Venna (2): >> > > ASoC: Samsung: Get I2S src_clk from clock alias id. >> > > ASoC: SAMSUNG: Add DT support for i2s >> >> > Any comments on DT support for i2s patch? If not when this patch can be pulled? >> >> Don't send contentless pings. >> >> I still don't really like what's going on with aliases here, I need to >> understand why things are structured the way they are to say something >> about that. > > Right. On a brief look, it appears that the binding is using aliases as > a way to encode implementation specific details of the driver. Samsung i2s driver registers the platform device twice one for the samsung-i2s.0,1 or 2 and two for samsung-i2s.4(which actually doesn't represent any H/W peripheral). The max number of I2S blocks on any Samsung SoC are 3, the secondary device registration starts with device number 4.The second time registration is for the secondary fifo interface of a CPU dai if any exists. With DT support the device number in the driver is always -1, I used alias id for the above purpose. > > g. > Thanks Padma -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |