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 V3 4/7] cpufreq: add generic cpufreq driver
Date: Wed, 21 Dec 2011 22:19:11 +0800	[thread overview]
Message-ID: <20111221141907.GA1777@richard-laptop> (raw)
In-Reply-To: <CAPXgP10CGxfEJ4jK2MkKt0-nAWgiawDERyA1N4wHvMCJfE3oDg@mail.gmail.com>

On Wed, Dec 21, 2011 at 01:49:07PM +0100, Kay Sievers wrote:
> On Wed, Dec 21, 2011 at 13:12, Mark Brown
> <broonie@opensource.wolfsonmicro.com> wrote:
> > On Wed, Dec 21, 2011 at 12:44:57PM +0100, Kay Sievers wrote:
> >
> >> We will convert all classes to buses over time time, and have a single
> >> type of device and a single type of subsystem.
> >
> > Are there any conversions that have been done already that I can look at
> > for reference?
> 
> The first step is the conversion from 'sys_device' to 'device', which is here:
>   http://git.kernel.org/?p=linux/kernel/git/kay/patches.git;a=tree
> 
> That should hit the tree soon, if all works according to plan. All
> sys_devices and sysdev classes will be gone for forever.
Even cpu node is device, I still need to find a way to get it.  I think it's
better have another patch to fix the regulator dt binding in cpu node. I'll
not include it in this patch series.

Richard
> 
> The 'class' to 'bus' work is simpler, because the logic in both of
> them is very similar and both use the same 'struct device' already.
> 
> We'll need to add some convenience APIs to bus, and add code to make
> sure the converted stuff has compat symlinks in /sys/class when
> needed. Then we can convert-over one 'struct class' to 'struct
> bus_type' after the other until 'struct class' can be deleted.
> 
> This work has not yet started, because we are busy with the sys_device
> stuff at the moment.
> 
> No new stuff should use 'struct class' or 'struct sys_device', they
> should all start right away with 'struct bus_type'.
> 
> Kay

  reply	other threads:[~2011-12-21 14:19 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-19  3:21 [PATCH V3 0/7] add a generic cpufreq driver Richard Zhao
2011-12-19  3:21 ` [PATCH V3 1/7] ARM: add cpufreq transiton notifier to adjust loops_per_jiffy for smp Richard Zhao
2011-12-21 14:21   ` Richard Zhao
2011-12-19  3:21 ` [PATCH V3 2/7] arm/imx: cpufreq: remove loops_per_jiffy recalculate " Richard Zhao
2011-12-19  3:21 ` [PATCH V3 3/7] cpufreq: OMAP: " Richard Zhao
2011-12-19  3:21 ` [PATCH V3 4/7] cpufreq: add generic cpufreq driver Richard Zhao
2011-12-19 10:05   ` Jamie Iles
2011-12-19 14:19     ` Richard Zhao
2011-12-19 14:39       ` Jamie Iles
2011-12-19 15:00         ` Rob Herring
2011-12-20  1:59           ` Richard Zhao
2011-12-20 15:13             ` Rob Herring
2011-12-20 15:21             ` Arnd Bergmann
2011-12-20 14:59   ` Mark Brown
2011-12-20 23:27     ` Richard Zhao
2011-12-20 23:48       ` Mark Brown
2011-12-21  1:20         ` Richard Zhao
2011-12-21  1:32           ` Mark Brown
2011-12-21  2:24             ` Richard Zhao
2011-12-21  2:33               ` Mark Brown
2011-12-21  2:51                 ` Richard Zhao
2011-12-21  9:27           ` Richard Zhao
2011-12-21  9:43             ` Arnd Bergmann
2011-12-21 11:44               ` Kay Sievers
2011-12-21 12:12                 ` Mark Brown
2011-12-21 12:49                   ` Kay Sievers
2011-12-21 14:19                     ` Richard Zhao [this message]
2011-12-22  0:50                       ` Mark Brown
2011-12-21 12:11               ` Mark Brown
2011-12-19  3:21 ` [PATCH V3 5/7] dts/imx6q: add cpufreq property Richard Zhao
2011-12-19  3:21 ` [PATCH V3 6/7] arm/imx6q: register arm_clk as cpu to clkdev Richard Zhao
2011-12-19  3:21 ` [PATCH V3 7/7] 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=20111221141907.GA1777@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