On Sat, Feb 15, 2014 at 12:53 AM, Laurent Pinchart <laurent.pinch...@ideasonboard.com> wrote: > On Friday 14 February 2014 10:58:22 Mark Rutland wrote: >> On Fri, Feb 14, 2014 at 01:00:01AM +0000, Laurent Pinchart wrote: >> > +Channels Optional Properties: >> > + >> > + - clock-source-rating: rating of the timer as a clock source device. >> > + - clock-event-rating: rating of the timer as a clock event device. >> >> This feels like a leak of Linux internals. Why do you need this? > > You're right, it is. The clock source and clock event ratings are currently > configured through platform data, I'll need to find a way to compute them in > the driver instead.
That would be very good! > There's still one piece of Linux-specific data I need though, as I need to > specify for each channel whether to use it as a clock source device, a clock > event device, both of them or none. That's configuration information that > needs to be provided somehow. I think you can decide clock source or clock event assignment based on number of channels available. If you have only a single channel then both clock event and clock source need to be supported. Otherwise use one channel for clock source and the rest for clock events. This is probably out of scope for this DT conversion, but it would be neat if you somehow could specify the CPU affinity for a channel to tie a clock event to an individual CPU core. This would make a a per-cpu timer unless I'm mistaken. But that's more of a software policy than anything else. Thanks, / magnus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
