From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 15/15] arm: dts: imx: Add missing OPP properties for CPUs
Date: Tue, 3 Jul 2018 20:34:48 +0800 [thread overview]
Message-ID: <20180703123447.GQ4348@dragon> (raw)
In-Reply-To: <264124e14b966a1bbc07c364fbd89fc55aa765e6.1527244201.git.viresh.kumar@linaro.org>
On Fri, May 25, 2018 at 04:02:01PM +0530, Viresh Kumar wrote:
> The OPP properties, like "operating-points", should either be present
> for all the CPUs of a cluster or none. If these are present only for a
> subset of CPUs of a cluster then things will start falling apart as soon
> as the CPUs are brought online in a different order. For example, this
> will happen because the operating system looks for such properties in
> the CPU node it is trying to bring up, so that it can create an OPP
> table.
>
> Add such missing properties.
>
> Fix other missing properties (like clocks, supply, clock latency) as
> well to make it all work.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Applied, thanks.
prev parent reply other threads:[~2018-07-03 12:34 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 10:31 [PATCH 00/15] arm: dts: Fix OPP and cooling device properties Viresh Kumar
2018-05-25 10:31 ` [PATCH 01/15] arm: dts: armada: Fix "#cooling-cells" property's name Viresh Kumar
2018-05-28 14:53 ` Gregory CLEMENT
2018-05-25 10:31 ` [PATCH 03/15] arm: dts: mediatek: Add missing cooling device properties for CPUs Viresh Kumar
2018-06-25 14:58 ` Matthias Brugger
2018-05-25 10:31 ` [PATCH 04/15] arm: dts: rk322x: " Viresh Kumar
2018-06-17 14:47 ` Heiko Stuebner
2018-05-25 10:31 ` [PATCH 05/15] arm: dts: uniphier: " Viresh Kumar
2018-06-01 3:25 ` Masahiro Yamada
2018-05-25 10:31 ` [PATCH 06/15] arm: dts: sun: " Viresh Kumar
2018-05-28 8:44 ` Maxime Ripard
2018-05-28 10:57 ` Viresh Kumar
2018-06-01 15:17 ` Maxime Ripard
2018-06-05 4:47 ` [PATCH V2 1/2] arm: dts: sun8i-h3: " Viresh Kumar
2018-06-05 4:47 ` [PATCH V2 2/2] arm: dts: sunxi: " Viresh Kumar
2018-06-05 7:11 ` Maxime Ripard
2018-06-05 16:02 ` Chen-Yu Tsai
2018-06-06 6:58 ` Maxime Ripard
2018-05-25 10:31 ` [PATCH 07/15] arm: dts: exynos: " Viresh Kumar
2018-05-29 13:18 ` Krzysztof Kozlowski
2018-05-30 4:38 ` Viresh Kumar
2018-05-30 12:32 ` Krzysztof Kozlowski
2018-05-31 5:22 ` Viresh Kumar
2018-06-20 18:44 ` Krzysztof Kozlowski
2018-05-25 10:31 ` [PATCH 10/15] arm: dts: rk3288: " Viresh Kumar
2018-06-17 14:47 ` Heiko Stuebner
2018-05-25 10:31 ` [PATCH 11/15] arm: dts: berlin: Add missing OPP " Viresh Kumar
2018-05-25 10:31 ` [PATCH 12/15] arm: dts: highbank: " Viresh Kumar
2018-07-02 20:25 ` Rob Herring
2018-07-02 23:27 ` Olof Johansson
2018-07-03 4:13 ` Viresh Kumar
2018-07-03 14:46 ` Olof Johansson
2018-05-25 10:32 ` [PATCH 15/15] arm: dts: imx: " Viresh Kumar
2018-05-25 11:46 ` Lucas Stach
2018-05-28 11:07 ` Viresh Kumar
2018-07-03 7:12 ` Shawn Guo
2018-07-03 8:56 ` Lucas Stach
2018-07-03 12:34 ` 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=20180703123447.GQ4348@dragon \
--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;
as well as URLs for NNTP newsgroup(s).