On 2018-11-08 15:09:35 [+0100], Alexandre Belloni wrote:
> It is not part of that series as I prefer to keep the discussion of how
> to configure that for later. This has been raised previously without any
> conclusion and I'd really like to see this rework enter upstream soon.
Okay. Does it make
On 08/11/2018 13:43:27+0100, Sebastian Andrzej Siewior wrote:
> On 2018-09-25 22:14:56 [+0200], Alexandre Belloni wrote:
> > On 22/09/2018 13:29:48+0200, Daniel Lezcano wrote:
> > > You say for rt the PIT is not suitable because of the shared irq but in
> > > the driver, the interrupt is flagged as
On 2018-09-25 22:14:56 [+0200], Alexandre Belloni wrote:
> On 22/09/2018 13:29:48+0200, Daniel Lezcano wrote:
> > You say for rt the PIT is not suitable because of the shared irq but in
> > the driver, the interrupt is flagged as shared.
> >
>
> Well, it is not simply sharing the interrupt that i
On 22/09/2018 13:29:48+0200, Daniel Lezcano wrote:
> On 13/09/2018 13:30, Alexandre Belloni wrote:
> > Hi,
> >
> > This series reworks the Atmel TCB drivers. It introduces a new driver to
> > handle
> > the clocksource and clockevent devices.
> >
> > This is necessary because:
> > - the current
On 13/09/2018 13:30, Alexandre Belloni wrote:
> Hi,
>
> This series reworks the Atmel TCB drivers. It introduces a new driver to
> handle
> the clocksource and clockevent devices.
>
> This is necessary because:
> - the current tcb_clksrc driver is probed too late to be able to be used at
>b
Hi,
This series reworks the Atmel TCB drivers. It introduces a new driver to handle
the clocksource and clockevent devices.
This is necessary because:
- the current tcb_clksrc driver is probed too late to be able to be used at
boot and we now have SoCs that don't have a PIT. They currently ar
6 matches
Mail list logo
