Re: [PATCH v3 0/2] Add stop callback to the cpufreq_driver interface.

2014-03-19 Thread Rafael J. Wysocki
On Wednesday, March 19, 2014 07:19:13 PM Viresh Kumar wrote: > On 19 March 2014 19:31, Rafael J. Wysocki wrote: > > Let's add ->stop() (or whatever to call it) *specifically* for ->setpolicy > > drivers > > setpolicy_stop() ? I know that's a bad name :) Well, what about ->stop_cpu()? -- I spea

Re: [PATCH v3 0/2] Add stop callback to the cpufreq_driver interface.

2014-03-19 Thread Viresh Kumar
On 19 March 2014 19:31, Rafael J. Wysocki wrote: > Let's add ->stop() (or whatever to call it) *specifically* for ->setpolicy > drivers setpolicy_stop() ? I know that's a bad name :) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@v

Re: [PATCH v3 0/2] Add stop callback to the cpufreq_driver interface.

2014-03-19 Thread Rafael J. Wysocki
On Wednesday, March 19, 2014 11:03:56 AM Viresh Kumar wrote: > On 19 March 2014 06:23, Rafael J. Wysocki wrote: > > On Tuesday, March 18, 2014 12:25:14 PM Dirk Brandewie wrote: > >> On 03/18/2014 12:08 PM, Srivatsa S. Bhat wrote: > >> > On 03/18/2014 10:52 PM, dirk.brande...@gmail.com wrote: > >>

Re: [PATCH v3 0/2] Add stop callback to the cpufreq_driver interface.

2014-03-18 Thread Viresh Kumar
On 19 March 2014 06:23, Rafael J. Wysocki wrote: > On Tuesday, March 18, 2014 12:25:14 PM Dirk Brandewie wrote: >> On 03/18/2014 12:08 PM, Srivatsa S. Bhat wrote: >> > On 03/18/2014 10:52 PM, dirk.brande...@gmail.com wrote: >> >> From: Dirk Brandewie >> >> >> > >> > I don't mean to nitpick, but g

Re: [PATCH v3 0/2] Add stop callback to the cpufreq_driver interface.

2014-03-18 Thread Rafael J. Wysocki
On Tuesday, March 18, 2014 12:25:14 PM Dirk Brandewie wrote: > On 03/18/2014 12:08 PM, Srivatsa S. Bhat wrote: > > On 03/18/2014 10:52 PM, dirk.brande...@gmail.com wrote: > >> From: Dirk Brandewie > >> > > > > I don't mean to nitpick, but generally its easier to deal with > > patchsets if you post

Re: [PATCH v3 0/2] Add stop callback to the cpufreq_driver interface.

2014-03-18 Thread Srivatsa S. Bhat
On 03/19/2014 12:55 AM, Dirk Brandewie wrote: > On 03/18/2014 12:08 PM, Srivatsa S. Bhat wrote: >> On 03/18/2014 10:52 PM, dirk.brande...@gmail.com wrote: >>> From: Dirk Brandewie >>> >> >> I don't mean to nitpick, but generally its easier to deal with >> patchsets if you post the subsequent versi

Re: [PATCH v3 0/2] Add stop callback to the cpufreq_driver interface.

2014-03-18 Thread Dirk Brandewie
On 03/18/2014 12:08 PM, Srivatsa S. Bhat wrote: On 03/18/2014 10:52 PM, dirk.brande...@gmail.com wrote: From: Dirk Brandewie I don't mean to nitpick, but generally its easier to deal with patchsets if you post the subsequent versions in fresh email threads. Otherwise it can get a bit muddled

Re: [PATCH v3 0/2] Add stop callback to the cpufreq_driver interface.

2014-03-18 Thread Srivatsa S. Bhat
On 03/18/2014 10:52 PM, dirk.brande...@gmail.com wrote: > From: Dirk Brandewie > I don't mean to nitpick, but generally its easier to deal with patchsets if you post the subsequent versions in fresh email threads. Otherwise it can get a bit muddled along with too many other email discussions in t

[PATCH v3 0/2] Add stop callback to the cpufreq_driver interface.

2014-03-18 Thread dirk . brandewie
From: Dirk Brandewie Changes: v2->v3 Changed the calling of the ->stop() callback to be conditional on the core being the last core controlled by a given policy. v1->2 Change name of callback function added to cpufreq_driver interface. Some drivers (intel_pstate) need to modify state on a core