From: Viresh Kumar <viresh.kumar@linaro.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: rjw@sisk.pl, Steve.Bannister@arm.com, linux@arm.linux.org.uk,
linux-pm@vger.kernel.org,
Sudeep KarkadaNagesha <sudeep.karkadanagesha@arm.com>,
devicetree-discuss@lists.ozlabs.org, Liviu.Dudau@arm.com,
linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org,
robin.randhawa@arm.com, linux-arm-kernel@lists.infradead.org,
mark.hambleton@broadcom.com, linaro-kernel@lists.linaro.org,
charles.garcia-tobin@arm.com
Subject: Re: [PATCH V2] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue
Date: Sat, 9 Mar 2013 11:06:55 +0800 [thread overview]
Message-ID: <CAKohpomVitj=mMmT3Z_QPgxzDyXkKN6xYReyJxO1Nc3ei=zCww@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1303080706310.24111@axis700.grange>
On 8 March 2013 14:11, Guennadi Liakhovetski <g.liakhovetski@gmx.de> wrote:
> Also in your driver you're doing
>
> cpufreq_notify_transition(&freqs, CPUFREQ_PRECHANGE);
> ...
> cpufreq_notify_transition(&freqs, CPUFREQ_POSTCHANGE);
>
> So, theoretically you could install such notifiers to adjust CPU voltages
> (using regulators too). But adding regulator calls directly to the driver
> would make it consistent with cpufreq-cpu0.c.
Yes
> so, if this doesn't violate
> any concepts, I think, it would be good to add those when suitable systems
> appear.
That's what i thought :)
WARNING: multiple messages have this Message-ID (diff)
From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue
Date: Sat, 9 Mar 2013 11:06:55 +0800 [thread overview]
Message-ID: <CAKohpomVitj=mMmT3Z_QPgxzDyXkKN6xYReyJxO1Nc3ei=zCww@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1303080706310.24111@axis700.grange>
On 8 March 2013 14:11, Guennadi Liakhovetski <g.liakhovetski@gmx.de> wrote:
> Also in your driver you're doing
>
> cpufreq_notify_transition(&freqs, CPUFREQ_PRECHANGE);
> ...
> cpufreq_notify_transition(&freqs, CPUFREQ_POSTCHANGE);
>
> So, theoretically you could install such notifiers to adjust CPU voltages
> (using regulators too). But adding regulator calls directly to the driver
> would make it consistent with cpufreq-cpu0.c.
Yes
> so, if this doesn't violate
> any concepts, I think, it would be good to add those when suitable systems
> appear.
That's what i thought :)
next prev parent reply other threads:[~2013-03-09 3:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 17:14 [PATCH V2] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue Viresh Kumar
2013-03-07 17:14 ` Viresh Kumar
2013-03-07 21:56 ` Guennadi Liakhovetski
2013-03-07 21:56 ` Guennadi Liakhovetski
2013-03-08 4:20 ` Viresh Kumar
2013-03-08 4:20 ` Viresh Kumar
2013-03-08 6:11 ` Guennadi Liakhovetski
2013-03-08 6:11 ` Guennadi Liakhovetski
2013-03-09 3:06 ` Viresh Kumar [this message]
2013-03-09 3:06 ` Viresh Kumar
2013-03-10 15:58 ` Francesco Lavra
2013-03-10 15:58 ` Francesco Lavra
2013-03-11 0:57 ` Viresh Kumar
2013-03-11 0:57 ` Viresh Kumar
2013-03-11 0:57 ` Viresh Kumar
2013-03-21 23:50 ` Rafael J. Wysocki
2013-03-21 23:50 ` Rafael J. Wysocki
2013-03-22 2:21 ` Viresh Kumar
2013-03-22 2:21 ` Viresh Kumar
2013-03-26 9:51 Viresh Kumar
2013-03-26 9:51 ` Viresh Kumar
2013-03-26 13:17 ` Rob Herring
2013-03-26 13:17 ` Rob Herring
2013-03-26 14:30 ` Viresh Kumar
2013-03-26 14:30 ` Viresh Kumar
2013-04-13 20:13 ` Francesco Lavra
2013-04-13 20:13 ` Francesco Lavra
2013-04-15 7:02 ` Viresh Kumar
2013-04-15 7:02 ` Viresh Kumar
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='CAKohpomVitj=mMmT3Z_QPgxzDyXkKN6xYReyJxO1Nc3ei=zCww@mail.gmail.com' \
--to=viresh.kumar@linaro.org \
--cc=Liviu.Dudau@arm.com \
--cc=Steve.Bannister@arm.com \
--cc=charles.garcia-tobin@arm.com \
--cc=cpufreq@vger.kernel.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=g.liakhovetski@gmx.de \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.hambleton@broadcom.com \
--cc=rjw@sisk.pl \
--cc=robin.randhawa@arm.com \
--cc=sudeep.karkadanagesha@arm.com \
/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.