linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: chf.fritz@googlemail.com (Christoph Fritz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mx35: add cpufreq support
Date: Sun, 27 May 2012 20:20:32 +0200	[thread overview]
Message-ID: <1338142832.8582.4.camel@mars> (raw)
In-Reply-To: <20120517224205.GA7021@mars>

On Fri, 2012-05-18 at 00:42 +0200, Christoph Fritz wrote:
> On Thu, May 17, 2012 at 08:40:58PM +0200, Christoph Fritz wrote:
> > On Thu, 2012-05-17 at 20:20 +0200, Sascha Hauer wrote:
> > > On Thu, May 17, 2012 at 07:49:20PM +0200, Christoph Fritz wrote:
> > 
> > > > Is there already a version I can rebase the patch?
> > > > 
> > > > On your repo at git://git.pengutronix.de/git/imx/linux-2.6.git I can't
> > > > find the new clock framework or even a work-in-progress version.
> > > 
> > > They are in linux-next now.
> 
> There changed a lot of stuff: Where should I register the function to
> set/get the cpu frequency?
> 
> To get an idea of how it should be done, I looked at imx51: Is there
> cpufreq-support still implemented/working?  I can see the
> arch/arm/mach-imx/cpu_op-mx51.c but not its correlating
> clk_cpu_set_rate function in arch/arm/mach-imx/clk-imx51-imx53.c.

*ping*


 Thanks,
  -- Christoph
 

  reply	other threads:[~2012-05-27 18:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07 14:14 [PATCH] ARM: mx35: add cpufreq support Christoph Fritz
2012-05-09  7:22 ` Sascha Hauer
2012-05-09  7:56   ` Christoph Fritz
2012-05-09  8:13     ` Sascha Hauer
2012-05-17 17:49       ` Christoph Fritz
2012-05-17 18:20         ` Sascha Hauer
2012-05-17 18:40           ` Christoph Fritz
2012-05-17 22:42             ` Christoph Fritz
2012-05-27 18:20               ` Christoph Fritz [this message]
2012-05-29 14:34               ` Sascha Hauer
2012-05-18  5:05             ` Marc Reilly

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=1338142832.8582.4.camel@mars \
    --to=chf.fritz@googlemail.com \
    --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).