From nobody Mon Jun 8 06:41:08 2026 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id DEBB64D8D95; Fri, 5 Jun 2026 11:54:43 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780660483; cv=none; b=kFWPwDxIQzohZLOgEqBhZpZGVT4Vjcrg5fj/B37UWBn7DI/qvXqXNv/jBWqy6Kc3SgX+Ul4rw+zSALnqYcfquiaXa8H0kEkRBSAoe7EjpEajiUMGBH60WGC0TT9fvVmQIh0ul/rCi6LWeUqByCXM9ndNfxsuFU9owrLiplo4yMo= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780660483; c=relaxed/simple; bh=4quFrMpJWBka7KBZ3BJNo1AoS735u/57CPXK32qFVzo=; h=From:Date:Subject:MIME-Version:Content-Type:Message-Id:To:Cc; b=lpA++wJkJUzDNUTYd36lBlcRFLgI3hgI6sazzNE6+z0RXOmXREse6NnJeI1ZvpmwXSo06MDlgaUk6IDOV+oe47ad3IlGXHEXQawxhXMXMmW/VpVryxEvau2KKgc3g4+WVCUcdJ4ZjmKWHV7ZMzwQnBkyRC1pkokVy0mSYARWzlA= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=VFGcH8ok; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="VFGcH8ok" Received: by smtp.kernel.org (Postfix) with ESMTPS id 7B32AC2BCB9; Fri, 5 Jun 2026 11:54:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1780660483; bh=4quFrMpJWBka7KBZ3BJNo1AoS735u/57CPXK32qFVzo=; h=From:Date:Subject:To:Cc:Reply-To:From; b=VFGcH8okXd/OrQDwMPf5JEGiAs7tqJZDQr97c46fTNJg8jQxH0cm+S371F4wmHFuD uGHZpnox6AC5tkozD8c9rl3YwxyeTsDQIjsurTvsbP3e+rMjtzhoWLbnBZrjPAYy5h 7eU3/3pTzvBFXs6oajovMr1EqIL7ER1iS2YfISCxumTtA6v56YxGtzNQC++ICU51iI OSdlHvQ2cPYXBfdtJjBCRpdyg50vroKGRhja0SQIWZvXKteOO5o/dNK57cr07+pfy8 8dS08EJdwEcOYxLFRUTE2ArcpD+H7TixgjqNgeWrg/6/Jr4FTNtErPvGX0ZO6wDDhD 517pPIBnpVKqg== Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 71BF7CD6E79; Fri, 5 Jun 2026 11:54:43 +0000 (UTC) From: Ricardo Pardini via B4 Relay Date: Fri, 05 Jun 2026 13:54:35 +0200 Subject: [PATCH] arm64: dts: rockchip: fix regulator names on NanoPC-T6 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <20260605-rk3588-dts-rockchip-nanopct6-fix-schematic-names-v1-1-15dd3b23ab1a@pardini.net> X-B4-Tracking: v=1; b=H4sIAAAAAAAC/yWNQQrCMBBFr1Jm7UCaYhu8irhIJ1MzlqYlE0Uov btRl+/zeW8H5SyscGl2yPwSlTVVaE8NUPTpziihMlhje9ObDvPcnZ3DUBTzSjNF2TD5tG5Uepz kjUqRF1+E6rywom9HF+wwOcsDVO2Wud5+yevtz/ocH0zl24Hj+AC4kf6rlAAAAA== X-Change-ID: 20260603-rk3588-dts-rockchip-nanopct6-fix-schematic-names-a1b8d27f82e7 To: Rob Herring , Krzysztof Kozlowski , Conor Dooley , Heiko Stuebner Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org, Sebastian Reichel , Ricardo Pardini X-Mailer: b4 0.15.2 X-Developer-Signature: v=1; a=openpgp-sha256; l=4043; i=ricardo@pardini.net; h=from:subject:message-id; bh=kgSZTfQ3v8bdt151HvlymrV22R4yaefcQJY9/TyNagE=; b=owEBiQF2/pANAwAIATteP+Oex+3pAcsmYgBqIrkCKjjYJPyA0jamo3cGmC4t1a33loZ4y4QVl 8IxJe1nsWOJAU8EAAEIADkWIQSsGCMM9q/qytxIiJM7Xj/jnsft6QUCaiK5AhsUgAAAAAAEAA5t YW51MiwyLjUrMS4xMiwwLDMACgkQO14/457H7enpNwf7BYfuQLgrCLiVvn1YHpmkizBLJrhd1kQ 78tWZjq4WLqeGryGR/BFiSoyZ0dsYH9tdah9Cz4MPpsLn5RvLv2rKUTRm8Ucy4kEKkijZ5aDytg dC7lzmx9l3iMXLbR0q80dUcn4oTRxcW4TZ8WY2MvqOccfl2C+EkQOPVhKRoEzdMCF3XbrBrnnCN moTgXuQQ2hDscxrEEsu+eveq2jK3jDfZwNxtmIqC8ZfW7Tv92e9Jai5hJBK5kDvoi5cnIfroKI0 aEDi6Pp4MNYQU6NLEfnjz+FPHQOKzD4dXbouQAjB1V8hFppyve5pPhcEytS98D5oXjx1RfsrFLp wTJyfKLfHLw== X-Developer-Key: i=ricardo@pardini.net; a=openpgp; fpr=AC18230CF6AFEACADC4888933B5E3FE39EC7EDE9 X-Endpoint-Received: by B4 Relay for ricardo@pardini.net/default with auth_id=588 X-Original-From: Ricardo Pardini Reply-To: ricardo@pardini.net From: Ricardo Pardini Three fixed-regulator names on the NanoPC-T6 don't match the board schematic [1]. - vcc3v3_pcie2x1l0 -> vdd_mpcie_3v3 This GPIO-switched 3v3 regulator is labeled vcc3v3_pcie2x1l0, but it is wired to and consumed by &pcie2x1l1. Per the schematic, the GPIO PCIE_M2_1_PWREN controls the power net VDD_MPCIE_3.3V; rename to match. - vdd_2v0_pldo_s3 -> vcc_2v0_pldo_s3 Typo in the regulator-name property of RK806-1 DCDC reg7. The node label and the schematic power-net name both already use the vcc_ form; only the regulator-name string had vdd_. - vcc3v3_pcie30 -> vcc3v3_pcie_m2_0 The GPIO-switched 3v3 feeding the M.2 M-Key (NVMe) slot is named after the PCIe controller it sits behind rather than the schematic power net. The schematic names it VCC3V3_PCIE_M2_0 (produced by an MP2143-based buck off VCC_5V0, enabled by PCIE_M2_0_PWREN); rename to match. No functional change. [1] https://wiki.friendlyelec.com/wiki/images/9/97/NanoPC-T6_2301_SCH.PDF Signed-off-by: Ricardo Pardini --- Align three fixed-regulator names on the NanoPC-T6 (and LTS) with the labels used in the board schematic: the mini-PCIe 3v3 regulator (whose current name is actively misleading), a vdd_/vcc_ typo on RK806-1 DCDC reg7, and the M.2 M-Key 3v3 supply (named after the PCIe controller rather than the schematic power net). Using actual schematic names was pointed out by Sebastian during review of an earlier (and mostly unrelated) series [1]. No functional change. [1] https://lore.kernel.org/linux-rockchip/ah2AYT4XmYR03I7z@venus/ --- arch/arm64/boot/dts/rockchip/rk3588-nanopc-t6.dtsi | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/arch/arm64/boot/dts/rockchip/rk3588-nanopc-t6.dtsi b/arch/arm6= 4/boot/dts/rockchip/rk3588-nanopc-t6.dtsi index 84b6b53f016ab..b44aff39cb32e 100644 --- a/arch/arm64/boot/dts/rockchip/rk3588-nanopc-t6.dtsi +++ b/arch/arm64/boot/dts/rockchip/rk3588-nanopc-t6.dtsi @@ -201,25 +201,25 @@ vbus5v0_usb: regulator-vbus5v0-usb { vin-supply =3D <&vcc5v0_sys>; }; =20 - vcc3v3_pcie2x1l0: regulator-vcc3v3-pcie2x1l0 { + vdd_mpcie_3v3: regulator-vdd-mpcie-3v3 { compatible =3D "regulator-fixed"; enable-active-high; gpio =3D <&gpio4 RK_PC2 GPIO_ACTIVE_HIGH>; pinctrl-names =3D "default"; pinctrl-0 =3D <&pcie_m2_1_pwren>; - regulator-name =3D "vcc3v3_pcie2x1l0"; + regulator-name =3D "vdd_mpcie_3v3"; regulator-min-microvolt =3D <3300000>; regulator-max-microvolt =3D <3300000>; vin-supply =3D <&vcc5v0_sys>; }; =20 - vcc3v3_pcie30: regulator-vcc3v3-pcie30 { + vcc3v3_pcie_m2_0: regulator-vcc3v3-pcie-m2-0 { compatible =3D "regulator-fixed"; enable-active-high; gpios =3D <&gpio2 RK_PC5 GPIO_ACTIVE_HIGH>; pinctrl-names =3D "default"; pinctrl-0 =3D <&pcie_m2_0_pwren>; - regulator-name =3D "vcc3v3_pcie30"; + regulator-name =3D "vcc3v3_pcie_m2_0"; regulator-min-microvolt =3D <3300000>; regulator-max-microvolt =3D <3300000>; vin-supply =3D <&vcc5v0_sys>; @@ -639,7 +639,7 @@ &pcie2x1l0 { =20 &pcie2x1l1 { reset-gpios =3D <&gpio4 RK_PA2 GPIO_ACTIVE_HIGH>; - vpcie3v3-supply =3D <&vcc3v3_pcie2x1l0>; + vpcie3v3-supply =3D <&vdd_mpcie_3v3>; pinctrl-names =3D "default"; pinctrl-0 =3D <&pcie2_1_rst>; status =3D "okay"; @@ -659,7 +659,7 @@ &pcie30phy { =20 &pcie3x4 { reset-gpios =3D <&gpio4 RK_PB6 GPIO_ACTIVE_HIGH>; - vpcie3v3-supply =3D <&vcc3v3_pcie30>; + vpcie3v3-supply =3D <&vcc3v3_pcie_m2_0>; status =3D "okay"; }; =20 @@ -965,7 +965,7 @@ vcc_2v0_pldo_s3: dcdc-reg7 { regulator-min-microvolt =3D <2000000>; regulator-max-microvolt =3D <2000000>; regulator-ramp-delay =3D <12500>; - regulator-name =3D "vdd_2v0_pldo_s3"; + regulator-name =3D "vcc_2v0_pldo_s3"; =20 regulator-state-mem { regulator-on-in-suspend; --- base-commit: e43ffb69e0438cddd72aaa30898b4dc446f664f8 change-id: 20260603-rk3588-dts-rockchip-nanopct6-fix-schematic-names-a1b8d2= 7f82e7 Best regards, -- =20 Ricardo Pardini