From: Nathan_Lynch@mentor.com (Nathan Lynch)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] arm_arch_timer: VDSO preparation, code consolidation
Date: Wed, 3 Sep 2014 09:09:06 -0500 [thread overview]
Message-ID: <54072102.1020605@mentor.com> (raw)
In-Reply-To: <1408743797-7648-1-git-send-email-nathan_lynch@mentor.com>
On 08/22/2014 04:43 PM, Nathan Lynch wrote:
> This series contains the necessary changes to allow architected timer
> access from user-space on 32-bit ARM. This allows the VDSO to support
> high resolution timestamps for clock_gettime and gettimeofday. This
> also merges substantially similar code from arm and arm64 into the
> core arm_arch_timer driver.
>
> These patches have been carried as part of the ARM VDSO patch set over
> the last several months, but I am splitting them out here as I assume
> they should go through the clocksource maintainer.
>
> Nathan Lynch (4):
> clocksource: arm_arch_timer: change clocksource name if CP15
> unavailable
> clocksource: arm_arch_timer: enable counter access for 32-bit ARM
> ARM: arch_timer: remove unused functions
> arm64: arch_timer: remove unused functions
>
> arch/arm/include/asm/arch_timer.h | 25 -------------------
> arch/arm64/include/asm/arch_timer.h | 31 -----------------------
> drivers/clocksource/arm_arch_timer.c | 48 +++++++++++++++++++++++++++++++++---
> 3 files changed, 44 insertions(+), 60 deletions(-)
Daniel, do you plan to take this series for 3.18?
prev parent reply other threads:[~2014-09-03 14:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 21:43 [PATCH 0/4] arm_arch_timer: VDSO preparation, code consolidation Nathan Lynch
2014-08-22 21:43 ` [PATCH 1/4] clocksource: arm_arch_timer: change clocksource name if CP15 unavailable Nathan Lynch
2014-08-22 21:43 ` [PATCH 2/4] clocksource: arm_arch_timer: enable counter access for 32-bit ARM Nathan Lynch
2014-08-22 21:43 ` [PATCH 3/4] ARM: arch_timer: remove unused functions Nathan Lynch
2014-08-22 21:43 ` [PATCH 4/4] arm64: " Nathan Lynch
2014-08-26 16:24 ` Catalin Marinas
2014-09-03 14:09 ` Nathan Lynch [this message]
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=54072102.1020605@mentor.com \
--to=nathan_lynch@mentor.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.