From nobody Mon Dec 1 22:37:30 2025 Received: from out-180.mta0.migadu.com (out-180.mta0.migadu.com [91.218.175.180]) (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 8557C32B9A6 for ; Thu, 27 Nov 2025 11:18:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.180 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764242312; cv=none; b=Memb8Cr6p7YIv2WZO0OE/BWroz5NSjX3uves6BvOQggNKB77BxfetWI4Qs9ZbFmqnM9ny5qIEvof2JS33V+X6XnzE7EPb1d7d1wnjqXOB7uWoJRmuk4CKNcF63xOpWdIcEyN/m2O2Xi3MCodEMinTZUBlhajmH3s8JSdfv+H0GE= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764242312; c=relaxed/simple; bh=mfSWS11rlwcpuN9mxpsXcx2t4ELbyGih+doj2aMJ6lE=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=rIn10HIGb8h218IhXl0iCZanjpER4iWKsi1K266YWBC2z79Dpue78LthImMdWjXqlUdKZep0ZSoyivSZNBJwhP0KarPUNsxuQo5F/3ehDYc/2nm5Vul2CtBktYTCswPsyNX3R9THvXlFaKB3jXFA56WL2gqGxvh2RG+gRLTZ3vI= 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=rGZnkAf6; arc=none smtp.client-ip=91.218.175.180 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="rGZnkAf6" Date: Thu, 27 Nov 2025 13:18:21 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1764242308; 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=zPf5UP0J6w/xMXhyK5yfcDOV4EwFbl4ijzFjM6fjGFQ=; b=rGZnkAf6Err3PUoQZd0aUC5RqoogQjhj3OM+p+fZeReFRG+ppXTNgD/4Wo/IfnYNrQBTqm J5A33u99IUXBIwKX9CatMPyetnnN9yRmC0wWXOhobBpNn0PdAqR6CSUQATyihiHMhH7Ppn 9aYW8wWDDKVm/rNL9abPohgJQsqjwQY= 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 v6 06/17] dt-bindings: leds: bd72720: Add BD72720 Message-ID: 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="XZ/EJQ6bdGOm290w" Content-Disposition: inline In-Reply-To: X-Migadu-Flow: FLOW_OUT --XZ/EJQ6bdGOm290w 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.52.0 --XZ/EJQ6bdGOm290w Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEIx+f8wZb28fLKEhTeFA3/03aocUFAmkoM30ACgkQeFA3/03a ocU50AgAuJVXDy/4XUGcCiADn1PUuVsJBca5DVVdAuChFYSJYE0ZYrhHteT4JG0/ VPtBi8if5VaDvUpFAsgwqYJKohmymvf4x7Vw3TngaekcYKlZ9XmyxNlYu7D6ncRQ Mc2gbTQBLlpR/SOi5ou5Bc9rZIqQoDUDT8MwIHMLX8Awihwp7XO9DjKCA3ajoBqV xH9AG7ItQ4MxnNQePczx2ZC5wWN36DSmHMqDqSunvafSKsXkH+g4sYgNSA1sz0NI t9XKmjaJQY9ZrJV270J2EiZ23oskYRvZEy3WjlGkFDQlaq5dbn190zGL1W1ImspR tcuWhn26folzQQRqRNIGb2LG2GkBCA== =v1LQ -----END PGP SIGNATURE----- --XZ/EJQ6bdGOm290w--