Messages in this thread | | | Date | Fri, 17 May 2013 12:02:41 +0100 | From | Mark Brown <> | Subject | Re: [PATCH RFC] clk: Introduce userspace clock driver |
| |
On Thu, May 16, 2013 at 11:55:45AM -0700, Sören Brinkmann wrote: > On Thu, May 16, 2013 at 06:26:05PM +0100, Mark Brown wrote:
> > The binding should obviously be defined as a set of clocks rather than a > > single clock - something like how we specify regulators on PMICs > > probably makes sense. Each clock can have its own properties.
> For a device driver as clock consumer, the bindings etc. are well > defined. Just add the 'clocks' and 'clock-names' props and use the CCF.
That's not really intended to be used for enumeration by the child, though - you'd at least need to define that the child looks through the same binding to figure out what clocks to request. [unhandled content-type:application/pgp-signature] | |