[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <51B8C336.4050700@codeaurora.org>
Date: Wed, 12 Jun 2013 14:51:34 -0400
From: Christopher Covington <cov@...eaurora.org>
To: Stephen Boyd <sboyd@...eaurora.org>
CC: John Stultz <john.stultz@...aro.org>, linux-kernel@...r.kernel.org,
linux-arm-msm@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
Russell King <linux@....linux.org.uk>, arm@...nel.org,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCHv3 3/3] arm64: Move to generic sched_clock infrastructure
On 06/05/2013 07:54 PM, Stephen Boyd wrote:
> Use the generic sched_clock infrastructure instead of rolling our
> own. This has the added benefit of fixing suspend/resume as
> outlined in 6a4dae5 (ARM: 7565/1: sched: stop sched_clock()
> during suspend, 2012-10-23) and correcting the timestamps when
> the hardware returns a value instead of 0 upon the first read.
Builds and runs for me on software models.
Tested-by: Christopher Covington <cov@...eaurora.org>
Cheers,
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
--
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