Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM: dts: am33xx/dra7xx: Fix cpufreq regression
Date: Wed, 14 Sep 2016 16:32:32 -0700	[thread overview]
Message-ID: <20160914233230.xhbzxpscpvb7d6vj@atomide.com> (raw)
In-Reply-To: <20160914205717.21975-1-d-gerlach@ti.com>

* Dave Gerlach <d-gerlach@ti.com> [160914 13:57]:
> Hi,
> CPUFreq on am335x and dra7 platforms got broken by two things:
>  - Updated OPPv2 nodes in device tree were merged before driver to
>    handle them was accepted.
>  - OMAP platforms now use the new cpufreq-dt-platdev driver to create
>    cpufreq-dt platform device but non OMAP TI devices were not changed
>    over to this driver.
> 
> This series addresses the first issue listed above by reverting three of
> the dts patches that got merged to restore OPPv1 tables. The second issue
> is addressed by [1].
> 
> With both this series and that patch we will have the existing cpufreq
> support restored on am335x and dra7xx.

OK thanks I've applied these into am335x-cpufreq-regression branch
and merging that into omap-for-v4.9/dt-v2 branch as well. Seems
like no huge rush to get these into v4.8-rc series as nobody has
noticed since May. And we can request these for stable inclusion
after they hit mainline. If there is need to have these in v4.8-rc,
let me know and I'll send a pull request for am335x-cpufreq-regression
separately.

Regards,

Tony

> [1] http://marc.info/?l=linux-pm&m=147388573513082&w=2
> 
> Dave Gerlach (3):
>   Revert "ARM: dts: am335x-boneblack: Enable 1GHz OPP for cpu"
>   Revert "ARM: dts: am33xx: Move to operating-points-v2 table and
>     ti-cpufreq driver"
>   Revert "ARM: dts: dra7: Move to operating-points-v2 table"
> 
>  arch/arm/boot/dts/am335x-boneblack.dts | 11 -----
>  arch/arm/boot/dts/am33xx.dtsi          | 88 +++++-----------------------------
>  arch/arm/boot/dts/dra7.dtsi            | 26 ++--------
>  arch/arm/boot/dts/dra74x.dtsi          |  1 -
>  4 files changed, 18 insertions(+), 108 deletions(-)
> 
> -- 
> 2.9.3
> 

      parent reply	other threads:[~2016-09-14 23:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14 20:57 [PATCH 0/3] ARM: dts: am33xx/dra7xx: Fix cpufreq regression Dave Gerlach
2016-09-14 20:57 ` [PATCH 1/3] Revert "ARM: dts: am335x-boneblack: Enable 1GHz OPP for cpu" Dave Gerlach
2016-09-14 20:57 ` [PATCH 2/3] Revert "ARM: dts: am33xx: Move to operating-points-v2 table and ti-cpufreq driver" Dave Gerlach
2016-09-14 20:57 ` [PATCH 3/3] Revert "ARM: dts: dra7: Move to operating-points-v2 table" Dave Gerlach
2016-09-14 23:32 ` Tony Lindgren [this message]

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=20160914233230.xhbzxpscpvb7d6vj@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox