Re: [PATCH v14 6/9] acpi/arm64: Add memory-mapped timer support in GTDT driver

2016-10-21 Thread Mark Rutland
On Thu, Sep 29, 2016 at 02:17:14AM +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 v14 6/9] acpi/arm64: Add memory-mapped timer support in GTDT driver

2016-10-21 Thread Mark Rutland
On Thu, Sep 29, 2016 at 02:17:14AM +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 v14 6/9] acpi/arm64: Add memory-mapped timer support in GTDT driver

2016-09-28 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 v14 6/9] acpi/arm64: Add memory-mapped timer support in GTDT driver

2016-09-28 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.