From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/6] ARM: dts: sun8i: add a cpu0 label to cpu@0 node on A23/33
Date: Tue, 13 Dec 2016 16:09:59 +0000 [thread overview]
Message-ID: <139af71f-390a-4023-8f82-71dd80212518@arm.com> (raw)
In-Reply-To: <20161213152252.53749-4-icenowy@aosc.xyz>
On 13/12/16 15:22, Icenowy Zheng wrote:
> A "cpu0" label is needed on cpu at 0 for cpufreq-dt to work.
>
IIUC any label should be fine and I don't see anything in the driver
looking for such label name. All I see is it looks for cpu0 regulator
for *legacy* DTs
> Add such a label, in order to prepare for cpufreq support of A23/33.
>
You need this as you add the same label in the following patches. The
commit message sounds like cpufreq-dt search for that label by name.
--
Regards,
Sudeep
next prev parent reply other threads:[~2016-12-13 16:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 15:22 [PATCH 0/6] Allwinner A33 CPU frequency scaling support Icenowy Zheng
2016-12-13 15:22 ` [PATCH 1/6] clk: sunxi-ng: fix PLL_CPUX adjusting on A33 Icenowy Zheng
2016-12-13 15:44 ` Maxime Ripard
2016-12-13 15:22 ` [PATCH 2/6] clk: sunxi-ng: set the parent rate when adjustin CPUX clock " Icenowy Zheng
2016-12-13 15:44 ` Maxime Ripard
2016-12-13 20:54 ` Icenowy Zheng
2016-12-14 9:21 ` Maxime Ripard
2016-12-13 15:22 ` [PATCH 3/6] ARM: dts: sun8i: add a cpu0 label to cpu@0 node on A23/33 Icenowy Zheng
2016-12-13 15:45 ` Maxime Ripard
2016-12-13 16:09 ` Sudeep Holla [this message]
2016-12-13 16:31 ` Chen-Yu Tsai
2016-12-13 16:45 ` Sudeep Holla
2016-12-13 15:22 ` [PATCH 4/6] ARM: dts: sun8i: add opp-v2 table for A33 Icenowy Zheng
2016-12-13 19:12 ` Maxime Ripard
2016-12-13 15:22 ` [PATCH 5/6] ARM: dts: sun8i: set cpu-supply in reference tablet DTSI Icenowy Zheng
2016-12-13 19:13 ` Maxime Ripard
2016-12-13 15:22 ` [PATCH 6/6] ARM: dts: sun8i: raise the max voltage of DCDC2 in sun8i reference tablets Icenowy Zheng
2016-12-13 19:14 ` 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=139af71f-390a-4023-8f82-71dd80212518@arm.com \
--to=sudeep.holla@arm.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