Hello.
Felipe Balbi wrote:
It's not so actually. This depends on the matching mechanism
established within clkdev: by device, by name, or by both. Not all
implementations will match by device, e.g. DA8xx/OMAP-L1x will match by
clock name.
then it has to be fixed. The name shouldn't matter.
It's not always feasible to do as you say. The same clock can be used
by more than two drivers, or the clock may be used out of driver context
altogether.
This was a big
discussion when Russell came up with the clkdev stuff and I remember
clearly that clock names shouldn't be passed down to drivers because
they don't matter.
Why then there are two matching mechanisms in the clkdev code?
WBR, Sergei
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
