From nobody Wed Feb 11 05:41:46 2026 Received: from out-181.mta0.migadu.com (out-181.mta0.migadu.com [91.218.175.181]) (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 F0831315D33; Thu, 13 Nov 2025 08:53:00 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.181 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763023983; cv=none; b=HhqO1McS5sV3zGqTmZSpZQ1KPcG62zM4DnPni/NBYVuXP+FVJSl9U0myNXMuZs6mNa4d1hVl9T63i2WejW/FTDsOqYGa5uatUgh/mqyf+OwYNUdRsUK40uJTerUnPGEIWRRPryva1E8K8vtO0gLnj9QsSCzsHqGhHu0bjtVUHpw= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763023983; c=relaxed/simple; bh=Vi2BDy+PFWaqoFmrmmtqaKDztibjr3EEGPJFaMiQ+dQ=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=GZqi8009h09AzdHqhW77uhFaRQWKBrnM/jZF8Yb4RJqCkFAzP+xXE2SRKWMA8BCpNfYF8xJFYV1fJ457r3mAELB3M4Tf76N0S+RzAXWGq+QkHUKnBOmm5CeAthkUGqnxbmEQuvX0xFiG3gPWpVekwrt/XIm2Uq4IhZ3dJbnzYt4= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=eXAhceal; arc=none smtp.client-ip=91.218.175.181 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="eXAhceal" Date: Thu, 13 Nov 2025 10:52:50 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1763023978; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references; bh=hezNVpxVc+T3j4/xFsOqUzZTQNKcSsqpvy2W+OjTBuM=; b=eXAhcealCFIXn0m4DWcrZJU4+iv7vFFr++30+aPbF9vVVtBty1PgvTSsgXWsPzjYVvQflQ bOpd7P6JFfCaQ1vYBfYx2aBagwdSLSQF8PxDKK+plUjrbNPSPEp2Iy3pP+eheKFDOi5pUp Of+WbXQRl9kqhRqpHSXDIANi8Cz+fbo= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Matti Vaittinen To: Matti Vaittinen , Matti Vaittinen Cc: Lee Jones , Pavel Machek , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Sebastian Reichel , Liam Girdwood , Mark Brown , Michael Turquette , Stephen Boyd , Matti Vaittinen , Linus Walleij , Bartosz Golaszewski , Alexandre Belloni , linux-leds@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, linux-clk@vger.kernel.org, linux-gpio@vger.kernel.org, linux-rtc@vger.kernel.org, Andreas Kemnade Subject: [PATCH v4 06/16] dt-bindings: leds: bd72720: Add BD72720 Message-ID: <27166fec843d8bb81c90762e6fc73559883e1563.1763022807.git.mazziesaccount@gmail.com> Reply-To: Matti Vaittinen References: Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="q1lGGyIWEu/v15kj" Content-Disposition: inline In-Reply-To: X-Migadu-Flow: FLOW_OUT --q1lGGyIWEu/v15kj Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" From: Matti Vaittinen Add the ROHM BD72720 documentation to the binding documents. Signed-off-by: Matti Vaittinen Acked-by: Krzysztof Kozlowski --- Revision history: RFCv1 =3D>: - No changes NOTE: The Linux LED driver does currently have: values bd72720-grnled and bd72720-ambled for the rohm,led-compatible. These are handled identically to the existing bd71828-grnled and bd71828-ambled and should be removed from the driver. Thus they are not documented in the binding document. Furthermore, the BD72720 Linux driver does not use the compatible property from the LED node. The Linux driver is load and probed based on the PMIC compatible in the MFD node. Thus no compatible string for the BD72720 LED node is added. --- .../devicetree/bindings/leds/rohm,bd71828-leds.yaml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/Documentation/devicetree/bindings/leds/rohm,bd71828-leds.yaml = b/Documentation/devicetree/bindings/leds/rohm,bd71828-leds.yaml index b7a3ef76cbf4..64cc40523e3d 100644 --- a/Documentation/devicetree/bindings/leds/rohm,bd71828-leds.yaml +++ b/Documentation/devicetree/bindings/leds/rohm,bd71828-leds.yaml @@ -10,11 +10,12 @@ maintainers: - Matti Vaittinen =20 description: | - This module is part of the ROHM BD71828 MFD device. For more details - see Documentation/devicetree/bindings/mfd/rohm,bd71828-pmic.yaml. + This module is part of the ROHM BD71828 and BD72720 MFD device. For more + details see Documentation/devicetree/bindings/mfd/rohm,bd71828-pmic.yaml + and Documentation/devicetree/bindings/mfd/rohm,bd72720-pmic.yaml =20 The LED controller is represented as a sub-node of the PMIC node on the = device - tree. + tree. This should be located under "leds" - node in PMIC node. =20 The device has two LED outputs referred as GRNLED and AMBLED in data-she= et. =20 --=20 2.51.1 --q1lGGyIWEu/v15kj Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEIx+f8wZb28fLKEhTeFA3/03aocUFAmkVnGIACgkQeFA3/03a ocVoEAf/aJS7bucIDhyz1TQUYRo2ROLBn2Dj0jdLYDgGRUvXoGvJh7ZGdhvI7Lq1 HOegX7f//Q67H3hDiRUGDKOhl1Ilm7hKdrIdfLmXq6GQAn0rlhxRpdrfVqUU/mmb a018tU4ca9isQya3prV9ntZY1qgdMZ/TOvbhs6ZBulO6lKMHrxMshdGQJrly0tPO TbZEfCgPVMYRh0RKVTo6NX+8t5AZ9HmDU/UoHk/bXOU65W7uS0fdG6kv/jHGaA0U H45VScgqk6dfDrMxFK0moJht4WQfMiqPaRbNBTPJ9gI0aB7uuM17t1gisrfkCtOR rKNdC5zEgmIyUiy00xRIserAu6oVZA== =+WGD -----END PGP SIGNATURE----- --q1lGGyIWEu/v15kj--