All of lore.kernel.org
 help / color / mirror / Atom feed
From: siarhei.siamashka@gmail.com (Siarhei Siamashka)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: sunxi: Remove overclocked/overvoltaged OPP
Date: Thu, 19 Mar 2015 08:59:25 +0200	[thread overview]
Message-ID: <20150319085925.70d8a10d@i7> (raw)
In-Reply-To: <1426732773-7179-3-git-send-email-wens@csie.org>

On Thu, 19 Mar 2015 10:39:33 +0800
Chen-Yu Tsai <wens@csie.org> wrote:

> Without proper regulator support for individual boards, it is dangerous
> to have overclocked/overvoltaged OPPs in the list. Cpufreq will increase
> the frequency without the accompanying voltage increase, resulting in
> an unstable system.
> 
> Remove them for now. We can revisit them with the new version of OPP
> bindings, which support boost settings and frequency ranges, among
> other things.
> 
> Signed-off-by: Chen-Yu Tsai <wens@csie.org>
> ---
>  arch/arm/boot/dts/sun5i-a13.dtsi | 3 +--
>  arch/arm/boot/dts/sun7i-a20.dtsi | 3 +--
>  2 files changed, 2 insertions(+), 4 deletions(-)

What about the sun4i-a10.dtsi file? Was it forgotten or skipped
deliberately?

-- 
Best regards,
Siarhei Siamashka

  reply	other threads:[~2015-03-19  6:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19  2:39 [PATCH 0/2] ARM: dts: sunxi: Fix cpufreq instabilities Chen-Yu Tsai
2015-03-19  2:39 ` [PATCH 1/2] ARM: dts: sun4i: a10-lime: Override and remove 1008MHz OPP setting Chen-Yu Tsai
2015-03-19  6:57   ` Siarhei Siamashka
2015-03-19  8:17     ` Chen-Yu Tsai
2015-03-19 10:28       ` Siarhei Siamashka
2015-03-26 16:58     ` [linux-sunxi] " Iain Paton
2015-03-26 17:56       ` Chen-Yu Tsai
2015-03-19  2:39 ` [PATCH 2/2] ARM: dts: sunxi: Remove overclocked/overvoltaged OPP Chen-Yu Tsai
2015-03-19  6:59   ` Siarhei Siamashka [this message]
2015-03-19  7:11     ` Chen-Yu Tsai
2015-03-19  8:14       ` Chen-Yu Tsai

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=20150319085925.70d8a10d@i7 \
    --to=siarhei.siamashka@gmail.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 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.