All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Zhao <richard.zhao@linaro.org>
To: Bryan Huntsman <bryanh@codeaurora.org>
Cc: Jamie Iles <jamie@jamieiles.com>,
	linux@arm.linux.org.uk, patches@linaro.org,
	devicetree-discuss@lists.ozlabs.org, cpufreq@vger.kernel.org,
	eric.miao@linaro.org, kernel@pengutronix.de, davej@redhat.com,
	linaro-dev@lists.linaro.org,
	linux-arm-kernel@lists.infradead.org,
	linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH V2 1/4] cpufreq: add arm soc generic cpufreq driver
Date: Sat, 17 Dec 2011 16:39:54 +0800	[thread overview]
Message-ID: <20111217083952.GE2010@richard-laptop> (raw)
In-Reply-To: <4EEBA306.3060309@codeaurora.org>

On Fri, Dec 16, 2011 at 11:59:02AM -0800, Bryan Huntsman wrote:
> 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:
If
 - cpu_clk are per_cpu, and get from cpu0 clk, cpu1 clk, etc.
   The same to regulators.
 - set CPUFREQ_SHARED_TYPE_NONE
 - don't set affect cpus.

Does that help you?

Thanks
Richard
> 
> 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.

WARNING: multiple messages have this Message-ID (diff)
From: richard.zhao@linaro.org (Richard Zhao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 1/4] cpufreq: add arm soc generic cpufreq driver
Date: Sat, 17 Dec 2011 16:39:54 +0800	[thread overview]
Message-ID: <20111217083952.GE2010@richard-laptop> (raw)
In-Reply-To: <4EEBA306.3060309@codeaurora.org>

On Fri, Dec 16, 2011 at 11:59:02AM -0800, Bryan Huntsman wrote:
> 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:
If
 - cpu_clk are per_cpu, and get from cpu0 clk, cpu1 clk, etc.
   The same to regulators.
 - set CPUFREQ_SHARED_TYPE_NONE
 - don't set affect cpus.

Does that help you?

Thanks
Richard
> 
> 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.

  reply	other threads:[~2011-12-17  8:39 UTC|newest]

Thread overview: 46+ 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 ` Richard Zhao
2011-12-16 10:30 ` [PATCH V2 1/4] cpufreq: " Richard Zhao
2011-12-16 10:30   ` Richard Zhao
2011-12-16 10:52   ` Jamie Iles
2011-12-16 10:52     ` Jamie Iles
2011-12-16 19:59     ` Bryan Huntsman
2011-12-16 19:59       ` Bryan Huntsman
2011-12-17  8:39       ` Richard Zhao [this message]
2011-12-17  8:39         ` Richard Zhao
2011-12-19  1:03       ` Richard Zhao
2011-12-19  1:03         ` Richard Zhao
     [not found]         ` <20111219010357.GW28768-iWYTGMXpHj9ITqJhDdzsOjpauB2SiJktrE5yTffgRl4@public.gmane.org>
2011-12-19 17:42           ` Stephen Boyd
2011-12-19 17:42             ` Stephen Boyd
2011-12-17  8:29     ` Richard Zhao
2011-12-17  8:29       ` Richard Zhao
2011-12-16 11:26   ` Heiko Stübner
2011-12-16 11:26     ` Heiko Stübner
2011-12-17  7:57     ` Richard Zhao
2011-12-17  7:57       ` Richard Zhao
2011-12-16 14:32   ` Rob Herring
2011-12-16 14:32     ` Rob Herring
2011-12-17  8:00     ` Richard Zhao
2011-12-17  8:00       ` Richard Zhao
2011-12-17  9:29       ` Arnd Bergmann
2011-12-17  9:29         ` Arnd Bergmann
2011-12-18 12:34         ` Richard Zhao
2011-12-18 12:34           ` Richard Zhao
2011-12-20 14:41   ` Mark Brown
2011-12-20 14:41     ` Mark Brown
2012-01-18 11:39   ` Mark Brown
2012-01-18 11:39     ` Mark Brown
2012-01-18 11:42     ` Mark Brown
2012-01-18 11:42       ` Mark Brown
2012-01-18 20:51       ` Grant Likely
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   ` 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 10:31   ` Richard Zhao
     [not found]   ` <1324031462-24961-4-git-send-email-richard.zhao-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2011-12-16 16:35     ` Mark Langsdorf
2011-12-16 16:35       ` Mark Langsdorf
2011-12-17  7:56       ` Richard Zhao
2011-12-17  7:56         ` Richard Zhao
2011-12-16 10:31 ` [PATCH V2 4/4] arm/imx6q: select ARCH_HAS_CPUFREQ Richard Zhao
2011-12-16 10:31   ` 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=20111217083952.GE2010@richard-laptop \
    --to=richard.zhao@linaro.org \
    --cc=bryanh@codeaurora.org \
    --cc=cpufreq@vger.kernel.org \
    --cc=davej@redhat.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=eric.miao@linaro.org \
    --cc=jamie@jamieiles.com \
    --cc=kernel@pengutronix.de \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=patches@linaro.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.