linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] ACPI, clocksource: add GTDT and ARM memory-mapped timer support
Date: Wed, 16 Dec 2015 17:32:01 +0100	[thread overview]
Message-ID: <56719201.2020801@linaro.org> (raw)
In-Reply-To: <1449034984-12075-1-git-send-email-fu.wei@linaro.org>


Marc,

can you have a look ?

Thanks

   -- Daniel

On 12/02/2015 06:43 AM, fu.wei at linaro.org wrote:
> From: Fu Wei <fu.wei@linaro.org>
>
> This patchset:
>      (1)Introduce ACPI GTDT parser: drivers/acpi/gtdt.c
>      Parse all kinds of timer in GTDT table of ACPI:arch timer,
>      memory-mapped timer and SBSA Generic Watchdog timer.
>      This driver can help to simplify all the relevant timer drivers,
>      and separate all the ACPI GTDT knowledge from them.
>
>      (2)Simplify ACPI code for arch timer in arm_arch_timer.c
>
>      (3)Add memory-mapped timer support in arm_arch_timer.c
>
> The SBSA Generic Watchdog info parsing support have been tested with
> a upstreaming SBSA Generic Watchdog driver:
> https://lkml.org/lkml/2015/10/27/466
> on the following platforms:
>      (1)ARM Foundation v8 model
>      (2)AMD Seattle platform
>
> ARM memory-mapped timer support of this patchset has been tested
> on the following platforms:
>      (1)ARM Foundation v8 model
>
> Changelog:
> v2: Rebase to latest kernel version(4.4-rc3).
>      Fix the bug about the config problem,
>      use CONFIG_ACPI_GTDT instead of CONFIG_ACPI in arm_arch_timer.c
>
> v1: The first upstreaming version: https://lkml.org/lkml/2015/10/28/553
>
> Fu Wei (3):
>    ACPI: add GTDT table parse driver into ACPI driver
>    clocksource: simplify ACPI code in arm_arch_timer.c
>    clocksource: add memory-mapped timer support in arm_arch_timer.c
>
>   drivers/acpi/Kconfig                 |   9 +
>   drivers/acpi/Makefile                |   1 +
>   drivers/acpi/gtdt.c                  | 367 +++++++++++++++++++++++++++++++++++
>   drivers/clocksource/arm_arch_timer.c | 178 +++++++++++++----
>   include/clocksource/arm_arch_timer.h |  19 ++
>   include/linux/acpi.h                 |  17 ++
>   6 files changed, 555 insertions(+), 36 deletions(-)
>   create mode 100644 drivers/acpi/gtdt.c
>


-- 
  <http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

  parent reply	other threads:[~2015-12-16 16:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02  5:43 [PATCH v2 0/3] ACPI, clocksource: add GTDT and ARM memory-mapped timer support fu.wei at linaro.org
2015-12-02  5:43 ` [PATCH v2 1/3] ACPI: add GTDT table parse driver into ACPI driver fu.wei at linaro.org
2015-12-02  5:43 ` [PATCH v2 2/3] clocksource: simplify ACPI code in arm_arch_timer.c fu.wei at linaro.org
2015-12-02  5:43 ` [PATCH v2 3/3] clocksource: add memory-mapped timer support " fu.wei at linaro.org
2015-12-16 16:32 ` Daniel Lezcano [this message]
2015-12-16 16:52   ` [PATCH v2 0/3] ACPI, clocksource: add GTDT and ARM memory-mapped timer support Marc Zyngier
2015-12-16 23:18     ` Fu Wei

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56719201.2020801@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).