From nobody Wed Dec 17 03:01:22 2025 Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (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 C7DA61BDC5; Tue, 16 Jan 2024 13:21:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=feathertop.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=feathertop.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=feathertop.org header.i=@feathertop.org header.b="Q4A9nCDO"; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="M9OJFDYO" Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id BBA785C01A4; Tue, 16 Jan 2024 08:21:34 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 16 Jan 2024 08:21:34 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=feathertop.org; h=cc:cc:content-transfer-encoding:content-type:date:date:from :from:in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to; s=fm2; t=1705411294; x= 1705497694; bh=mqRapvDpAQ7FPAyJBmNhOYsAn7gqgD2a+gSOVpqzeBY=; b=Q 4A9nCDOj2O4z55kRsqrOU8cyRblkqsxjY9aWZ1RLm9c4SoYaP8KtpepdoZlyNh8C bkGNaRMKNC4eQyvjVp0uLbiI5vcxAWwKUr5YVHrYgBdLPx7WZZscA2Zjm/ld4k8U rXilvmaz/g9U1o8GL9ApgmSj7rMF4NTpvlK2oP82t9gcQb2K5c9TUlRGaifWrIeC 3mO90zFZERnpdTu/A0DFjHuSIQy+DJMvXlNOcMYB1/6hD+i24VN9Nxey4VoSogfz oM2aCNlLAFqPiBmhUZcTJ7mAIUfBho4x3d9GukAXpVllQb2I/CSK6eGi6yws2BCj j1SBGtstEtO1azJFl9XJw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1705411294; x= 1705497694; bh=mqRapvDpAQ7FPAyJBmNhOYsAn7gqgD2a+gSOVpqzeBY=; b=M 9OJFDYOppzJqOKls4EBmRmOpQCIGzkuYDHaUQNoKh5IsaT0sWibeExfkEy21TcrS bSyyVA8sz6fg96LEQWZ1eCJYdmj5OpM5WoFjUe8GOLjgo4hl0JTQSPayuGYWX+SC ljVdFPXxVcWxstZgqMlzSVQVnMpYpRdoRHnYmdYbHMfdlmp9Jhw3VuBHEPZGSsOT QoIg6SAU1NA4Fnff7IJRD8zcTKeKqFM1+1o1mRgyDlkBmkBVi/SmP0wweMMcgnV+ Oq6VsLp7dn8TTTqLEbzcYA3Th5IqNl6z3xoDDNCnBJ2yqu+9IcBzasWVH6E8Ok5/ PhTjPbh0ON+5iRC9dBUSg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdejfedgheduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkofgjfhgggfestdekredtredttdenucfhrhhomhepvfhimhcu nfhunhhnuceothhimhesfhgvrghthhgvrhhtohhprdhorhhgqeenucggtffrrghtthgvrh hnpeefffeuhfetgeeikeejvefgtdefteehgfdvhfetfeeuffeuhffhfeekgfekgeehieen ucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehtihhmse hfvggrthhhvghrthhophdrohhrgh X-ME-Proxy: Feedback-ID: i1f8241ce:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 16 Jan 2024 08:21:28 -0500 (EST) Received: by feathertop.org (sSMTP sendmail emulation); Wed, 17 Jan 2024 00:21:26 +1100 From: Tim Lunn To: linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org Cc: Tim Lunn , linux-arm-kernel@lists.infradead.org, Chris Zhong , Conor Dooley , Heiko Stuebner , Krzysztof Kozlowski , Lee Jones , Rob Herring , Zhang Qing , linux-kernel@vger.kernel.org Subject: [PATCH v2 2/3] dt-bindings: rockchip: rk809 fix existing example Date: Wed, 17 Jan 2024 00:21:01 +1100 Message-Id: <20240116132102.3272682-3-tim@feathertop.org> X-Mailer: git-send-email 2.40.1 In-Reply-To: <20240116132102.3272682-1-tim@feathertop.org> References: <20240116132102.3272682-1-tim@feathertop.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Fix typo in the example specifying wrong compatible string for rk809. Remove additional vccX-supply properties that dont exist on rk809. Signed-off-by: Tim Lunn Acked-by: Conor Dooley --- Changes in v2: - Fix vcc-supply warning detected by dt_binding bot Documentation/devicetree/bindings/mfd/rockchip,rk809.yaml | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/Documentation/devicetree/bindings/mfd/rockchip,rk809.yaml b/Do= cumentation/devicetree/bindings/mfd/rockchip,rk809.yaml index bac2e751e2f2..9b9d670708ce 100644 --- a/Documentation/devicetree/bindings/mfd/rockchip,rk809.yaml +++ b/Documentation/devicetree/bindings/mfd/rockchip,rk809.yaml @@ -154,8 +154,8 @@ examples: #address-cells =3D <1>; #size-cells =3D <0>; =20 - rk808: pmic@1b { - compatible =3D "rockchip,rk808"; + rk809: pmic@1b { + compatible =3D "rockchip,rk809"; reg =3D <0x1b>; #clock-cells =3D <1>; clock-output-names =3D "xin32k", "rk808-clkout2"; @@ -174,9 +174,6 @@ examples: vcc7-supply =3D <&vcc_sysin>; vcc8-supply =3D <&vcc3v3_sys>; vcc9-supply =3D <&vcc_sysin>; - vcc10-supply =3D <&vcc_sysin>; - vcc11-supply =3D <&vcc_sysin>; - vcc12-supply =3D <&vcc3v3_sys>; =20 regulators { vdd_center: DCDC_REG1 { --=20 2.40.1