Hi,
On Wed, Mar 29, 2017 at 11:22:10AM +0200, Daniel Lezcano wrote:
> On Tue, Mar 28, 2017 at 08:51:46PM -0500, Rob Herring wrote:
> > On Wed, Mar 22, 2017 at 06:48:28PM +0300, Alexander Kochetkov wrote:
> > > From: Daniel Lezcano <daniel.lezcano@xxxxxxxxxx>
> > >
> > > The CLOCKSOURCE_OF_DECLARE() was introduced before the
> > > CLOCKEVENT_OF_DECLARE() and that resulted in some abuse where the
> > > clockevent and the clocksource are both initialized in the same init
> > > routine.
> > >
> > > With the introduction of the CLOCKEVENT_OF_DECLARE(), the driver can
> > > now split the clocksource and the clockevent init code. However, the
> > > device tree may specify a single node, so the same node will be passed
> > > to the clockevent/clocksource's init function, with the same base
> > > address.
> > >
> > > with this patch it is possible to specify an attribute to the timer's node to
> > > specify if it is a clocksource or a clockevent and define two timers node.
> >
> > Daniel and I discussed and agreed against this a while back. What
> > changed?
>
> Hi Rob,
>
> > > For example:
> > >
> > > timer: timer@98400000 {
> > > compatible = "moxa,moxart-timer";
> > > reg = <0x98400000 0x42>;
> >
> > This overlaps the next node. You can change this to 0x10, but are these
> > really 2 independent h/w blocks? Don't design the nodes around the
> > current needs of Linux.
>
> Mmh, thanks for raising this. Conceptually speaking there are two (or more)
> different entities, the clocksource and the clockevents but they share the same
> IP block.
>From the DT's PoV, this is one entity, which is the IP block.
The clocksource/clockevent concept is a Linux implementation detail. The
DT cannot and should not be aware of that.
[...]
> > > interrupts = <19 1>;
> > > clocks = <&coreclk>;
> > > clockevent;
> >
> > This is not needed. The presence of "interrupts" is enough to say use
> > this timer for clockevent.
>
> Yes, that is true if no drivers was already taking CLOCKSOURCE_OF and
> initializing the clockevent. The driver will pass through the clocksource_probe
> function, check the interrupt and bail out because there is an interrupt
> declared and assume it is a clockevent, so no initialization for the driver.
> IOW, it is not backward compatible.
>
> We need this attribute somehow in order to separate clearly a clocksource or a
> clockevent with a new implementation.
Why? A single IP block can provide the functionality of both (though
there are reasons that functionality may be mutually exclusive). What is
the benefit of this split?
> > > With this approach, we allow a mechanism to clearly define a clocksource or a
> > > clockevent without aerobatics we can find around in some drivers:
> > > timer-sp804.c, arc-timer.c, dw_apb_timer_of.c, mps2-timer.c,
> > > renesas-ostm.c, time-efm32.c, time-lpc32xx.c.
> >
> > These all already have bindings and work. What problem are you trying to
> > solve other than restructuring Linux?
>
> Yes, there is already the bindings, but that force to do some hackish
> initialization.
Here, you are forcing hackish DT changes that do not truly describe HW.
How is that better?
> I would like to give the opportunity to declare separately a clocksource and a
> clockevent, in order to have full control of how this is initialized.
To me it sounds like what we need is Linux infrastructure that allows
one to register a device as having both clockevent/clocksource
functionality.
That way, we can choose to do something sane at boot time, and if the
user really wants specific devices used in specific ways, they can
request that.
Thanks,
Mark.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
