[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DC2FWE35CXPV.YM6MK820R2PV@ti.com>
Date: Thu, 14 Aug 2025 15:40:26 -0500
From: Randolph Sapp <rs@...com>
To: Nishanth Menon <nm@...com>
CC: <vigneshr@...com>, <kristo@...nel.org>, <robh@...nel.org>,
<krzk+dt@...nel.org>, <conor+dt@...nel.org>, <d-gole@...com>,
<afd@...com>, <bb@...com>, <linux-arm-kernel@...ts.infradead.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<detheridge@...com>, <matt.coster@...tec.com>,
Michael Walle
<mwalle@...nel.org>
Subject: Re: [PATCH 2/3] arm64: dts: ti: k3-am62p-j722s: enable the bxs-4-64
On Wed Aug 13, 2025 at 1:42 PM CDT, Nishanth Menon wrote:
> On 12:56-20250813, Randolph Sapp wrote:
> [...]
>
>> >> + reg = <0x00 0x0fd80000 0x00 0x80000>;
>> >> + clocks = <&k3_clks 237 1>;
>> >> + clock-names = "core";
>> >> + assigned-clocks = <&k3_clks 237 1>;
>> >> + assigned-clock-rates = <800000000>;
>
> btw, as per https://www.ti.com/lit/ds/symlink/tda4aen-q1.pdf (page 86)
> 720MHz when vdd_core is 0.75v (default)
> and 800MHz when vdd_core is 0.85v
>
> 0.85v is set in the board dts and higher OPPs are enabled depending on
> board capability.
>
> You might want to check the assigned-clock-rates based on data sheet,
> default should'nt need a assigned-clock-rate.
Are you suggesting that we set assigned-clock-rates in the board dts instead, or
do you just want to do away with assigned-clock-rates in general and eat the
perf difference?
Powered by blists - more mailing lists