[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170607231715.ns2vcxza2eexnzjs@piout.net>
Date: Thu, 8 Jun 2017 01:17:15 +0200
From: Alexandre Belloni <alexandre.belloni@...e-electrons.com>
To: Daniel Lezcano <daniel.lezcano@...aro.org>
Cc: Nicolas Ferre <nicolas.ferre@...rochip.com>,
Boris Brezillon <boris.brezillon@...e-electrons.com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 46/58] clocksource/drivers: Add a new driver for the
Atmel ARM TC blocks
On 07/06/2017 at 23:08:48 +0200, Daniel Lezcano wrote:
> > I was going to agree but this is not flexible enough because the
> > quadrature decoder always uses the first two channels. So on some
> > products, we may have:
> > - TCB0:
> > o channels 0,1: qdec
> > o channel 2: clocksource
> >
> > - TCB1:
> > o channels 0,1: qdec
> > o channel 2: clockevent
> >
> > This avoids wasting TCB channels.
>
> Ok. In this case you can check if the interrupt is specified for the node, if
> yes, then it is a clockevent.
>
But currently it is always specified in the SoC's dtsi. I don't find
that too practical to push that to the board's dts. Also, lying by
omission (the IRQ is always wired) in the DT is not different from
having a property selecting which timer is the clocksource and which is
the clockevent.
--
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
Powered by blists - more mailing lists