From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: Chen-Yu Tsai <wens@csie.org>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Gregory CLEMENT <gregory.clement@free-electrons.com>,
Shuge <shuge@allwinnertech.com>,
Meng Zhang <kevin@allwinnertech.com>,
linux-arm-kernel@lists.infradead.org
Subject: ARM: dts: sun9i: Allwinner A80 dtsi - missing clock-frequency property
Date: Wed, 31 Dec 2014 01:37:12 +0100 [thread overview]
Message-ID: <54A34538.2020802@gmx.de> (raw)
In-Reply-To: <1412773376-25212-3-git-send-email-wens@csie.org>
When booting Linux 3.19-rc2 on a Merrii Optimusboard using
arch/arm/boot/dts/sun9i-a80-optimus.dts adn
arch/arm/boot/dts/sun9i-a80.dtsi I get errors
[ 0.061192] /cpus/cpu@0 missing clock-frequency property
[ 0.061209] /cpus/cpu@1 missing clock-frequency property
[ 0.061223] /cpus/cpu@2 missing clock-frequency property
[ 0.061237] /cpus/cpu@3 missing clock-frequency property
[ 0.061251] /cpus/cpu@100 missing clock-frequency property
[ 0.061266] /cpus/cpu@101 missing clock-frequency property
[ 0.061283] /cpus/cpu@102 missing clock-frequency property
[ 0.061300] /cpus/cpu@103 missing clock-frequency property
The dtsi was provided by patch
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4ab328f06e305bf3ea254f4e3c94bb4d820998c1
According to file pack/chips/sun9iw1p1/optimus/sys_config.fex supplied
in the OptimusBoard SDK the big cluster can run at up to 1800 MHz, and
the LITTLE cluster can run at up to 1200 MHz,depending on the CPU voltage:
big
1.08V (1608Mhz, 1800Mhz]
1.00V (1536Mhz, 1608Mhz]
0.96V (1440Mhz, 1536Mhz]
0.90V (1296Mhz, 1440Mhz]
0.84V ( 0Mhz, 1296Mhz]
LITTLE
1.02V (1128Mhz, 1200Mhz]
0.96V (1008Mhz, 1128Mhz]
0.90V ( 864Mhz, 1008Mhz]
0.84V ( 0Mhz, 864Mhz]
I guess the proper way to specify the data is the one described in
Documentation/devicetree/bindings/cpufreq/arm_big_little_dt.txt
Other boards might run at other frequencies. Hence we might want to put
this information into the board file
arch/arm/boot/dts/sun9i-a80-optimus.dts.
Documentation/devicetree/bindings/cpufreq/arm_big_little_dt.txt,
arch/arm/boot/dts/exynos5260.dtsi, and
arch/arm/boot/dts/exynos5420.dtsi, all assume that
cpu@0-cpu@3 are A15 (big) and cpu@101-cpu@103 are A7 (LITTLE).
Shouldn't arch/arm/boot/dts/sun9i-a80.dtsi stick to this convention?
The scripts to create the uImage and to reproduce the problem are in
https://github.com/xypron/kernel-optimusboard/tree/35d06c020f6584b5023e0e4bef67cc5a625f65bb
Best regards
Heinrich Schuchardt
WARNING: multiple messages have this Message-ID (diff)
From: Heinrich Schuchardt <xypron.glpk-Mmb7MZpHnFY@public.gmane.org>
To: Chen-Yu Tsai <wens-jdAy2FN1RRM@public.gmane.org>,
Maxime Ripard
<maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Ian Campbell
<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Gregory CLEMENT
<gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
Shuge <shuge-0TFLnhJekD6UEPyfVivIlAC/G2K4zDHf@public.gmane.org>,
Meng Zhang
<kevin-0TFLnhJekD6UEPyfVivIlAC/G2K4zDHf@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: ARM: dts: sun9i: Allwinner A80 dtsi - missing clock-frequency property
Date: Wed, 31 Dec 2014 01:37:12 +0100 [thread overview]
Message-ID: <54A34538.2020802@gmx.de> (raw)
In-Reply-To: <1412773376-25212-3-git-send-email-wens-jdAy2FN1RRM@public.gmane.org>
When booting Linux 3.19-rc2 on a Merrii Optimusboard using
arch/arm/boot/dts/sun9i-a80-optimus.dts adn
arch/arm/boot/dts/sun9i-a80.dtsi I get errors
[ 0.061192] /cpus/cpu@0 missing clock-frequency property
[ 0.061209] /cpus/cpu@1 missing clock-frequency property
[ 0.061223] /cpus/cpu@2 missing clock-frequency property
[ 0.061237] /cpus/cpu@3 missing clock-frequency property
[ 0.061251] /cpus/cpu@100 missing clock-frequency property
[ 0.061266] /cpus/cpu@101 missing clock-frequency property
[ 0.061283] /cpus/cpu@102 missing clock-frequency property
[ 0.061300] /cpus/cpu@103 missing clock-frequency property
The dtsi was provided by patch
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4ab328f06e305bf3ea254f4e3c94bb4d820998c1
According to file pack/chips/sun9iw1p1/optimus/sys_config.fex supplied
in the OptimusBoard SDK the big cluster can run at up to 1800 MHz, and
the LITTLE cluster can run at up to 1200 MHz,depending on the CPU voltage:
big
1.08V (1608Mhz, 1800Mhz]
1.00V (1536Mhz, 1608Mhz]
0.96V (1440Mhz, 1536Mhz]
0.90V (1296Mhz, 1440Mhz]
0.84V ( 0Mhz, 1296Mhz]
LITTLE
1.02V (1128Mhz, 1200Mhz]
0.96V (1008Mhz, 1128Mhz]
0.90V ( 864Mhz, 1008Mhz]
0.84V ( 0Mhz, 864Mhz]
I guess the proper way to specify the data is the one described in
Documentation/devicetree/bindings/cpufreq/arm_big_little_dt.txt
Other boards might run at other frequencies. Hence we might want to put
this information into the board file
arch/arm/boot/dts/sun9i-a80-optimus.dts.
Documentation/devicetree/bindings/cpufreq/arm_big_little_dt.txt,
arch/arm/boot/dts/exynos5260.dtsi, and
arch/arm/boot/dts/exynos5420.dtsi, all assume that
cpu@0-cpu@3 are A15 (big) and cpu@101-cpu@103 are A7 (LITTLE).
Shouldn't arch/arm/boot/dts/sun9i-a80.dtsi stick to this convention?
The scripts to create the uImage and to reproduce the problem are in
https://github.com/xypron/kernel-optimusboard/tree/35d06c020f6584b5023e0e4bef67cc5a625f65bb
Best regards
Heinrich Schuchardt
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-12-31 0:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 13:02 [PATCH v3 0/5] ARM: sunxi: Add basic support for Allwinner A80 SoC Chen-Yu Tsai
2014-10-08 13:02 ` Chen-Yu Tsai
2014-10-08 13:02 ` Chen-Yu Tsai
2014-10-08 13:02 ` [PATCH v3 1/5] ARM: sunxi: Introduce Allwinner A80 support Chen-Yu Tsai
2014-10-08 13:02 ` Chen-Yu Tsai
2014-10-08 13:02 ` Chen-Yu Tsai
2014-10-08 13:02 ` [PATCH v3 2/5] ARM: dts: sunxi: Add Allwinner A80 dtsi Chen-Yu Tsai
2014-10-08 13:02 ` Chen-Yu Tsai
2014-12-31 0:37 ` Heinrich Schuchardt [this message]
2014-12-31 0:37 ` ARM: dts: sun9i: Allwinner A80 dtsi - missing clock-frequency property Heinrich Schuchardt
2014-12-31 3:18 ` Chen-Yu Tsai
2014-12-31 3:18 ` Chen-Yu Tsai
2014-12-31 3:18 ` Chen-Yu Tsai
2014-10-08 13:02 ` [PATCH v3 3/5] ARM: dts: sun9i: Add A80 Optimus Board support Chen-Yu Tsai
2014-10-08 13:02 ` Chen-Yu Tsai
2014-10-08 13:32 ` Dinh Nguyen
2014-10-08 13:32 ` Dinh Nguyen
2014-10-08 13:32 ` Dinh Nguyen
2014-10-08 13:41 ` Chen-Yu Tsai
2014-10-08 13:41 ` Chen-Yu Tsai
2014-10-08 13:41 ` Chen-Yu Tsai
2014-10-08 13:02 ` [PATCH v3 4/5] devicetree: bindings: Document supported Allwinner sunxi SoCs Chen-Yu Tsai
2014-10-08 13:02 ` Chen-Yu Tsai
2014-10-08 13:02 ` [PATCH v3 5/5] Documentation: sunxi: Add A80 datasheet link Chen-Yu Tsai
2014-10-08 13:02 ` Chen-Yu Tsai
2014-10-09 2:54 ` [PATCH v3 0/5] ARM: sunxi: Add basic support for Allwinner A80 SoC Andreas Färber
2014-10-09 2:54 ` Andreas Färber
2014-10-10 18:30 ` Maxime Ripard
2014-10-10 18:30 ` Maxime Ripard
2014-10-10 18:30 ` Maxime Ripard
2014-10-10 18:26 ` Maxime Ripard
2014-10-10 18:26 ` 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=54A34538.2020802@gmx.de \
--to=xypron.glpk@gmx.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gregory.clement@free-electrons.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kevin@allwinnertech.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=shuge@allwinnertech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.