From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] ARM: dts: sunxi: Fix cpufreq instabilities
Date: Sat, 21 Mar 2015 19:20:35 +0100 [thread overview]
Message-ID: <20150321182035.GE2774@lukather> (raw)
In-Reply-To: <1426834160-10409-1-git-send-email-wens@csie.org>
On Fri, Mar 20, 2015 at 02:49:18PM +0800, Chen-Yu Tsai wrote:
> Hi Maxime,
>
> Here's v2 of the sunxi cpufreq dts fixes, aimed at 4.0.
>
> 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.
Applied both, thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150321/6037c727/attachment.sig>
next prev parent reply other threads:[~2015-03-21 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 6:49 [PATCH v2 0/2] ARM: dts: sunxi: Fix cpufreq instabilities Chen-Yu Tsai
2015-03-20 6:49 ` [PATCH v2 1/2] ARM: dts: sun4i: a10-lime: Override and remove 1008MHz OPP setting Chen-Yu Tsai
2015-03-20 6:49 ` [PATCH v2 2/2] ARM: dts: sunxi: Remove overclocked/overvoltaged OPP Chen-Yu Tsai
2015-03-21 18:20 ` Maxime Ripard [this message]
2015-03-23 23:43 ` [PATCH v2 0/2] ARM: dts: sunxi: Fix cpufreq instabilities Chen-Yu Tsai
2015-03-24 0:07 ` 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=20150321182035.GE2774@lukather \
--to=maxime.ripard@free-electrons.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