From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/2] ARM: dts: imx6q-cm-fx6: fix the operation points
Date: Thu, 16 Jun 2016 09:35:20 +0800 [thread overview]
Message-ID: <20160616013520.GP20243@tiger> (raw)
In-Reply-To: <e24c7d64dbce490fbeaa0f44b56027d0@rwthex-s1-b.rwth-ad.de>
On Mon, Jun 13, 2016 at 01:24:55AM +0200, christopher.spinrath at rwth-aachen.de wrote:
> From: Valentin Raevsky <valentin@compulab.co.il>
>
> The current ldo settings of the cm-fx6 do not allow 1.2GHz cpu
> frequency. At this frequency the module behaves unstable.
>
> But the imx6q fuse indicates that 1.2GHz operation is possible.
> Hence, remove the 1.2GHz operation point in the device tree.
>
> Signed-off-by: Valentin Raevsky <valentin@compulab.co.il>
> [christopher.spinrath at rwth-aachen.de: enhance commit message, adjust
> remaining operation points to match the ones in imx6q.dtsi and add
> a comment in the device tree]
> Signed-off-by: Christopher Spinrath <christopher.spinrath@rwth-aachen.de>
> Reviewed-by: Fabio Estevam <fabio.estevam@nxp.com>
Applied, thanks.
prev parent reply other threads:[~2016-06-16 1:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 23:24 [PATCH v3 1/2] ARM: dts: imx6q-cm-fx6: fix the operation points christopher.spinrath at rwth-aachen.de
2016-06-16 1:35 ` Shawn Guo [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=20160616013520.GP20243@tiger \
--to=shawnguo@kernel.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