[alsa-devel] [PATCH v3] ARM: kirkwood: extend the kirkwood i2s driver for DT usage
broonie at kernel.org
Tue Jul 23 19:16:50 CEST 2013
On Tue, Jul 23, 2013 at 04:19:56PM +0100, Russell King - ARM Linux wrote:
> On Tue, Jul 23, 2013 at 04:01:50PM +0100, Mark Brown wrote:
> > Why would platform data have anything to do with this? To repeat again
> > the way the clocks are mapped should be totally transparent to the
> > driver requesting them, if it isn't then the driver is not using the API
> > properly.
> Total rubbish. Of course the driver needs to know what the clocks are,
> so that it can program its hardware accordingly.
Of course, but why through platform data? Though reading your mail I
think we're talking at cross purposes here...
> In this case, it has always been the rule with the clock API that it
> shall be used as:
> clk_get(device, "internal");
> to get the internal clock, and:
> clk_get(device, "external");
> to get the external clock - or whatever names are appropriate to name the
> clock _inputs_.
This is exactly what I'd expect, yes - but it doesn't need the driver to
have platform data as far as I can see. As you say the driver should be
requesting the two clock inputs the IP has by name which doesn't need it
to have any platform data, it just needs code like you have above. The
board specific configuration is all handled within the clk_get() calls.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 836 bytes
Desc: Digital signature
More information about the Alsa-devel