From: Simon Horman <horms@verge.net.au>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-sh@vger.kernel.org, Magnus Damm <magnus.damm@gmail.com>,
linux-arm-kernel@lists.infradead.org,
"Rafael J. Wysocki" <rjw@sisk.pl>,
cpufreq@vger.kernel.org,
Guennadi Liakhovetski <g.liakhovetski+renesas@gmail.com>
Subject: Re: [PATCH v5 3/3] ARM: shmobile: sh73a0: add CPUFreq support
Date: Thu, 18 Apr 2013 22:52:12 +0900 [thread overview]
Message-ID: <20130418135212.GL20929@verge.net.au> (raw)
In-Reply-To: <1365156038-12467-4-git-send-email-g.liakhovetski@gmx.de>
On Fri, Apr 05, 2013 at 12:00:38PM +0200, Guennadi Liakhovetski wrote:
> This patch enables the use of the generic cpufreq-cpu0 driver on sh73a0.
> Providing a regulator, a list of OPPs in DT, combined with a virtual
> cpufreq-cpu0 platform device and a clock, attached to it is everything,
> the cpufreq-cpu0 driver needs. The first sh73a0 platform, implementing
> such CPUFreq support is kzm9g-reference.
>
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski+renesas@gmail.com>
> ---
>
> v5: remove sh73a0-kzm9g-reference.dts hunk, it's now merged into patch 2/3
>
> arch/arm/mach-shmobile/Kconfig | 2 ++
> arch/arm/mach-shmobile/setup-sh73a0.c | 5 +++++
> 2 files changed, 7 insertions(+), 0 deletions(-)
Thanks, queued-up for v3.11 in the soc-sh73a0 branch.
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 3/3] ARM: shmobile: sh73a0: add CPUFreq support
Date: Thu, 18 Apr 2013 13:52:12 +0000 [thread overview]
Message-ID: <20130418135212.GL20929@verge.net.au> (raw)
In-Reply-To: <1365156038-12467-4-git-send-email-g.liakhovetski@gmx.de>
On Fri, Apr 05, 2013 at 12:00:38PM +0200, Guennadi Liakhovetski wrote:
> This patch enables the use of the generic cpufreq-cpu0 driver on sh73a0.
> Providing a regulator, a list of OPPs in DT, combined with a virtual
> cpufreq-cpu0 platform device and a clock, attached to it is everything,
> the cpufreq-cpu0 driver needs. The first sh73a0 platform, implementing
> such CPUFreq support is kzm9g-reference.
>
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski+renesas@gmail.com>
> ---
>
> v5: remove sh73a0-kzm9g-reference.dts hunk, it's now merged into patch 2/3
>
> arch/arm/mach-shmobile/Kconfig | 2 ++
> arch/arm/mach-shmobile/setup-sh73a0.c | 5 +++++
> 2 files changed, 7 insertions(+), 0 deletions(-)
Thanks, queued-up for v3.11 in the soc-sh73a0 branch.
WARNING: multiple messages have this Message-ID (diff)
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 3/3] ARM: shmobile: sh73a0: add CPUFreq support
Date: Thu, 18 Apr 2013 22:52:12 +0900 [thread overview]
Message-ID: <20130418135212.GL20929@verge.net.au> (raw)
In-Reply-To: <1365156038-12467-4-git-send-email-g.liakhovetski@gmx.de>
On Fri, Apr 05, 2013 at 12:00:38PM +0200, Guennadi Liakhovetski wrote:
> This patch enables the use of the generic cpufreq-cpu0 driver on sh73a0.
> Providing a regulator, a list of OPPs in DT, combined with a virtual
> cpufreq-cpu0 platform device and a clock, attached to it is everything,
> the cpufreq-cpu0 driver needs. The first sh73a0 platform, implementing
> such CPUFreq support is kzm9g-reference.
>
> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski+renesas@gmail.com>
> ---
>
> v5: remove sh73a0-kzm9g-reference.dts hunk, it's now merged into patch 2/3
>
> arch/arm/mach-shmobile/Kconfig | 2 ++
> arch/arm/mach-shmobile/setup-sh73a0.c | 5 +++++
> 2 files changed, 7 insertions(+), 0 deletions(-)
Thanks, queued-up for v3.11 in the soc-sh73a0 branch.
next prev parent reply other threads:[~2013-04-18 13:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 10:00 [PATCH v5 0/3] CPUFreq for sh73a0 / kzm9g, using cpufreq-cpu0 Guennadi Liakhovetski
2013-04-05 10:00 ` Guennadi Liakhovetski
2013-04-05 10:00 ` Guennadi Liakhovetski
2013-04-05 10:00 ` [PATCH v5 1/3] ARM: shmobile: sh73a0: add support for adjusting CPU frequency Guennadi Liakhovetski
2013-04-05 10:00 ` Guennadi Liakhovetski
2013-04-05 10:00 ` Guennadi Liakhovetski
2013-04-18 13:52 ` Simon Horman
2013-04-18 13:52 ` Simon Horman
2013-04-18 13:52 ` Simon Horman
2013-04-05 10:00 ` [PATCH v5 2/3] ARM: shmobile: kzm9g-reference: add AS3711 and CPUFreq DT bindings Guennadi Liakhovetski
2013-04-05 10:00 ` Guennadi Liakhovetski
2013-04-05 10:00 ` Guennadi Liakhovetski
2013-04-18 13:51 ` Simon Horman
2013-04-18 13:51 ` Simon Horman
2013-04-18 13:51 ` Simon Horman
2013-04-05 10:00 ` [PATCH v5 3/3] ARM: shmobile: sh73a0: add CPUFreq support Guennadi Liakhovetski
2013-04-05 10:00 ` Guennadi Liakhovetski
2013-04-05 10:00 ` Guennadi Liakhovetski
2013-04-05 16:07 ` Sergei Shtylyov
2013-04-05 16:07 ` Sergei Shtylyov
2013-04-05 16:07 ` Sergei Shtylyov
2013-04-05 18:04 ` Guennadi Liakhovetski
2013-04-05 18:04 ` Guennadi Liakhovetski
2013-04-05 18:04 ` Guennadi Liakhovetski
2013-04-05 18:16 ` Sergei Shtylyov
2013-04-05 18:16 ` Sergei Shtylyov
2013-04-05 18:16 ` Sergei Shtylyov
2013-04-18 13:52 ` Simon Horman [this message]
2013-04-18 13:52 ` Simon Horman
2013-04-18 13:52 ` Simon Horman
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=20130418135212.GL20929@verge.net.au \
--to=horms@verge.net.au \
--cc=cpufreq@vger.kernel.org \
--cc=g.liakhovetski+renesas@gmail.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=rjw@sisk.pl \
/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.