On 2018-05-02 20:10:46 [+0200], Alexandre Belloni wrote:
> > > As said below, this is solving multiple issues, including the one for
> > > SoCs that don't have the PIT.
> > will the PIT be removed? Where it needs the PIT?
> >
>
> The last patch is unselecting the PIT driver so by default it is
On 2018-05-02 20:10:46 [+0200], Alexandre Belloni wrote:
> > > As said below, this is solving multiple issues, including the one for
> > > SoCs that don't have the PIT.
> > will the PIT be removed? Where it needs the PIT?
> >
>
> The last patch is unselecting the PIT driver so by default it is
On 02/05/2018 15:34:18+0200, Sebastian Andrzej Siewior wrote:
> On 2018-04-26 20:52:33 [+0200], Alexandre Belloni wrote:
> >
> > I don't remember you posted anything for the TCB. Wasn't it focused on
> > getting rid of the PIT irq?
>
> the PIT irq which was shared with the UART one some devices,
On 02/05/2018 15:34:18+0200, Sebastian Andrzej Siewior wrote:
> On 2018-04-26 20:52:33 [+0200], Alexandre Belloni wrote:
> >
> > I don't remember you posted anything for the TCB. Wasn't it focused on
> > getting rid of the PIT irq?
>
> the PIT irq which was shared with the UART one some devices,
On 2018-04-26 20:52:33 [+0200], Alexandre Belloni wrote:
>
> I don't remember you posted anything for the TCB. Wasn't it focused on
> getting rid of the PIT irq?
the PIT irq which was shared with the UART one some devices, yes this
was part of it. The other essential piece was using a higher
On 2018-04-26 20:52:33 [+0200], Alexandre Belloni wrote:
>
> I don't remember you posted anything for the TCB. Wasn't it focused on
> getting rid of the PIT irq?
the PIT irq which was shared with the UART one some devices, yes this
was part of it. The other essential piece was using a higher
On 26/04/2018 18:46:23+0200, Sebastian Andrzej Siewior wrote:
> On 2018-04-18 12:51:37 [+0200], Alexandre Belloni wrote:
> > Hi,
>
> Hi,
>
> please keep on Cc if you intend to repost this.
>
Sure, I'll do.
> > This series gets back on the TCB drivers rework. It introduces a new driver
> > to
On 26/04/2018 18:46:23+0200, Sebastian Andrzej Siewior wrote:
> On 2018-04-18 12:51:37 [+0200], Alexandre Belloni wrote:
> > Hi,
>
> Hi,
>
> please keep on Cc if you intend to repost this.
>
Sure, I'll do.
> > This series gets back on the TCB drivers rework. It introduces a new driver
> > to
On 2018-04-18 12:51:37 [+0200], Alexandre Belloni wrote:
> Hi,
Hi,
please keep on Cc if you intend to repost this.
> This series gets back on the TCB drivers rework. It introduces a new driver to
> handle the clocksource and clockevent devices.
So you don't want the old thing we have in -RT. I
On 2018-04-18 12:51:37 [+0200], Alexandre Belloni wrote:
> Hi,
Hi,
please keep on Cc if you intend to repost this.
> This series gets back on the TCB drivers rework. It introduces a new driver to
> handle the clocksource and clockevent devices.
So you don't want the old thing we have in -RT. I
Hi,
This series gets back on the TCB drivers rework. It introduces a new driver to
handle the clocksource and clockevent devices.
As a reminder, 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
Hi,
This series gets back on the TCB drivers rework. It introduces a new driver to
handle the clocksource and clockevent devices.
As a reminder, 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
12 matches
Mail list logo
