From: Matti Vaittinen <matti.vaittinen@linux.dev>
To: Matti Vaittinen <mazziesaccount@gmail.com>,
Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
Matti Vaittinen <matti.vaittinen@linux.dev>
Cc: Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Matti Vaittinen <mazziesaccount@gmail.com>,
Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney+clk@redhat.com>,
Jerome Brunet <jbrunet+clk@baylibre.com>,
Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Michael Walle <mwalle@kernel.org>,
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,
Sverdlin@mva-rohm, Alexander <alexander.sverdlin@siemens.com>
Subject: [PATCH v4 01/10] dt-bindings: mfd: common ROHM PMIC properties
Date: Wed, 16 Sep 2026 09:06:05 +0300 [thread overview]
Message-ID: <114ad461ace2f76e6a04a482d3c31ee0b372e672.1789538455.git.mazziesaccount@gmail.com> (raw)
In-Reply-To: <cover.1789538455.git.mazziesaccount@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 5032 bytes --]
From: Matti Vaittinen <mazziesaccount@gmail.com>
ROHM PMICs keep having similar functionalities from one generation to the
next. Keeping the device-trees describing these functionalities similar
helps users because:
1. They can re-use existing device-tree properties when switching from
one project, using a ROHM PMIC, to next project using newer
variant.
2. The users can find and re-use examples from old projects - even if
they never worked with ROHM PMICs before.
Similarly, introducing new and different properties for same
functionality previous variant had, will be adding confusion.
Sometimes the existing properties aren't 100% what reviewers would
prefer. When issues are minor or just cosmetic, changing the existing
properties is not feasible. Reviewers can't be expected to know which
properties are new, and which are existing - and this can lead to
unnecessary review discussion wasting time and energy from everyone.
Adding a common file for re-used ROHM PMIC properties should make it
clearly visible that a property is re-used, when a new PMIC binding
refers to this file instead of (re-)describing all the existing
bindings. This will also help keeping the common properties identical
across the variants.
Add new file listing commonly used ROHM PMIC properties.
Signed-off-by: Matti Vaittinen <mazziesaccount@gmail.com>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
Reviewed-by: Linus Walleij <linusw@kernel.org>
---
Revision history:
v3 => :
- No changes
v2:
- New patch
---
.../bindings/mfd/rohm,pmic-pins.yaml | 72 +++++++++++++++++++
1 file changed, 72 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mfd/rohm,pmic-pins.yaml
diff --git a/Documentation/devicetree/bindings/mfd/rohm,pmic-pins.yaml b/Documentation/devicetree/bindings/mfd/rohm,pmic-pins.yaml
new file mode 100644
index 000000000000..0d1082804f5a
--- /dev/null
+++ b/Documentation/devicetree/bindings/mfd/rohm,pmic-pins.yaml
@@ -0,0 +1,72 @@
+# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/mfd/rohm,pmic-pins.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: ROHM PMICs' OTP configured pin descriptions
+
+maintainers:
+ - Matti Vaittinen <mazziesaccount@gmail.com>
+
+description:
+ Collection of properties which are commonly used to describe various
+ ROHM PMIC's pins.
+
+properties:
+ rohm,clkout-open-drain:
+ description: clk32kout mode. Set to 1 for "open-drain" or 0 for "cmos"
+ a.k.a "push-pull".
+ $ref: /schemas/types.yaml#/definitions/uint32
+ maximum: 1
+
+ rohm,pin-clkout:
+ $ref: /schemas/types.yaml#/definitions/string
+ description:
+ The IC has different OTP options to use clkout-pin for different
+ purposes. Set this property to indicate the OTP variant.
+
+ Many of the ROHM ICs have pins, which function can be defined in
+ OTP. Some of them provide no means to detect the pin configuration
+ at run-time, leaving software unaware of which features the IC
+ really has. These properties can be used to inform which pins
+ provide which functionality. IOW, these properties aren't used to
+ configure pin, they are used to tell what functionality pins on
+ this specific IC have.
+
+ # Supported functionalities depend on the exact IC model. Following
+ # values are already defined: gpi, gpo.
+ # Please, re-use them when adding new ICs.
+
+ rohm,pin-fault_b:
+ $ref: /schemas/types.yaml#/definitions/string
+ description:
+ The IC has different OTP options to use fault_b-pin for different
+ purposes. Set this property to indicate the OTP variant.
+
+ # Supported functionalities depend on the exact IC model. Following
+ # values are already defined: gpi, gpo, faultb, readyind, pwrseq.
+ # Please, re-use them when adding new ICs.
+
+patternProperties:
+ "^rohm,pin-dvs[0-1]$":
+ $ref: /schemas/types.yaml#/definitions/string
+ description:
+ The IC has different OTP options to use dvs<X>-pins for different
+ purposes. Set this property to indicate the OTP variant.
+ # Supported functionalities depend on the exact IC model. Following
+ # values are already defined: dvs-input, gpi, gpo, pwrseq.
+ # Please, re-use them when adding new ICs.
+
+ "^rohm,pin-exten([0-1])?$":
+ $ref: /schemas/types.yaml#/definitions/string
+ description:
+ The IC has an OTP option to use exten -pin(s) for different purposes.
+ Set this property to indicate the OTP variant.
+ # Supported functionalities depend on the exact IC model. Following
+ # values are already defined: gpi, gpo, pwrseq.
+ # Please, re-use them when adding new ICs.
+
+# The schema is expected to be reference by IC schemas, which may introduce
+# other properties that must be allowed.
+additionalProperties: true
--
2.55.0
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-09-16 6:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 6:04 [PATCH v4 00/10] Support ROHM BD73800 Matti Vaittinen
2026-09-16 6:06 ` Matti Vaittinen [this message]
2026-09-16 6:07 ` [PATCH v4 02/10] dt-bindings: rohm,bd*: Ref common ROHM bindings Matti Vaittinen
2026-09-16 6:08 ` [PATCH v4 03/10] dt-bindings: regulator: ROHM BD73800 regulators Matti Vaittinen
2026-09-16 6:08 ` [PATCH v4 04/10] dt-bindings: mfd: ROHM BD73800 PMIC Matti Vaittinen
2026-09-16 6:09 ` [PATCH v4 05/10] mfd: Support for ROHM BD73800 PMIC core Matti Vaittinen
2026-09-16 6:09 ` [PATCH v4 06/10] rtc: bd70528: Support RTC on ROHM BD73800 Matti Vaittinen
2026-09-16 6:10 ` [PATCH v4 07/10] regulator: bd71828: Support " Matti Vaittinen
2026-09-16 6:11 ` [PATCH v4 08/10] clk: bd718x7: " Matti Vaittinen
2026-09-16 6:12 ` [PATCH v4 09/10] gpio: bd73800: Support ROHM BD73800 PMIC GPIOs Matti Vaittinen
2026-09-16 17:31 ` Linus Walleij
2026-09-17 4:47 ` Matti Vaittinen
2026-09-16 6:12 ` [PATCH v4 10/10] MAINTAINERS: Add ROHM BD73800 PMIC files Matti Vaittinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=114ad461ace2f76e6a04a482d3c31ee0b372e672.1789538455.git.mazziesaccount@gmail.com \
--to=matti.vaittinen@linux.dev \
--cc=Sverdlin@mva-rohm \
--cc=alexander.sverdlin@siemens.com \
--cc=alexandre.belloni@bootlin.com \
--cc=bmasney+clk@redhat.com \
--cc=brgl@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet+clk@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linusw@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.com \
--cc=mfd@lists.linux.dev \
--cc=mwalle@kernel.org \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®