[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140922153919.GQ25809@arm.com>
Date: Mon, 22 Sep 2014 16:39:19 +0100
From: Will Deacon <will.deacon@....com>
To: Nathan Lynch <nathan_lynch@...tor.com>
Cc: Daniel Lezcano <daniel.lezcano@...aro.org>,
Catalin Marinas <Catalin.Marinas@....com>,
Christopher Covington <cov@...eaurora.org>,
Doug Anderson <dianders@...omium.org>,
Lorenzo Pieralisi <Lorenzo.Pieralisi@....com>,
Marc Zyngier <Marc.Zyngier@....com>,
Mark Rutland <Mark.Rutland@....com>,
Russell King <linux@....linux.org.uk>,
Sonny Rao <sonnyrao@...omium.org>,
Stephen Boyd <sboyd@...eaurora.org>,
Thomas Gleixner <tglx@...utronix.de>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/3] arm_arch_timer: VDSO preparation, code
consolidation
On Thu, Sep 18, 2014 at 03:59:32PM +0100, 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.
>
> The functional changes are:
> - When available, CNTVCT is made readable by user space on arm, as it
> is on arm64.
> - The clocksource name becomes "arch_mem_counter" if CP15 access to
> the counter is not available.
>
> These changes 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 maintainers.
For the series:
Acked-by: Will Deacon <will.deacon@....com>
I'm not sure which tree the arch-timer stuff usually goes through, but
the arm/arm64 bits look fine so I'm happy for them to merged together.
Will
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists