On Tue, Feb 25, 2014 at 12:39:29PM +0900, Mark Brown wrote: > On Tue, Feb 25, 2014 at 11:13:14AM +0800, Nicolin Chen wrote: > > On Tue, Feb 25, 2014 at 12:09:47PM +0900, Mark Brown wrote: > > > > We should be able to arrange to have the ESAI be a clock provider > > > shouldn't we? If the clocks need to interface to other things (and they > > > do) then we should be able to use the standard interface we have to > > > clocks. > > > Excuse me, I think I just don't get the approach how to use clock API to > > standardize the MCLK derived from ESAI IP: it's surely not a fixed-clock > > so we couldn't register in DT and it's not SoC internal clock which means > > we couldn't register it in the SoC clock driver either. > > > Could you please shed me some light on it? > > So register it from the ESAI driver then. Then I think I need to find a way to pass the clock to CODEC driver... Anyway, I'll try it first. Thank you. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
