lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <trinity-888f5bdb-1e23-4b5f-83c3-f36ade039908-1732719986576@trinity-msg-rest-gmx-gmx-live-5cd5dd5458-8s6ml>
Date: Wed, 27 Nov 2024 15:06:26 +0000
From: Frank Wunderlich <frank-w@...lic-files.de>
To: angelogioacchino.delregno@...labora.com, linux@...web.de,
 robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
 matthias.bgg@...il.com
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org, linux-mediatek@...ts.infradead.org
Subject: Aw: Re: [RFC v1 14/14] arm64: dts: mediatek: mt7988: add
 operating-points

&gt; Gesendet: Mittwoch, 27. November 2024 um 14:34
&gt; Von: "AngeloGioacchino Del Regno" <angelogioacchino.delregno@...labora.com>
&gt; An: "Frank Wunderlich" <linux@...web.de>, "Rob Herring" <robh@...nel.org>, "Krzysztof Kozlowski" <krzk+dt@...nel.org>, "Conor Dooley" <conor+dt@...nel.org>, "Matthias Brugger" <matthias.bgg@...il.com>
&gt; CC: "Frank Wunderlich" <frank-w@...lic-files.de>, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-mediatek@...ts.infradead.org
&gt; Betreff: Re: [RFC v1 14/14] arm64: dts: mediatek: mt7988: add operating-points
&gt;
&gt; Il 29/10/24 11:39, Frank Wunderlich ha scritto:
&gt; &gt; From: Frank Wunderlich <frank-w@...lic-files.de>
&gt; &gt;
&gt; &gt; Add operating points defining frequency/voltages of cpu cores.
&gt; &gt;
&gt; &gt; Signed-off-by: Frank Wunderlich <frank-w@...lic-files.de>
&gt; &gt; ---
&gt; &gt;   arch/arm64/boot/dts/mediatek/mt7988a.dtsi | 45 +++++++++++++++++++++--
&gt; &gt;   1 file changed, 41 insertions(+), 4 deletions(-)
&gt; &gt;
&gt; &gt; diff --git a/arch/arm64/boot/dts/mediatek/mt7988a.dtsi b/arch/arm64/boot/dts/mediatek/mt7988a.dtsi
&gt; &gt; index e037854666c1..25669d498617 100644
&gt; &gt; --- a/arch/arm64/boot/dts/mediatek/mt7988a.dtsi
&gt; &gt; +++ b/arch/arm64/boot/dts/mediatek/mt7988a.dtsi
&gt; &gt; @@ -16,32 +16,69 @@ cpus {
&gt; &gt;   		#address-cells = &lt;1&gt;;
&gt; &gt;   		#size-cells = &lt;0&gt;;
&gt; &gt;
&gt; &gt; -		cpu@0 {
&gt; &gt; +		cpu0: cpu@0 {
&gt;
&gt; Where are those cpuX labels used? I don't see any usage.

these are used in later patch and needed in uboot when we want to switch to OF_UPSTREAM.

&gt; &gt;   			compatible = "arm,cortex-a73";
&gt; &gt;   			reg = &lt;0x0&gt;;
&gt; &gt;   			device_type = "cpu";
&gt; &gt;   			enable-method = "psci";
&gt; &gt; +			clocks = &lt;&amp;mcusys CLK_MCU_ARM_DIV_SEL&gt;,
&gt; &gt; +				 &lt;&amp;topckgen CLK_TOP_XTAL&gt;;
&gt; &gt; +			clock-names = "cpu", "intermediate";
&gt; &gt; +			operating-points-v2 = &lt;&amp;cluster0_opp&gt;;
&gt; &gt;   		};
&gt; &gt;
&gt; &gt; -		cpu@1 {
&gt; &gt; +		cpu1: cpu@1 {
&gt; &gt;   			compatible = "arm,cortex-a73";
&gt; &gt;   			reg = &lt;0x1&gt;;
&gt; &gt;   			device_type = "cpu";
&gt; &gt;   			enable-method = "psci";
&gt; &gt; +			clocks = &lt;&amp;mcusys CLK_MCU_ARM_DIV_SEL&gt;,
&gt; &gt; +				 &lt;&amp;topckgen CLK_TOP_XTAL&gt;;
&gt; &gt; +			clock-names = "cpu", "intermediate";
&gt; &gt; +			operating-points-v2 = &lt;&amp;cluster0_opp&gt;;
&gt; &gt;   		};
&gt; &gt;
&gt; &gt; -		cpu@2 {
&gt; &gt; +		cpu2: cpu@2 {
&gt; &gt;   			compatible = "arm,cortex-a73";
&gt; &gt;   			reg = &lt;0x2&gt;;
&gt; &gt;   			device_type = "cpu";
&gt; &gt;   			enable-method = "psci";
&gt; &gt; +			clocks = &lt;&amp;mcusys CLK_MCU_ARM_DIV_SEL&gt;,
&gt; &gt; +				 &lt;&amp;topckgen CLK_TOP_XTAL&gt;;
&gt; &gt; +			clock-names = "cpu", "intermediate";
&gt; &gt; +			operating-points-v2 = &lt;&amp;cluster0_opp&gt;;
&gt; &gt;   		};
&gt; &gt;
&gt; &gt; -		cpu@3 {
&gt; &gt; +		cpu3: cpu@3 {
&gt; &gt;   			compatible = "arm,cortex-a73";
&gt; &gt;   			reg = &lt;0x3&gt;;
&gt; &gt;   			device_type = "cpu";
&gt; &gt;   			enable-method = "psci";
&gt; &gt; +			clocks = &lt;&amp;mcusys CLK_MCU_ARM_DIV_SEL&gt;,
&gt; &gt; +				 &lt;&amp;topckgen CLK_TOP_XTAL&gt;;
&gt; &gt; +			clock-names = "cpu", "intermediate";
&gt; &gt; +			operating-points-v2 = &lt;&amp;cluster0_opp&gt;;
&gt; &gt; +		};
&gt; &gt; +
&gt; &gt; +		cluster0_opp: opp-table-0 {
&gt; &gt; +			compatible = "operating-points-v2";
&gt; &gt; +			opp-shared;
&gt; &gt; +			opp00 {
&gt;
&gt; ...But you can also be consistent with other devicetrees and follow the pattern
&gt; for the node names of the OPP entries.
&gt;
&gt; opp-800000000
&gt; opp-1100000000
&gt; ...etc

ok, will change this..so just adding the opp-hz value to the name (or label)?

&gt; Cheers,
&gt; Angelo
&gt;
&gt; &gt; +				opp-hz = /bits/ 64 &lt;800000000&gt;;
&gt; &gt; +				opp-microvolt = &lt;850000&gt;;
&gt; &gt; +			};
&gt; &gt; +			opp01 {
&gt; &gt; +				opp-hz = /bits/ 64 &lt;1100000000&gt;;
&gt; &gt; +				opp-microvolt = &lt;850000&gt;;
&gt; &gt; +			};
&gt; &gt; +			opp02 {
&gt; &gt; +				opp-hz = /bits/ 64 &lt;1500000000&gt;;
&gt; &gt; +				opp-microvolt = &lt;850000&gt;;
&gt; &gt; +			};
&gt; &gt; +			opp03 {
&gt; &gt; +				opp-hz = /bits/ 64 &lt;1800000000&gt;;
&gt; &gt; +				opp-microvolt = &lt;900000&gt;;
&gt; &gt; +			};
&gt; &gt;   		};
&gt; &gt;   	};
&gt; &gt;
&gt;
&gt;
&gt; </frank-w@...lic-files.de></frank-w@...lic-files.de></frank-w@...lic-files.de></matthias.bgg@...il.com></conor+dt@...nel.org></krzk+dt@...nel.org></robh@...nel.org></linux@...web.de></angelogioacchino.delregno@...labora.com>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ