From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 06E7DC54F55 for ; Wed, 29 Jul 2026 15:08:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-ID:Date:Subject:Cc:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=vnfCfjc57cASbG0/K+BkcAOAlxhR1Hffo3o8NKPHaoo=; b=3+9Wh4ZpH96L9B vR4hS/hplVF2Yuftw1eyAmQDK7uNLx57/dFxZ3GpfZ6Z99Xjsx5vxHISlashK5aqI0kAKMFRNQbcT G2ug4P6vn3lcY+QHdQt9LRorHBLVtD2SMvOd6vtEEnhrETw1U+DvGsqh9GNFRvTWhB4ouowRUE2ZG EZVHxkymVE2/SNBRYARAYE8SsHFQkYUbuaF+KhDwZZC0ElscZInVpH5KXTLjPAliCQ9XV5BZQjd9L xOk9i6D4uqKa1jn7c/It3yHVcI6jNBDd7HOf9Ht3q5bNxV6sGX2e1p1XXfDuOiOaF7/8LyF2MWNU+ Aq5lqx7n8UsJZuFIf8+Q==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1wp5si-00000008LLc-1pjG; Wed, 29 Jul 2026 15:07:40 +0000 Received: from hall.aurel32.net ([2001:bc8:30d7:100::1]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1wp5sf-00000008LKd-1NvT for linux-riscv@lists.infradead.org; Wed, 29 Jul 2026 15:07:38 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=aurel32.net ; s=202004.hall; h=Content-Transfer-Encoding:MIME-Version:References: In-Reply-To:Message-ID:Date:Subject:Cc:To:From:Content-Type:From:Reply-To: Subject:Content-ID:Content-Description:X-Debbugs-Cc; bh=aAP1gRw0f/juH/GrkAVHhQx3XXlaFij+1lKD3oiCoMI=; b=EoQk1r90j4GLpmmKJJHFhrbjuE hNuQIAd6+6oY4LzLf0RmTnBqra6Q9hf0KYz8T/qxcYkbw9C2JYRsmG5kX1vo3DSaOQCu/QCib0q9c m4zu9Y1POB2RfcBJkBbivjh3j4jt0Qsg3+Efsl2S5dfkxLqOYRsBRXpf/+V9CiLh1l+ZA/EvdqLhx JGQ90KJM3AQyQeASVBZYvd88xdpjJIymwKbH1hbdY20w/sR/znC9JPsBBrYj7nf/iycvoWuK+OOIA wXcxcLzRB2wIf5thx0c/rDxdF4DQswXfv2uYvrGBpwtROyWu2vHRtrrickslw9Mo3xwVWiHQiG4Vi Hei3VhYg==; Received: from authenticated user by hall.aurel32.net with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wp5sd-00000002eB5-1JeV; Wed, 29 Jul 2026 17:07:35 +0200 From: Aurelien Jarno To: linux-kernel@vger.kernel.org, Rob Herring , Krzysztof Kozlowski , Conor Dooley , Yixun Lan , Paul Walmsley , Palmer Dabbelt , Albert Ou , Alexandre Ghiti , Alex Elder Cc: Aurelien Jarno , stable@vger.kernel.org, devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS), linux-riscv@lists.infradead.org (open list:RISC-V SPACEMIT SoC Support), spacemit@lists.linux.dev (open list:RISC-V SPACEMIT SoC Support) Subject: [PATCH 1/6] riscv: dts: spacemit: k1-bananapi-f3: fix maximum CPU core voltage Date: Wed, 29 Jul 2026 17:02:18 +0200 Message-ID: <20260729150722.1598630-2-aurelien@aurel32.net> X-Mailer: git-send-email 2.53.0 In-Reply-To: <20260729150722.1598630-1-aurelien@aurel32.net> References: <20260729150722.1598630-1-aurelien@aurel32.net> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.9.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20260729_080737_369970_A5CCBD22 X-CRM114-Status: GOOD ( 10.81 ) X-BeenThere: linux-riscv@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-riscv" Errors-To: linux-riscv-bounces+linux-riscv=archiver.kernel.org@lists.infradead.org On the Banana Pi BPI-F3 board, the buck1 and buck2 voltage regulators, which supply the CPU core voltage, are configured with a maximum output voltage of 3.45V, while the highest operating point requires only 1.050V. This means that a kernel bug, OPP misconfiguration, or privileged userspace could request a voltage above the safe operating limit, causing possible permanent CPU damage. Set the maximum regulator voltage to 1.050V instead. Fixes: 09a412d39748 ("riscv: dts: spacemit: define regulator constraints") Link: https://sashiko.dev/#/message/20260728211020.1248676-2-aurelien%40aurel32.net Cc: stable@vger.kernel.org Signed-off-by: Aurelien Jarno --- arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts b/arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts index e2961b7e0a3eb..58035d886bf67 100644 --- a/arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts +++ b/arch/riscv/boot/dts/spacemit/k1-bananapi-f3.dts @@ -237,14 +237,14 @@ pmic@41 { regulators { buck1_0v9: buck1 { regulator-min-microvolt = <500000>; - regulator-max-microvolt = <3450000>; + regulator-max-microvolt = <1050000>; regulator-ramp-delay = <5000>; regulator-always-on; }; buck2 { regulator-min-microvolt = <500000>; - regulator-max-microvolt = <3450000>; + regulator-max-microvolt = <1050000>; regulator-ramp-delay = <5000>; regulator-always-on; }; -- 2.53.0 _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv