Hi Lorenzo,
On 30 March 2017 at 00:47, Lorenzo Pieralisi wrote:
> On Wed, Mar 22, 2017 at 12:31:20AM +0800, fu@linaro.org wrote:
>> From: Fu Wei
>>
>> On platforms booting with ACPI, architected memory-mapped timers'
>> configuration data is
Hi Lorenzo,
On 30 March 2017 at 00:47, Lorenzo Pieralisi wrote:
> On Wed, Mar 22, 2017 at 12:31:20AM +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
>>
On Wed, Mar 22, 2017 at 12:31:20AM +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
On Wed, Mar 22, 2017 at 12:31:20AM +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
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
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.
6 matches
Mail list logo