Re: [PATCH v24 09/11] acpi/arm64: Add memory-mapped timer support in GTDT driver

2017-04-19 Thread Lorenzo Pieralisi
On Wed, Apr 19, 2017 at 04:45:54PM +0100, Mark Rutland wrote: > On Wed, Apr 19, 2017 at 04:07:25PM +0100, Mark Rutland wrote: > > On Tue, Apr 18, 2017 at 06:21:07PM +0100, Lorenzo Pieralisi wrote: > > > On Sat, Apr 15, 2017 at 02:40:12AM +0800, fu@linaro.org wrote: > > > > If yes, why can't

Re: [PATCH v24 09/11] acpi/arm64: Add memory-mapped timer support in GTDT driver

2017-04-19 Thread Lorenzo Pieralisi
On Wed, Apr 19, 2017 at 04:45:54PM +0100, Mark Rutland wrote: > On Wed, Apr 19, 2017 at 04:07:25PM +0100, Mark Rutland wrote: > > On Tue, Apr 18, 2017 at 06:21:07PM +0100, Lorenzo Pieralisi wrote: > > > On Sat, Apr 15, 2017 at 02:40:12AM +0800, fu@linaro.org wrote: > > > > If yes, why can't

Re: [PATCH v24 09/11] acpi/arm64: Add memory-mapped timer support in GTDT driver

2017-04-19 Thread Mark Rutland
On Wed, Apr 19, 2017 at 04:07:25PM +0100, Mark Rutland wrote: > On Tue, Apr 18, 2017 at 06:21:07PM +0100, Lorenzo Pieralisi wrote: > > On Sat, Apr 15, 2017 at 02:40:12AM +0800, fu@linaro.org wrote: > > If yes, why can't it simply be written like this ? > > > > for (; i >= 0; i--,

Re: [PATCH v24 09/11] acpi/arm64: Add memory-mapped timer support in GTDT driver

2017-04-19 Thread Mark Rutland
On Wed, Apr 19, 2017 at 04:07:25PM +0100, Mark Rutland wrote: > On Tue, Apr 18, 2017 at 06:21:07PM +0100, Lorenzo Pieralisi wrote: > > On Sat, Apr 15, 2017 at 02:40:12AM +0800, fu@linaro.org wrote: > > If yes, why can't it simply be written like this ? > > > > for (; i >= 0; i--,

Re: [PATCH v24 09/11] acpi/arm64: Add memory-mapped timer support in GTDT driver

2017-04-19 Thread Mark Rutland
On Tue, Apr 18, 2017 at 06:21:07PM +0100, Lorenzo Pieralisi wrote: > On Sat, Apr 15, 2017 at 02:40:12AM +0800, fu@linaro.org wrote: > > +error: > > + for (i = 0; i < ARCH_TIMER_MEM_MAX_FRAMES; i++) { > > + frame = _mem->frame[i]; > > + if (frame->phys_irq > 0) > > +

Re: [PATCH v24 09/11] acpi/arm64: Add memory-mapped timer support in GTDT driver

2017-04-19 Thread Mark Rutland
On Tue, Apr 18, 2017 at 06:21:07PM +0100, Lorenzo Pieralisi wrote: > On Sat, Apr 15, 2017 at 02:40:12AM +0800, fu@linaro.org wrote: > > +error: > > + for (i = 0; i < ARCH_TIMER_MEM_MAX_FRAMES; i++) { > > + frame = _mem->frame[i]; > > + if (frame->phys_irq > 0) > > +

Re: [PATCH v24 09/11] acpi/arm64: Add memory-mapped timer support in GTDT driver

2017-04-18 Thread Lorenzo Pieralisi
On Sat, Apr 15, 2017 at 02:40:12AM +0800, fu@linaro.org wrote: > From: Fu Wei > > On platforms booting with ACPI, architected memory-mapped timers' > configuration data is provided by firmware through the ACPI GTDT > static table. > > The clocksource architected timer

Re: [PATCH v24 09/11] acpi/arm64: Add memory-mapped timer support in GTDT driver

2017-04-18 Thread Lorenzo Pieralisi
On Sat, Apr 15, 2017 at 02:40:12AM +0800, fu@linaro.org wrote: > From: Fu Wei > > On platforms booting with ACPI, architected memory-mapped timers' > configuration data is provided by firmware through the ACPI GTDT > static table. > > The clocksource architected timer kernel driver requires

[PATCH v24 09/11] acpi/arm64: Add memory-mapped timer support in GTDT driver

2017-04-14 Thread fu . wei
From: Fu Wei On platforms booting with ACPI, architected memory-mapped timers' configuration data is provided by firmware through the ACPI GTDT static table. The clocksource architected timer kernel driver requires a firmware interface to collect timer configuration and

[PATCH v24 09/11] acpi/arm64: Add memory-mapped timer support in GTDT driver

2017-04-14 Thread fu . wei
From: Fu Wei On platforms booting with ACPI, architected memory-mapped timers' configuration data is provided by firmware through the ACPI GTDT static table. The clocksource architected timer kernel driver requires a firmware interface to collect timer configuration and configure its driver.