Dear Arnd
On Tue, 3 Nov 2015 09:49:32 +0100
Arnd Bergmann wrote:
> On Tuesday 03 November 2015 14:59:40 Jisheng Zhang wrote:
> > > On Monday 02 November 2015 11:03:34 Jisheng Zhang wrote:
> > > > On Fri, 30 Oct 2015 13:42:01 +0100 Arnd Bergmann wrote:
> > > I'd be happier with a solution th
On Tuesday 03 November 2015 14:59:40 Jisheng Zhang wrote:
> > On Monday 02 November 2015 11:03:34 Jisheng Zhang wrote:
> > > On Fri, 30 Oct 2015 13:42:01 +0100 Arnd Bergmann wrote:
> > I'd be happier with a solution that keeps the DT describing the hardware
> > and not the way we expect Linux to
Dear Arnd,
On Mon, 2 Nov 2015 22:56:02 +0100
Arnd Bergmann wrote:
> On Monday 02 November 2015 11:03:34 Jisheng Zhang wrote:
> > On Fri, 30 Oct 2015 13:42:01 +0100 Arnd Bergmann wrote:
> > >
> > > This is not ideal from an overall maintenance perspective. We want to
> > > be able to have a ker
On Monday 02 November 2015 11:03:34 Jisheng Zhang wrote:
> On Fri, 30 Oct 2015 13:42:01 +0100 Arnd Bergmann wrote:
> >
> > This is not ideal from an overall maintenance perspective. We want to
> > be able to have a kernel with all drivers enabled that gives us the
> > best behavior on all platform
On Monday 02 November 2015 09:48:38 Daniel Lezcano wrote:
> If I follow the logic of arch_arm_timer is better than dw_apb timer.
>
> 1. The arch_arm_timer is present
>
> => dw_apb timer is not used at all
>
> CONFIG_ARM_ARCH_TIMER=y
> # CONFIG_DW_APB_TIMER is not set
>
> 2. The arch_arm_t
Dear Daniel,
On Mon, 2 Nov 2015 09:48:38 +0100
Daniel Lezcano wrote:
> On 11/02/2015 03:51 AM, Jisheng Zhang wrote:
> > Dear Daniel,
> >
> > On Fri, 30 Oct 2015 13:37:01 +0100
> > Daniel Lezcano wrote:
> >
> >> On 10/30/2015 12:09 PM, Jisheng Zhang wrote:
> >>> Dear Daniel,
> >>>
> >>> On Fr
On 11/02/2015 03:51 AM, Jisheng Zhang wrote:
Dear Daniel,
On Fri, 30 Oct 2015 13:37:01 +0100
Daniel Lezcano wrote:
On 10/30/2015 12:09 PM, Jisheng Zhang wrote:
Dear Daniel,
On Fri, 30 Oct 2015 11:44:46 +0100
Daniel Lezcano wrote:
On 10/30/2015 09:27 AM, Jisheng Zhang wrote:
Implement an
Dear Arnd and Daniel,
On Fri, 30 Oct 2015 13:42:01 +0100
Arnd Bergmann wrote:
> On Friday 30 October 2015 19:09:29 Jisheng Zhang wrote:
> > > > diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig
> > > > index a7726db..7b081805 100644
> > > > --- a/drivers/clocksource/Kconfig
>
Dear Daniel,
On Fri, 30 Oct 2015 13:37:01 +0100
Daniel Lezcano wrote:
> On 10/30/2015 12:09 PM, Jisheng Zhang wrote:
> > Dear Daniel,
> >
> > On Fri, 30 Oct 2015 11:44:46 +0100
> > Daniel Lezcano wrote:
> >
> >> On 10/30/2015 09:27 AM, Jisheng Zhang wrote:
> >>> Implement an ARM delay timer
On Friday 30 October 2015 19:09:29 Jisheng Zhang wrote:
> > > diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig
> > > index a7726db..7b081805 100644
> > > --- a/drivers/clocksource/Kconfig
> > > +++ b/drivers/clocksource/Kconfig
> > > @@ -29,6 +29,16 @@ config DW_APB_TIMER_OF
>
On 10/30/2015 12:09 PM, Jisheng Zhang wrote:
Dear Daniel,
On Fri, 30 Oct 2015 11:44:46 +0100
Daniel Lezcano wrote:
On 10/30/2015 09:27 AM, Jisheng Zhang wrote:
Implement an ARM delay timer to be used for udelay(). This allows us to
skip the delay loop calibration at boot on Marvell BG2, BG2Q
Dear Daniel,
On Fri, 30 Oct 2015 11:44:46 +0100
Daniel Lezcano wrote:
> On 10/30/2015 09:27 AM, Jisheng Zhang wrote:
> > Implement an ARM delay timer to be used for udelay(). This allows us to
> > skip the delay loop calibration at boot on Marvell BG2, BG2Q, BG2CD
> > platforms. And after this p
On 10/30/2015 09:27 AM, Jisheng Zhang wrote:
Implement an ARM delay timer to be used for udelay(). This allows us to
skip the delay loop calibration at boot on Marvell BG2, BG2Q, BG2CD
platforms. And after this patch, udelay() will be unaffected by CPU
frequency changes.
Signed-off-by: Jisheng Z
Dear Daniel,
On Fri, 30 Oct 2015 16:27:39 +0800
Jisheng Zhang wrote:
> Implement an ARM delay timer to be used for udelay(). This allows us to
> skip the delay loop calibration at boot on Marvell BG2, BG2Q, BG2CD
> platforms. And after this patch, udelay() will be unaffected by CPU
> frequency c
Implement an ARM delay timer to be used for udelay(). This allows us to
skip the delay loop calibration at boot on Marvell BG2, BG2Q, BG2CD
platforms. And after this patch, udelay() will be unaffected by CPU
frequency changes.
Signed-off-by: Jisheng Zhang
---
drivers/clocksource/Kconfig
On 10/20/2015 10:11 AM, Jisheng Zhang wrote:
Implement an ARM delay timer to be used for udelay(). This allows us to
skip the delay loop calibration at boot on Marvell BG2, BG2Q, BG2CD
platforms. And after this patch, udelay() will be unaffected by CPU
frequency changes.
But, this driver is not
Implement an ARM delay timer to be used for udelay(). This allows us to
skip the delay loop calibration at boot on Marvell BG2, BG2Q, BG2CD
platforms. And after this patch, udelay() will be unaffected by CPU
frequency changes.
But, this driver is not only used on ARM platforms, so I dunno how to
h
17 matches
Mail list logo