From: "André Svensson" <andre.svensson@axis.com>
To: Support Opensource <support.opensource@diasemi.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Adam Ward <Adam.Ward.opensource@diasemi.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
kernel@axis.com, "Waqar Hameed" <waqar.hameed@axis.com>,
"André Svensson" <andre.svensson@axis.com>
Subject: [PATCH 1/2] regulator: dt-bindings: dlg,da9121: Add dlg,no-gpio-control
Date: Mon, 9 Mar 2026 16:52:35 +0100 [thread overview]
Message-ID: <20260309-no-gpio-control-v1-1-06d2365917c6@axis.com> (raw)
In-Reply-To: <20260309-no-gpio-control-v1-0-06d2365917c6@axis.com>
Add the optional boolean property dlg,no-gpio-control. When present, it
indicates that no DA91xx GPIO pins are configured/used with functions
RELOAD/DVC/EN, which can affect the output voltage control, regulator
mode control and enable signal control.
It is mutually exclusive with enable-gpios, regardless of whether the
referenced GPIO is connected to a GPIO pin or the IC_EN pin, since
enable-gpios allows the regulator to be controlled via an external
hardware signal.
Co-developed-by: Waqar Hameed <waqar.hameed@axis.com>
Signed-off-by: Waqar Hameed <waqar.hameed@axis.com>
Signed-off-by: André Svensson <andre.svensson@axis.com>
---
.../devicetree/bindings/regulator/dlg,da9121.yaml | 49 ++++++++++++++++++++++
1 file changed, 49 insertions(+)
diff --git a/Documentation/devicetree/bindings/regulator/dlg,da9121.yaml b/Documentation/devicetree/bindings/regulator/dlg,da9121.yaml
index 13b3f75f8e5e..ce76eb5b85bd 100644
--- a/Documentation/devicetree/bindings/regulator/dlg,da9121.yaml
+++ b/Documentation/devicetree/bindings/regulator/dlg,da9121.yaml
@@ -81,6 +81,14 @@ properties:
Specify the polling period, measured in milliseconds, between interrupt status
update checks. Range 1000-10000 ms.
+ dlg,no-gpio-control:
+ type: boolean
+ description: |
+ Available GPIO input pins of the regulator are strapped to fixed levels, therefore
+ GPIO configurable input functions, DVC/RELOAD/EN, cannot dynamically update BUCK
+ registers. GPIO pins connected as output pins are not required to be strapped to a
+ fixed level. Not allowed together with enable-gpios.
+
regulators:
type: object
additionalProperties: false
@@ -134,6 +142,17 @@ allOf:
properties:
buck2: false
+ - if:
+ required:
+ - dlg,no-gpio-control
+ then:
+ properties:
+ regulators:
+ patternProperties:
+ "^buck([1-2])$":
+ properties:
+ enable-gpios: false
+
additionalProperties: false
examples:
@@ -168,6 +187,36 @@ examples:
};
};
+ - |
+ #include <dt-bindings/interrupt-controller/irq.h>
+ #include <dt-bindings/regulator/dlg,da9121-regulator.h>
+ i2c {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ pmic@68 {
+ compatible = "dlg,da9121";
+ reg = <0x68>;
+
+ interrupt-parent = <&gpio6>;
+ interrupts = <11 IRQ_TYPE_LEVEL_LOW>;
+
+ dlg,irq-polling-delay-passive-ms = <2000>;
+ dlg,no-gpio-control;
+
+ regulators {
+ DA9121_BUCK: buck1 {
+ regulator-name = "BUCK1";
+ regulator-min-microvolt = <300000>;
+ regulator-max-microvolt = <1900000>;
+ regulator-min-microamp = <7000000>;
+ regulator-max-microamp = <20000000>;
+ regulator-boot-on;
+ regulator-initial-mode = <DA9121_BUCK_MODE_AUTO>;
+ };
+ };
+ };
+ };
+
- |
#include <dt-bindings/gpio/gpio.h>
#include <dt-bindings/interrupt-controller/irq.h>
--
2.43.0
next prev parent reply other threads:[~2026-03-09 15:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 15:52 [PATCH 0/2] Allow caching of buck registers when no GPIO input control is configured André Svensson
2026-03-09 15:52 ` André Svensson [this message]
2026-03-09 16:30 ` [PATCH 1/2] regulator: dt-bindings: dlg,da9121: Add dlg,no-gpio-control Mark Brown
2026-03-10 8:55 ` André Svensson
2026-03-09 15:52 ` [PATCH 2/2] regulator: da9121: Allow caching BUCK registers André Svensson
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=20260309-no-gpio-control-v1-1-06d2365917c6@axis.com \
--to=andre.svensson@axis.com \
--cc=Adam.Ward.opensource@diasemi.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@axis.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=support.opensource@diasemi.com \
--cc=waqar.hameed@axis.com \
/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®