Devicetree
 help / color / mirror / Atom feed
From: Svyatoslav Ryhel <clamor95@gmail.com>
To: 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>,
	Svyatoslav Ryhel <clamor95@gmail.com>, Milo Kim <milo.kim@ti.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: [PATCH v2 1/7] regulator: dt-bindings: ti,lp872x: Deprecate ti,dvs-gpio and ti,update-config
Date: Tue, 13 Oct 2026 21:14:11 +0300	[thread overview]
Message-ID: <20261013181417.492252-2-clamor95@gmail.com> (raw)
In-Reply-To: <20261013181417.492252-1-clamor95@gmail.com>

Mark ti,dvs-gpio as deprecated in favor of using dvs-gpio property. The
ti,dvs-gpio is not used in any of existing in kernel device trees anyway,
so this should not break any tree. Mark ti,update-config deprecated in
favor of using the presence of the ti,general-config property as a trigger
to update.

Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
---
 Documentation/devicetree/bindings/regulator/ti,lp872x.yaml | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/Documentation/devicetree/bindings/regulator/ti,lp872x.yaml b/Documentation/devicetree/bindings/regulator/ti,lp872x.yaml
index 8e74dbb3ae303..8216f1e3125d4 100644
--- a/Documentation/devicetree/bindings/regulator/ti,lp872x.yaml
+++ b/Documentation/devicetree/bindings/regulator/ti,lp872x.yaml
@@ -47,10 +47,12 @@ properties:
 
   ti,update-config:
     type: boolean
+    deprecated: true
     description: define it when LP872X_GENERAL_CFG register should be set
 
   ti,dvs-gpio:
     maxItems: 1
+    deprecated: true
     description: GPIO specifier for external DVS pin control of LP872x devices.
 
   ti,dvs-vsel:
@@ -67,6 +69,10 @@ properties:
     maxItems: 1
     description: GPIO specifier for EN pin control of LP872x devices.
 
+  dvs-gpios:
+    description: GPIO specifier for external DVS pin control.
+    maxItems: 1
+
   buck:
     type: object
     $ref: regulator.yaml#
-- 
2.53.0


  reply	other threads:[~2026-10-13 18:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13 18:14 [PATCH v2 0/7] lp872x: remove platform_data based probing and adjustments Svyatoslav Ryhel
2026-10-13 18:14 ` Svyatoslav Ryhel [this message]
2026-10-13 18:22   ` [PATCH v2 1/7] regulator: dt-bindings: ti,lp872x: Deprecate ti,dvs-gpio and ti,update-config sashiko-bot
2026-10-13 18:14 ` [PATCH v2 2/7] regulator: dt-bindings: ti,lp872x: Document input supplies Svyatoslav Ryhel
2026-10-13 18:14 ` [PATCH v2 3/7] regulator: lp872x: Fold driver header into driver file Svyatoslav Ryhel
2026-10-13 18:14 ` [PATCH v2 4/7] regulator: lp872x: Remove redundant regmap wrappers Svyatoslav Ryhel
2026-10-13 18:14 ` [PATCH v2 5/7] regulator: lp872x: Remove platform_data based probing Svyatoslav Ryhel
2026-10-13 18:27   ` sashiko-bot
2026-10-13 18:14 ` [PATCH v2 6/7] regulator: lp872x: Add support for input and regulator power supplies Svyatoslav Ryhel
2026-10-13 18:14 ` [PATCH v2 7/7] regulator: lp872x: Use macro to fill regulator descriptor Svyatoslav Ryhel

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=20261013181417.492252-2-clamor95@gmail.com \
    --to=clamor95@gmail.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=milo.kim@ti.com \
    --cc=robh@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