[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250816-tegra210-speedo-v1-0-a981360adc27@gmail.com>
Date: Sat, 16 Aug 2025 00:53:32 -0500
From: Aaron Kling via B4 Relay <devnull+webgeek1234.gmail.com@...nel.org>
To: Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Thierry Reding <thierry.reding@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>, Joseph Lo <josephl@...dia.com>,
Peter De Schrijver <pdeschrijver@...dia.com>,
Prashant Gaikwad <pgaikwad@...dia.com>
Cc: linux-clk@...r.kernel.org, devicetree@...r.kernel.org,
linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org,
Thierry Reding <treding@...dia.com>, Aaron Kling <webgeek1234@...il.com>
Subject: [PATCH 0/5] Properly Limit Tegra210 Clock Rates
The Tegra210 CVB tables were added in commit 2b2dbc2f94e5. Since then,
all Tegra210 socs have tried to scale the cpu to 1.9 GHz, when the
supported devkits are only supposed to scale to 1.5 or 1.7 GHZ.
Overclocking should not be the default state.
Signed-off-by: Aaron Kling <webgeek1234@...il.com>
---
Aaron Kling (5):
dt-bindings: clock: tegra124-dfll: Add property to limit frequency
soc: tegra: fuse: speedo-tegra210: Update speedo ids
soc: tegra: fuse: speedo-tegra210: Add sku 0x8F
clk: tegra: dfll: Support limiting max clock per device
arm64: tegra: Limit max cpu frequency on P3450
.../bindings/clock/nvidia,tegra124-dfll.txt | 3 ++
arch/arm64/boot/dts/nvidia/tegra210-p3450-0000.dts | 1 +
drivers/clk/tegra/clk-tegra124-dfll-fcpu.c | 8 ++++-
drivers/soc/tegra/fuse/speedo-tegra210.c | 39 ++++++++++++++++++----
4 files changed, 43 insertions(+), 8 deletions(-)
---
base-commit: 8f5ae30d69d7543eee0d70083daf4de8fe15d585
change-id: 20250812-tegra210-speedo-470691e8b8cc
Best regards,
--
Aaron Kling <webgeek1234@...il.com>
Powered by blists - more mailing lists