From: Alexander Shiyan <eagle.alexander923@gmail.com>
To: devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, 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>,
Heiko Stuebner <heiko@sntech.de>,
Alexander Shiyan <eagle.alexander923@gmail.com>
Subject: [PATCH] dt-bindings: regulator: fcs,fan53555: Remove vsel-gpios property
Date: Mon, 27 Apr 2026 14:54:43 +0300 [thread overview]
Message-ID: <20260427115443.3224840-1-eagle.alexander923@gmail.com> (raw)
The vsel-gpios property is currently documented in the binding but
is not used by the driver. The FAN53555 family of regulators supports
two voltage selector registers (VSEL0/VSEL1), and the selection between
them is intended to be controlled by an external hardware pin (VSEL).
However, the driver does not support dynamic toggling of this pin via
a GPIO, it only uses the fcs,suspend-voltage-selector property to
statically assign which register is used for runtime voltage and which
for suspend voltage.
Remove the vsel-gpios property from the binding to prevent incorrect DT
usage and to reflect the actual hardware description supported by the
driver.
Signed-off-by: Alexander Shiyan <eagle.alexander923@gmail.com>
---
.../devicetree/bindings/regulator/fcs,fan53555.yaml | 5 -----
1 file changed, 5 deletions(-)
diff --git a/Documentation/devicetree/bindings/regulator/fcs,fan53555.yaml b/Documentation/devicetree/bindings/regulator/fcs,fan53555.yaml
index 69bae90fc4b2..7f3b74ccf8db 100644
--- a/Documentation/devicetree/bindings/regulator/fcs,fan53555.yaml
+++ b/Documentation/devicetree/bindings/regulator/fcs,fan53555.yaml
@@ -43,11 +43,6 @@ properties:
vin-supply:
description: Supply for the vin pin
- vsel-gpios:
- description: Voltage Select. When this pin is LOW, VOUT is set by the
- VSEL0 register. When this pin is HIGH, VOUT is set by the VSEL1 register.
- maxItems: 1
-
required:
- compatible
- reg
--
2.52.0
reply other threads:[~2026-04-27 11:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260427115443.3224840-1-eagle.alexander923@gmail.com \
--to=eagle.alexander923@gmail.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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