From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maxime Ripard Subject: Re: [PATCH 10/10] arm64: dts: allwinner: h5: Add CPU Operating Performance Points table Date: Wed, 30 Jan 2019 10:29:27 +0100 Message-ID: <20190130092927.x65ihy3je5n6324w@flea> References: <20190130084203.25053-1-wens@csie.org> <20190130084203.25053-11-wens@csie.org> Reply-To: maxime.ripard-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="fkao57vkiawei5pc" Return-path: Sender: linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Content-Disposition: inline In-Reply-To: <20190130084203.25053-11-wens-jdAy2FN1RRM@public.gmane.org> List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , To: Chen-Yu Tsai Cc: linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org, Icenowy Zheng , Andre Przywara , Emmanuel Vadot , Jagan Teki , Sergey Matyukevich , Hauke Mehrtens , linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: devicetree@vger.kernel.org --fkao57vkiawei5pc Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline On Wed, Jan 30, 2019 at 04:42:03PM +0800, Chen-Yu Tsai wrote: > enable-method = "psci"; > clocks = <&ccu CLK_CPUX>; > clock-latency-ns = <244144>; /* 8 32k periods */ > + operating-points-v2 = <&cpu_opp_table>; > + #cooling-cells = <2>; > + }; > + }; > + > + cpu_opp_table: opp_table { > + compatible = "operating-points-v2"; > + opp-shared; > + > + opp@408000000 { > + opp-hz = /bits/ 64 <408000000>; > + opp-microvolt = <1000000 1000000 1310000>; > + clock-latency-ns = <244144>; /* 8 32k periods */ > + }; > + > + opp@648000000 { > + opp-hz = /bits/ 64 <648000000>; > + opp-microvolt = <1040000 1040000 1310000>; > + clock-latency-ns = <244144>; /* 8 32k periods */ > + }; > + > + opp@816000000 { > + opp-hz = /bits/ 64 <816000000>; > + opp-microvolt = <1080000 1080000 1310000>; > + clock-latency-ns = <244144>; /* 8 32k periods */ > + }; > + > + opp@912000000 { > + opp-hz = /bits/ 64 <912000000>; > + opp-microvolt = <1120000 1120000 1310000>; > + clock-latency-ns = <244144>; /* 8 32k periods */ > + }; > + > + opp@960000000 { > + opp-hz = /bits/ 64 <960000000>; > + opp-microvolt = <1160000 1160000 1310000>; > + clock-latency-ns = <244144>; /* 8 32k periods */ > + }; > + > + opp@1008000000 { > + opp-hz = /bits/ 64 <1008000000>; > + opp-microvolt = <1200000 1200000 1310000>; > + clock-latency-ns = <244144>; /* 8 32k periods */ > + }; > + > + opp@1056000000 { > + opp-hz = /bits/ 64 <1056000000>; > + opp-microvolt = <1240000 1240000 1310000>; > + clock-latency-ns = <244144>; /* 8 32k periods */ > + }; > + > + opp@1104000000 { > + opp-hz = /bits/ 64 <1104000000>; > + opp-microvolt = <1260000 1260000 1310000>; > + clock-latency-ns = <244144>; /* 8 32k periods */ > + }; > + > + opp@1152000000 { > + opp-hz = /bits/ 64 <1152000000>; > + opp-microvolt = <1300000 1300000 1310000>; > + clock-latency-ns = <244144>; /* 8 32k periods */ What is the frequency and voltage that U-Boot sets up? We've had the issue with the A33 that it's started at 1008MHz, with the matching voltage, and ramping up the frequency to 1.2GHz on boards without PMIC support would increase the frequency but not the voltage, resulting in a brownout. Maxime -- Maxime Ripard, Bootlin Embedded Linux and Kernel engineering https://bootlin.com --fkao57vkiawei5pc--