All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Gerlach <d-gerlach@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	linux-pm@vger.kernel.org, Viresh Kumar <viresh.kumar@linaro.org>,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Dave Gerlach <d-gerlach@ti.com>
Subject: [PATCH 0/3] ARM: dts: am33xx/dra7xx: Fix cpufreq regression
Date: Wed, 14 Sep 2016 15:57:14 -0500	[thread overview]
Message-ID: <20160914205717.21975-1-d-gerlach@ti.com> (raw)

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.

Regards,
Dave

[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


WARNING: multiple messages have this Message-ID (diff)
From: d-gerlach@ti.com (Dave Gerlach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM: dts: am33xx/dra7xx: Fix cpufreq regression
Date: Wed, 14 Sep 2016 15:57:14 -0500	[thread overview]
Message-ID: <20160914205717.21975-1-d-gerlach@ti.com> (raw)

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.

Regards,
Dave

[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

             reply	other threads:[~2016-09-14 20:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-14 20:57 Dave Gerlach [this message]
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   ` 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   ` 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 20:57   ` Dave Gerlach
2016-09-14 23:32 ` [PATCH 0/3] ARM: dts: am33xx/dra7xx: Fix cpufreq regression Tony Lindgren
2016-09-14 23:32   ` Tony Lindgren

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=20160914205717.21975-1-d-gerlach@ti.com \
    --to=d-gerlach@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=tony@atomide.com \
    --cc=viresh.kumar@linaro.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 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.