[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohpomVitj=mMmT3Z_QPgxzDyXkKN6xYReyJxO1Nc3ei=zCww@mail.gmail.com>
Date: Sat, 9 Mar 2013 11:06:55 +0800
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Guennadi Liakhovetski <g.liakhovetski@....de>
Cc: rjw@...k.pl, Steve.Bannister@....com, linux@....linux.org.uk,
linux-pm@...r.kernel.org,
Sudeep KarkadaNagesha <sudeep.karkadanagesha@....com>,
devicetree-discuss@...ts.ozlabs.org, Liviu.Dudau@....com,
linux-kernel@...r.kernel.org, cpufreq@...r.kernel.org,
robin.randhawa@....com, linux-arm-kernel@...ts.infradead.org,
mark.hambleton@...adcom.com, linaro-kernel@...ts.linaro.org,
charles.garcia-tobin@....com
Subject: Re: [PATCH V2] cpufreq: ARM big LITTLE: Add generic cpufreq driver
and its DT glue
On 8 March 2013 14:11, Guennadi Liakhovetski <g.liakhovetski@....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 :)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists