cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Richard Zhao <richard.zhao@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org, cpufreq@vger.kernel.org,
	devicetree-discuss@lists.ozlabs.org, linux@arm.linux.org.uk,
	mark.langsdorf@calxeda.com, patches@linaro.org,
	eric.miao@linaro.org, kernel@pengutronix.de, davej@redhat.com,
	linaro-dev@lists.linaro.org
Subject: Re: [PATCH V2 1/4] cpufreq: add arm soc generic cpufreq driver
Date: Wed, 18 Jan 2012 11:39:50 +0000	[thread overview]
Message-ID: <20120118113949.GA22977@sirena.org.uk> (raw)
In-Reply-To: <1324031462-24961-2-git-send-email-richard.zhao@linaro.org>

On Fri, Dec 16, 2011 at 06:30:59PM +0800, Richard Zhao wrote:

> +	if (higher && cpu_reg)
> +		regulator_set_voltage(cpu_reg,
> +				cpu_volts[index], cpu_volts[index]);
> +
> +	ret = clk_set_rate(cpu_clk, freq);
> +	if (ret != 0) {
> +		printk(KERN_DEBUG "cannot set CPU clock rate\n");
> +		return ret;
> +	}
> +
> +	if (!higher && cpu_reg)
> +		regulator_set_voltage(cpu_reg,
> +				cpu_volts[index], cpu_volts[index]);

This appears to reintroduce the setting of an exact voltage which I'm
sure was fixed in previous versions of the patch.

> +static struct cpufreq_driver arm_cpufreq_driver = {
> +	.flags = CPUFREQ_STICKY,
> +	.verify = arm_verify_speed,
> +	.target = arm_set_target,
> +	.get = arm_get_speed,
> +	.init = arm_cpufreq_init,
> +	.exit = arm_cpufreq_exit,
> +	.name = "arm",
> +};

This code doesn't actually look terribly ARM specific...

> +	printk(KERN_INFO "ARM SoC generic CPU frequency driver\n");

Do we need this?

  parent reply	other threads:[~2012-01-18 11:39 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
     [not found]         ` <20111219010357.GW28768-iWYTGMXpHj9ITqJhDdzsOjpauB2SiJktrE5yTffgRl4@public.gmane.org>
2011-12-19 17:42           ` Stephen Boyd
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 [this message]
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
     [not found]   ` <1324031462-24961-4-git-send-email-richard.zhao-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
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=20120118113949.GA22977@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=davej@redhat.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=eric.miao@linaro.org \
    --cc=kernel@pengutronix.de \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.langsdorf@calxeda.com \
    --cc=patches@linaro.org \
    --cc=richard.zhao@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox