Patchwork [GIT,PULL] ARM: CPUFreq updates for 3.11

login
register
mail settings
Submitter viresh kumar
Date June 24, 2013, 5:50 a.m.
Message ID <CAKohpo=v4qPDH32Y4ithr_p007nTn5AOUzkUCiHTGgQN6-=BEw@mail.gmail.com>
Download mbox
Permalink /patch/253625/
State New
Headers show

Pull-request

git://git.linaro.org/people/vireshk/linux.git cpufreq-fix-notification-arm

Comments

viresh kumar - June 24, 2013, 5:50 a.m.
Hi Rafael,

This is part of my patchset "CPUFreq: Fix {PRE|POST}CHANGE notification
sequence". It contains changes specific to cpufreq core and ARM drivers.

I have left changes to non-ARM cpufreq drivers from this pull request. See if
you can take them for 3.11.

The following changes since commit 9e895ace5d82df8929b16f58e9f515f6d54ab82d:

  Linux 3.10-rc7 (2013-06-22 09:47:31 -1000)

are available in the git repository at:

  git://git.linaro.org/people/vireshk/linux.git cpufreq-fix-notification-arm

for you to fetch changes up to f2d65dd0d573e6961165f0be35bac84997b9e707:

  cpufreq: tegra: call CPUFREQ_POSTCHANGE notfier in error cases
(2013-06-24 11:14:24 +0530)

----------------------------------------------------------------
Viresh Kumar (9):
      cpufreq: make sure frequency transitions are serialized
      cpufreq: arm-big-little: call CPUFREQ_POSTCHANGE notfier in error cases
      cpufreq: davinci: call CPUFREQ_POSTCHANGE notfier in error cases
      cpufreq: dbx500: call CPUFREQ_POSTCHANGE notfier in error cases
      cpufreq: exynos: call CPUFREQ_POSTCHANGE notfier in error cases
      cpufreq: imx6q: call CPUFREQ_POSTCHANGE notfier in error cases
      cpufreq: omap: call CPUFREQ_POSTCHANGE notfier in error cases
      cpufreq: s3c64xx: call CPUFREQ_POSTCHANGE notfier in error cases
      cpufreq: tegra: call CPUFREQ_POSTCHANGE notfier in error cases

 drivers/cpufreq/arm_big_little.c  |  4 +---
 drivers/cpufreq/cpufreq.c         |  9 +++++++++
 drivers/cpufreq/davinci-cpufreq.c |  3 +++
 drivers/cpufreq/dbx500-cpufreq.c  |  4 ++--
 drivers/cpufreq/exynos-cpufreq.c  | 10 ++++++++--
 drivers/cpufreq/imx6q-cpufreq.c   | 17 +++++++++++------
 drivers/cpufreq/omap-cpufreq.c    |  6 +++---
 drivers/cpufreq/s3c64xx-cpufreq.c |  8 ++++++--
 drivers/cpufreq/tegra-cpufreq.c   |  4 ++--
 9 files changed, 45 insertions(+), 20 deletions(-)
viresh kumar - June 24, 2013, 10:42 a.m.
On 24 June 2013 16:19, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> On Monday, June 24, 2013 11:20:35 AM Viresh Kumar wrote:
>> Hi Rafael,
>>
>> This is part of my patchset "CPUFreq: Fix {PRE|POST}CHANGE notification
>> sequence". It contains changes specific to cpufreq core and ARM drivers.
>>
>> I have left changes to non-ARM cpufreq drivers from this pull request. See if
>> you can take them for 3.11.
>>
>> The following changes since commit 9e895ace5d82df8929b16f58e9f515f6d54ab82d:
>>
>>   Linux 3.10-rc7 (2013-06-22 09:47:31 -1000)
>>
>> are available in the git repository at:
>>
>>   git://git.linaro.org/people/vireshk/linux.git cpufreq-fix-notification-arm
>>
>> for you to fetch changes up to f2d65dd0d573e6961165f0be35bac84997b9e707:
>
> Well, this contains changes that aren't specific to ARM as far as I can say.

Yeah, the first patch touches core. How do you want to proceed with this one
then? You will apply them from mail? Or you will apply first patch (core cpufreq
one) and I should send pull request without it?
Rafael J. Wysocki - June 24, 2013, 10:49 a.m.
On Monday, June 24, 2013 11:20:35 AM Viresh Kumar wrote:
> Hi Rafael,
> 
> This is part of my patchset "CPUFreq: Fix {PRE|POST}CHANGE notification
> sequence". It contains changes specific to cpufreq core and ARM drivers.
> 
> I have left changes to non-ARM cpufreq drivers from this pull request. See if
> you can take them for 3.11.
> 
> The following changes since commit 9e895ace5d82df8929b16f58e9f515f6d54ab82d:
> 
>   Linux 3.10-rc7 (2013-06-22 09:47:31 -1000)
> 
> are available in the git repository at:
> 
>   git://git.linaro.org/people/vireshk/linux.git cpufreq-fix-notification-arm
> 
> for you to fetch changes up to f2d65dd0d573e6961165f0be35bac84997b9e707:

Well, this contains changes that aren't specific to ARM as far as I can say.

Not pulled.

Thanks,
Rafael


>   cpufreq: tegra: call CPUFREQ_POSTCHANGE notfier in error cases
> (2013-06-24 11:14:24 +0530)
> 
> ----------------------------------------------------------------
> Viresh Kumar (9):
>       cpufreq: make sure frequency transitions are serialized
>       cpufreq: arm-big-little: call CPUFREQ_POSTCHANGE notfier in error cases
>       cpufreq: davinci: call CPUFREQ_POSTCHANGE notfier in error cases
>       cpufreq: dbx500: call CPUFREQ_POSTCHANGE notfier in error cases
>       cpufreq: exynos: call CPUFREQ_POSTCHANGE notfier in error cases
>       cpufreq: imx6q: call CPUFREQ_POSTCHANGE notfier in error cases
>       cpufreq: omap: call CPUFREQ_POSTCHANGE notfier in error cases
>       cpufreq: s3c64xx: call CPUFREQ_POSTCHANGE notfier in error cases
>       cpufreq: tegra: call CPUFREQ_POSTCHANGE notfier in error cases
> 
>  drivers/cpufreq/arm_big_little.c  |  4 +---
>  drivers/cpufreq/cpufreq.c         |  9 +++++++++
>  drivers/cpufreq/davinci-cpufreq.c |  3 +++
>  drivers/cpufreq/dbx500-cpufreq.c  |  4 ++--
>  drivers/cpufreq/exynos-cpufreq.c  | 10 ++++++++--
>  drivers/cpufreq/imx6q-cpufreq.c   | 17 +++++++++++------
>  drivers/cpufreq/omap-cpufreq.c    |  6 +++---
>  drivers/cpufreq/s3c64xx-cpufreq.c |  8 ++++++--
>  drivers/cpufreq/tegra-cpufreq.c   |  4 ++--
>  9 files changed, 45 insertions(+), 20 deletions(-)
> --
> To unsubscribe from this list: send the line "unsubscribe cpufreq" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
Rafael J. Wysocki - June 24, 2013, 10:59 a.m.
On Monday, June 24, 2013 04:12:29 PM Viresh Kumar wrote:
> On 24 June 2013 16:19, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > On Monday, June 24, 2013 11:20:35 AM Viresh Kumar wrote:
> >> Hi Rafael,
> >>
> >> This is part of my patchset "CPUFreq: Fix {PRE|POST}CHANGE notification
> >> sequence". It contains changes specific to cpufreq core and ARM drivers.
> >>
> >> I have left changes to non-ARM cpufreq drivers from this pull request. See if
> >> you can take them for 3.11.
> >>
> >> The following changes since commit 9e895ace5d82df8929b16f58e9f515f6d54ab82d:
> >>
> >>   Linux 3.10-rc7 (2013-06-22 09:47:31 -1000)
> >>
> >> are available in the git repository at:
> >>
> >>   git://git.linaro.org/people/vireshk/linux.git cpufreq-fix-notification-arm
> >>
> >> for you to fetch changes up to f2d65dd0d573e6961165f0be35bac84997b9e707:
> >
> > Well, this contains changes that aren't specific to ARM as far as I can say.
> 
> Yeah, the first patch touches core. How do you want to proceed with this one
> then? You will apply them from mail? Or you will apply first patch (core cpufreq
> one) and I should send pull request without it?

In your original series that patch was the last one.  What made you change your
mind and put it in front?

Rafael
viresh kumar - June 24, 2013, 11:10 a.m.
On 24 June 2013 16:29, Rafael J. Wysocki <rjw@sisk.pl> wrote:

> In your original series that patch was the last one.  What made you change your
> mind and put it in front?

I initially thought that this one would break git bisect (code would
compile, but would fail) for platforms whose code I have fixed in
this patchset.

But that is true only for failure cases, otherwise code would work as
normal.

And hence kept this at the top this time.
Rafael J. Wysocki - June 24, 2013, 11:45 a.m.
On Monday, June 24, 2013 04:40:27 PM Viresh Kumar wrote:
> On 24 June 2013 16:29, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> 
> > In your original series that patch was the last one.  What made you change your
> > mind and put it in front?
> 
> I initially thought that this one would break git bisect (code would
> compile, but would fail) for platforms whose code I have fixed in
> this patchset.
> 
> But that is true only for failure cases, otherwise code would work as
> normal.
> 
> And hence kept this at the top this time.

Well, it should go last.  Also I'd prefer to apply it directly.

Please check my comment in there too.

Thanks,
Rafael