From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Quentin Schulz <quentin.schulz@free-electrons.com>
Cc: robh+dt@kernel.org, mark.rutland@arm.com, linux@armlinux.org.u,
wens@csie.org, icenowy@aosc.xyz, linux-sunxi@googlegroups.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
thomas.petazzoni@free-electrons.com
Subject: Re: [PATCH] ARM: sun8i: a33: remove highest OPP to fix CPU crashes
Date: Tue, 21 Mar 2017 16:56:32 +0100 [thread overview]
Message-ID: <20170321155632.k7vtmkorucsspnun@lukather> (raw)
In-Reply-To: <20170320112551.25825-1-quentin.schulz@free-electrons.com>
[-- Attachment #1: Type: text/plain, Size: 987 bytes --]
On Mon, Mar 20, 2017 at 12:25:51PM +0100, Quentin Schulz wrote:
> The highest supported frequency (1.2GHz) requires to "overvolt" the CPU.
> However, some boards still do not have the cpu-supply DT property in the
> cpu DT node which means that the CPU will always run with the same input
> voltage but try to run at 1.2GHz frequency. This is the source of
> (experienced) CPU crashes.
>
> Remove the OPP which requires overvolting the CPU until all boards have
> a cpu-supply property.
>
> Fixes: 03749eb88e635ad67818827adde8e5eea7b64571 ("ARM: dts: sun8i: add
> opp-v2 table for A33")
The commit ID must be 12 chars, as documented in
Documentation/process/submitting-patches.rst.
You can also use the pretty format given there to be sure to have it
right.
>
> Signed-off-by: Quentin Schulz <quentin.schulz@free-electrons.com>
Applied, thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2017-03-21 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 11:25 Quentin Schulz
2017-03-21 15:56 ` Maxime Ripard [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=20170321155632.k7vtmkorucsspnun@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=icenowy@aosc.xyz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=linux@armlinux.org.u \
--cc=mark.rutland@arm.com \
--cc=quentin.schulz@free-electrons.com \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@free-electrons.com \
--cc=wens@csie.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
all inboxes | Powered by JetHome®