From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mta0.migadu.com (out-25.mta0.migadu.com [91.218.175.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 8F263471CF5 for ; Wed, 2 Sep 2026 11:04:22 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.25 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788347065; cv=none; b=h2OztGLN8UyDc+TkFwG7sZKY84DQjhfeQ2iVJqFnQo74pGJ9k5Xf/NbgbjP0cJz3f8d0oLXh13nRxWdW9wCXfQnrjfdLw3lXYEagYOHQ0GNOkPS5fFRzt2WEtP0p8zDdmTwkOjZ5ET4tFALvhR+LDXwUQm3euJnE3MMebh1c9Uo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788347065; c=relaxed/simple; bh=mNzjoXbA5ma/7li2AYSLeMuio74ySSjVxw8OjFqvkhQ=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=SpnuYXwRpuAIIuzMnBLife9+g4agNBIZirS98VC7u/5hU1xRO9dBcVmM9ahp+vG+7QAza2vDRoDzHv8yjEHued/u+Wg1c9E/zBWfiChIf9vfOwO6oOz/32iRQ/RMPi4kqo6/zn0gp8vIokRPI5orsJ5dCBK6xgAtlMCF+MM+KOg= 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=F9mPjNyu; arc=none smtp.client-ip=91.218.175.25 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="F9mPjNyu" X-Envelope-To: devicetree@vger.kernel.org DKIM-Signature: a=rsa-sha256; bh=mNzjoXbA5ma/7li2AYSLeMuio74ySSjVxw8OjFqvkhQ=; c=simple/simple; d=linux.dev; h=from:to:subject:date:message-id:mime-version:content-type; s=key1; t=1788347060; v=1; x=1788951860; b=F9mPjNyu18FrAiNFrTp1fXr2L1/mNtsN52L4ClStpDBM6p6uXzJFy543Nrp42NK7A97dkpi8 89BKU3ZIwjWa32A/ZsP8gUVAvBw6ICnymigVn2A7YntpkHYLn+mERQ2nU7n9QO23B7/stdwCsAu Jh7UlJw3L4xTkQiH0DkwGqGY= X-Envelope-To: devicetree@vger.kernel.org Received: by mta12.migadu.com with ESMTPS id 534f7718f5f0019a; Wed, 02 Sep 2026 11:04:20 +0000 X-Mizu-Trace-ID: 534f7718f5f0019a X-Migadu-Flow: FLOW_OUT Date: Wed, 2 Sep 2026 14:04:15 +0300 From: Matti Vaittinen To: Matti Vaittinen , Matti Vaittinen , Matti Vaittinen Cc: Lee Jones , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Liam Girdwood , Mark Brown , Matti Vaittinen , Stephen Boyd , Brian Masney , Jerome Brunet , Linus Walleij , Bartosz Golaszewski , Alexandre Belloni , Michael Walle , mfd@lists.linux.dev, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org, linux-gpio@vger.kernel.org, linux-rtc@vger.kernel.org Subject: [PATCH v3 03/10] dt-bindings: regulator: ROHM BD73800 regulators Message-ID: Reply-To: Matti Vaittinen References: Precedence: bulk X-Mailing-List: devicetree@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="x6SObUgyw3EOWLBl" Content-Disposition: inline In-Reply-To: --x6SObUgyw3EOWLBl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable =46rom: Matti Vaittinen Add bindings for the BUCKs and LDOs on ROHM BD73800. The PMIC state specific voltages can be set in same fashion as with a few other ROHM PMICs (for example with BD718[15,28,37,47,50,79]). Same properties are recycled :) The LDOs 1 and 4 can use different voltage ranges depending on the OTP configuration. Signed-off-by: Matti Vaittinen --- Revision history: v3: - No changes v1 =3D> v2: - Description of the state specific voltages moved to own file and referenced from it (because multiple PMIC bindings used them). The dt checker's documentation reference checker warns about the link to the MFD binding - which will be introduced in next commit. These commits have kind of a chicken and egg issue as MFD is referencing regulator properties introduced in this patch. I could squash these but IMO, this is clearer for the reviewers. AFAICS, Both MFD and regulator subsystems tend to be busy. I could also split adding the MFD comment reference to own patch which would be after the patch adding the MFD binding, but having own patch for just adding the comment is a bit meh. So, I decided to live with the broken doc-link between these two patches. --- .../regulator/rohm,bd73800-regulator.yaml | 99 +++++++++++++++++++ 1 file changed, 99 insertions(+) create mode 100644 Documentation/devicetree/bindings/regulator/rohm,bd7380= 0-regulator.yaml diff --git a/Documentation/devicetree/bindings/regulator/rohm,bd73800-regul= ator.yaml b/Documentation/devicetree/bindings/regulator/rohm,bd73800-regula= tor.yaml new file mode 100644 index 000000000000..2db4585272c5 --- /dev/null +++ b/Documentation/devicetree/bindings/regulator/rohm,bd73800-regulator.ya= ml @@ -0,0 +1,99 @@ +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/regulator/rohm,bd73800-regulator.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: ROHM BD73800 Power Management Integrated Circuit regulators + +maintainers: + - Matti Vaittinen + +description: | + This module is part of the ROHM BD73800 MFD device. For more details + see Documentation/devicetree/bindings/mfd/rohm,bd73800-pmic.yaml. + + The regulator controller is represented as a sub-node of the PMIC node + on the device tree. + + Regulator nodes should be named to buck and ldo. + The valid names for BD73800 regulator nodes are + buck1, buck2, buck3, buck4, buck5, buck6, buck7, buck8 + ldo1, ldo2, ldo3, ldo4 + +patternProperties: + "^buck[1-8]$": + type: object + description: + Properties for a single BUCK regulator. + allOf: + - $ref: regulator.yaml# + - $ref: rohm,pmic-states.yaml# + + properties: + regulator-name: + pattern: "^buck[1-8]$" + description: + should be "buck1", ..., "buck8" + + rohm,dvs-run-voltage: + minimum: 0 + maximum: 3500000 + + rohm,dvs-idle-voltage: + minimum: 0 + maximum: 3500000 + + rohm,dvs-suspend-voltage: + minimum: 0 + maximum: 3500000 + + # BUCKs 1,2,3,4 and 8 support voltages 0.5 - 1.3V + # BUCK 5 supports voltages 0.3 - 1.3V + # BUCKs 6 and 7 support voltages 1.5 - 3.5V + + required: + - regulator-name + + unevaluatedProperties: false + + "^ldo[1-4]$": + type: object + description: + Properties for single LDO regulator. + allOf: + - $ref: regulator.yaml# + - $ref: rohm,pmic-states.yaml# + + properties: + regulator-name: + pattern: "^ldo[1-4]$" + description: + should be "ldo1", ..., "ldo4" + + rohm,dvs-run-voltage: + minimum: 0 + maximum: 1 + + rohm,dvs-idle-voltage: + minimum: 0 + maximum: 1 + + rohm,dvs-suspend-voltage: + minimum: 0 + maximum: 1 + + rohm,ldo-range-high: + type: boolean + description: + LDO1 and LDO3 voltage ranges can be "high" or "low" depending on + OTP. Indicate that the "high" range is used. See comment below + for voltages. + + # LDOs 2 and 4 support voltages 0.75 - 3.3V + # LDOs 1 and 3 may support different ranges depending on OTP. + # either 0.6 - 1.8V or 0.75 - 3.3V. + + unevaluatedProperties: false + +additionalProperties: false --=20 2.55.0 --x6SObUgyw3EOWLBl Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEIx+f8wZb28fLKEhTeFA3/03aocUFAmqYAq8ACgkQeFA3/03a ocW1TwgAnEvX9XY08LsxpPRBIyMMiJ6cJFUojWYQgONE3gFsR9xIee+FllPTVtsH BPg0JUJrtK47U2vdwyAhqMS5qBOteBmF7J2VnFAmxMQ5Mx+qfQ3kZGU/9K/MiiuD f456ylRb0pp0WxLlObw4dxWWmguS2FhlhR6kY0/MlxDULPaa5B24rwPJqIi5f3X2 drCR7nsnDwgqegcaq7uJk2OdvxLWULK5A8wtZV6Ulb8qEFIcs/K2MqGF9qF+4ggD 7px3jtQgIXkj2TJ1qwnOyGtkWcmjjtAxP0eH3yTZm4KSH90IVy4FXT5SRTfK+JMS UUnQa28MWeltdyjSM3/qg9y5s8p3WA== =KO5n -----END PGP SIGNATURE----- --x6SObUgyw3EOWLBl--