From: Krzysztof Kozlowski <krzk@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>, Kukjin Kim <kgene@kernel.org>,
devicetree@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] ARM: dts: exynos: Add all CPUs in cooling maps
Date: Sun, 18 Nov 2018 15:14:55 +0100 [thread overview]
Message-ID: <20181118141455.GA11419@kozik-lap> (raw)
In-Reply-To: <24d8433f544046eda4d21e8c7133e3bab770b615.1542362000.git.viresh.kumar@linaro.org>
On Fri, Nov 16, 2018 at 03:31:10PM +0530, Viresh Kumar wrote:
> Each CPU can (and does) participate in cooling down the system but the
> DT only captures a handful of them, normally CPU0, in the cooling maps.
> Things work by chance currently as under normal circumstances its the
> first CPU of each cluster which is used by the operating systems to
> probe the cooling devices. But as soon as this CPU ordering changes and
> any other CPU is used to bring up the cooling device, we will start
> seeing failures.
>
> Also the DT is rather incomplete when we list only one CPU in the
> cooling maps, as the hardware doesn't have any such limitations.
>
> Update cooling maps to include all devices affected by individual trip
> points.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
> arch/arm/boot/dts/exynos3250-artik5.dtsi | 6 +-
> arch/arm/boot/dts/exynos3250-monk.dts | 6 +-
> arch/arm/boot/dts/exynos3250-rinato.dts | 6 +-
> arch/arm/boot/dts/exynos4210-trats.dts | 4 +-
> arch/arm/boot/dts/exynos4210.dtsi | 2 +-
> .../boot/dts/exynos4412-itop-scp-core.dtsi | 8 +-
> arch/arm/boot/dts/exynos4412-midas.dtsi | 8 +-
> .../boot/dts/exynos4412-odroid-common.dtsi | 8 +-
> arch/arm/boot/dts/exynos4412-odroidu3.dts | 17 ++-
> arch/arm/boot/dts/exynos4412.dtsi | 6 +-
> arch/arm/boot/dts/exynos5250.dtsi | 7 +-
> arch/arm/boot/dts/exynos5422-odroidhc1.dts | 106 +++++++++++-------
> .../boot/dts/exynos5422-odroidxu3-common.dtsi | 106 +++++++++++-------
Thanks, applied.
Best regards,
Krzysztof
next prev parent reply other threads:[~2018-11-18 14:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 10:01 [PATCH 0/6] ARM: dts: Fix incomplete cooling-maps Viresh Kumar
2018-11-16 10:01 ` [PATCH 1/6] ARM: dts: exynos: Add all CPUs in cooling maps Viresh Kumar
2018-11-18 14:14 ` Krzysztof Kozlowski [this message]
2018-11-16 10:01 ` [PATCH 2/6] ARM: dts: ls1021a: " Viresh Kumar
2018-11-28 2:46 ` Shawn Guo
2018-11-16 10:01 ` [PATCH 3/6] ARM: dts: mt7623: " Viresh Kumar
2018-11-16 10:01 ` [PATCH 4/6] ARM: dts: rockchip: " Viresh Kumar
2018-11-26 13:16 ` Heiko Stuebner
2018-11-16 10:01 ` [PATCH 5/6] ARM: dts: sunxi: " Viresh Kumar
2018-11-19 14:39 ` Maxime Ripard
2018-11-16 10:01 ` [PATCH 6/6] ARM: dts: uniphier: " Viresh Kumar
2018-11-26 15:49 ` Masahiro Yamada
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=20181118141455.GA11419@kozik-lap \
--to=krzk@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.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).