public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: richard.zhao@linaro.org (Richard Zhao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 3/4] arm/imx6q: register arm_clk as cpu to clkdev
Date: Sat, 17 Dec 2011 15:56:15 +0800	[thread overview]
Message-ID: <20111217075612.GA2010@richard-laptop> (raw)
In-Reply-To: <21672683C5A3814BB4DB938EBE482DE40A1AE8EF74@IAD2MBX09.mex02.mlsrvr.com>

On Fri, Dec 16, 2011 at 11:35:39AM -0500, Mark Langsdorf wrote:
> Is there a portable/generic approach for other drivers that may
> want to use arm-cpufreq.c? arm_clk is not normally defined for
> my SoC and I don't see an easy way to pull it in.
Could you tell me the details? Is your board arch/arm/mach-highbank/ Rob
maintained?
clk API is the most generic way for arm as far as I find out.

Thanks
Richard
> 
> --Mark Langsdorf
> Calxeda, Inc.
> 
> ________________________________________
> From: Richard Zhao [richard.zhao at linaro.org]
> Sent: Friday, December 16, 2011 4:31 AM
> To: linux-arm-kernel at lists.infradead.org; cpufreq at vger.kernel.org; devicetree-discuss at lists.ozlabs.org
> Cc: linux at arm.linux.org.uk; davej at redhat.com; kernel at pengutronix.de; shawn.guo at linaro.org; eric.miao at linaro.org; Mark Langsdorf; linaro-dev at lists.linaro.org; patches at linaro.org; Richard Zhao
> Subject: [PATCH V2 3/4] arm/imx6q: register arm_clk as cpu to clkdev
> 
> cpufreq needs cpu clock to change frequency.
> 
> Signed-off-by: Richard Zhao <richard.zhao@linaro.org>
> ---
>  arch/arm/mach-imx/clock-imx6q.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/arch/arm/mach-imx/clock-imx6q.c b/arch/arm/mach-imx/clock-imx6q.c
> index 039a7ab..72acbc2 100644
> --- a/arch/arm/mach-imx/clock-imx6q.c
> +++ b/arch/arm/mach-imx/clock-imx6q.c
> @@ -1911,6 +1911,7 @@ static struct clk_lookup lookups[] = {
>         _REGISTER_CLOCK(NULL, "gpmi_io_clk", gpmi_io_clk),
>         _REGISTER_CLOCK(NULL, "usboh3_clk", usboh3_clk),
>         _REGISTER_CLOCK(NULL, "sata_clk", sata_clk),
> +       _REGISTER_CLOCK(NULL, "cpu", arm_clk),
>  };
> 
>  int imx6q_set_lpm(enum mxc_cpu_pwr_mode mode)
> --
> 1.7.5.4

  reply	other threads:[~2011-12-17  7:56 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
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 [this message]
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=20111217075612.GA2010@richard-laptop \
    --to=richard.zhao@linaro.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