From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 1/4] cpufreq: add arm soc generic cpufreq driver
Date: Mon, 19 Dec 2011 09:42:29 -0800 [thread overview]
Message-ID: <4EEF7785.8040907@codeaurora.org> (raw)
In-Reply-To: <20111219010357.GW28768@b20223-02.ap.freescale.net>
On 12/18/11 17:03, Richard Zhao wrote:
>
> Do you have to patch to implement per-cpu udelay? In current code, udelay uses
> global loops_per_jiffy.
>
>
We've been carrying forward the timer based udelay patches. They're in
the patch tracker as 6873/1, 6874/1, and 6875/1.
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2011-12-19 17:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 10:30 [PATCH V2 0/4] add arm soc generic cpufreq driver Richard Zhao
2011-12-16 10:30 ` [PATCH V2 1/4] cpufreq: " Richard Zhao
2011-12-16 10:52 ` Jamie Iles
2011-12-16 19:59 ` Bryan Huntsman
2011-12-17 8:39 ` Richard Zhao
2011-12-19 1:03 ` Richard Zhao
2011-12-19 17:42 ` Stephen Boyd [this message]
2011-12-17 8:29 ` Richard Zhao
2011-12-16 11:26 ` Heiko Stübner
2011-12-17 7:57 ` Richard Zhao
2011-12-16 14:32 ` Rob Herring
2011-12-17 8:00 ` Richard Zhao
2011-12-17 9:29 ` Arnd Bergmann
2011-12-18 12:34 ` Richard Zhao
2011-12-20 14:41 ` Mark Brown
2012-01-18 11:39 ` Mark Brown
2012-01-18 11:42 ` Mark Brown
2012-01-18 20:51 ` Grant Likely
2011-12-16 10:31 ` [PATCH V2 2/4] dts/imx6q: add cpufreq property Richard Zhao
2011-12-16 10:31 ` [PATCH V2 3/4] arm/imx6q: register arm_clk as cpu to clkdev Richard Zhao
2011-12-16 16:35 ` Mark Langsdorf
2011-12-17 7:56 ` Richard Zhao
2011-12-16 10:31 ` [PATCH V2 4/4] arm/imx6q: select ARCH_HAS_CPUFREQ Richard Zhao
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=4EEF7785.8040907@codeaurora.org \
--to=sboyd@codeaurora.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).