- Subject: Re: [PATCH V2 1/4] cpufreq: add arm soc generic cpufreq driver
- From: Bryan Huntsman <bryanh@xxxxxxxxxxxxxx>
- Date: Fri, 16 Dec 2011 11:59:02 -0800
- Cc: Richard Zhao <richard.zhao@xxxxxxxxxx>, linux@xxxxxxxxxxxxxxxx, patches@xxxxxxxxxx, devicetree-discuss@xxxxxxxxxxxxxxxx, cpufreq@xxxxxxxxxxxxxxx, eric.miao@xxxxxxxxxx, kernel@xxxxxxxxxxxxxx, davej@xxxxxxxxxx, linaro-dev@xxxxxxxxxxxxxxxx, linux-arm-kernel@xxxxxxxxxxxxxxxxxxx, linux-arm-msm@xxxxxxxxxxxxxxx
- In-reply-to: <20111216105229.GB3230@totoro>
- References: <1324031462-24961-1-git-send-email-richard.zhao@linaro.org> <1324031462-24961-2-git-send-email-richard.zhao@linaro.org> <20111216105229.GB3230@totoro>
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20111124 Thunderbird/9.0
On 12/16/2011 02:52 AM, Jamie Iles wrote:
>
>> +static DEFINE_PER_CPU(unsigned long, l_p_j_ref);
>> +static unsigned long l_p_j_ref_freq;
>> +
>> +static struct clk *cpu_clk;
>
> This assumes that all CPU's share the same clk and run at the same rate.
> Is that a fair/safe assumption? I honestly don't know the answer to
> this so it's just a question!!!
On MSM, cpus independently scale both frequency and voltage. Our clock
driver isn't upstream yet. David Brown has a preliminary version here:
https://www.codeaurora.org/gitweb/quic/kernel/?p=davidb/linux-msm.git;a=shortlog;h=refs/heads/msm-clock-rfc
Once we get our driver upstream, MSM will be an exception and not select
ARM_GENERIC_CPUFREQ. We'll probably have a separate msm-cpufreq.c
driver under drivers/cpufreq/.
- Bryan
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
--
To unsubscribe from this list: send the line "unsubscribe cpufreq" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Linux USB Devel]
[Video for Linux]
[Linux Audio Users]
[Photo]
[Yosemite News]
[Yosemite Photos]
[Free Online Dating]
[Linux Kernel]
[Linux SCSI]
[XFree86]