linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: wens@csie.org (Chen-Yu Tsai)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH resend v2 0/2] ARM: dts: sunxi: Fix cpufreq instabilities
Date: Wed, 25 Mar 2015 00:53:25 +0800	[thread overview]
Message-ID: <1427216007-9185-1-git-send-email-wens@csie.org> (raw)

Hi Maxime,

Here's v2 of the sunxi cpufreq dts fixes, rebased onto v4.0-rc5.
I assume you'll fix up the merge conflicts with 4.1 stuff?

The first patch limits the Olimex A10-Lime to 912MHz, as a few people
reported on IRC that it was unstable at 1008MHz.

The second patch removes the overclocking settings from sun[457]i dts,
so all the boards will be stable, regardless of whether regulators
were added or not.

I would like to revisit this after the new OPP bindings are merged
and support added to cpufreq-dt.


Changes since v1:

  - Added sun4i dts fixes
  - Corrected A10-Lime settings to match sun4i


Regards
ChenYu


Chen-Yu Tsai (2):
  ARM: dts: sun4i: a10-lime: Override and remove 1008MHz OPP setting
  ARM: dts: sunxi: Remove overclocked/overvoltaged OPP

 arch/arm/boot/dts/sun4i-a10-olinuxino-lime.dts | 16 ++++++++++++++++
 arch/arm/boot/dts/sun4i-a10.dtsi               |  3 +--
 arch/arm/boot/dts/sun5i-a13.dtsi               |  3 +--
 arch/arm/boot/dts/sun7i-a20.dtsi               |  3 +--
 4 files changed, 19 insertions(+), 6 deletions(-)

-- 
2.1.4

             reply	other threads:[~2015-03-24 16:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 16:53 Chen-Yu Tsai [this message]
2015-03-24 16:53 ` [PATCH resend v2 1/2] ARM: dts: sun4i: a10-lime: Override and remove 1008MHz OPP setting Chen-Yu Tsai
2015-03-26 17:11   ` [linux-sunxi] " Iain Paton
2015-03-24 16:53 ` [PATCH resend v2 2/2] ARM: dts: sunxi: Remove overclocked/overvoltaged OPP Chen-Yu Tsai
2015-03-24 21:51 ` [PATCH resend v2 0/2] ARM: dts: sunxi: Fix cpufreq instabilities Maxime Ripard

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=1427216007-9185-1-git-send-email-wens@csie.org \
    --to=wens@csie.org \
    --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;
as well as URLs for NNTP newsgroup(s).