Messages in this thread | | | Date | Thu, 16 May 2013 11:55:45 -0700 | From | Sören Brinkmann <> | Subject | Re: [PATCH RFC] clk: Introduce userspace clock driver |
| |
On Thu, May 16, 2013 at 06:26:05PM +0100, Mark Brown wrote: > On Thu, May 16, 2013 at 10:44:16AM -0400, Philip Balister wrote: > > On 05/16/2013 12:28 AM, Saravana Kannan wrote: > > > > Agreed. I was about to reply with exactly the same point. I haven't done > > > any UIO coding, but that device file will eventually have to be opened. > > > Turn on the clocks in the open and turn them off at close. > > > > Rate to request can be a DT property. > > > But you are assuming each device implemented in the fpga uses one clock. > > This assumption is clearly not valid since devices will ahve to share > > clocks. > > 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.
Sören
-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |