From: Peng Fan <peng.fan@nxp.com>

The Documentation/devicetree/bindings/regulator/regulator.yaml
already states in its description that regulator-suspend-microvolt
is deprecated, but the schema did not formally mark it as such.

Add the `deprecated: true` annotation to regulator-suspend-microvolt
so that this is enforced at the schema level.

Signed-off-by: Peng Fan <peng.fan@nxp.com>
---
 Documentation/devicetree/bindings/regulator/regulator.yaml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/devicetree/bindings/regulator/regulator.yaml b/Documentation/devicetree/bindings/regulator/regulator.yaml
index 77573bcb6b791e4f90837d70309d1f32331f098a..042e56396399f9aa92f72c891729837f92538fb5 100644
--- a/Documentation/devicetree/bindings/regulator/regulator.yaml
+++ b/Documentation/devicetree/bindings/regulator/regulator.yaml
@@ -274,6 +274,7 @@ patternProperties:
           suspend. This property is now deprecated, instead setting voltage
           for suspend mode via the API which regulator driver provides is
           recommended.
+        deprecated: true
 
       regulator-changeable-in-suspend:
         description: whether the default voltage and the regulator on/off

---
base-commit: 0f853ca2a798ead9d24d39cad99b0966815c582a
change-id: 20260119-regulator-binding-3750ddf8ae8b

Best regards,
-- 
Peng Fan <peng.fan@nxp.com>

On Mon, 19 Jan 2026 11:48:49 +0800, Peng Fan (OSS) wrote:
> The Documentation/devicetree/bindings/regulator/regulator.yaml
> already states in its description that regulator-suspend-microvolt
> is deprecated, but the schema did not formally mark it as such.
> 
> Add the `deprecated: true` annotation to regulator-suspend-microvolt
> so that this is enforced at the schema level.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/1] dt-bindings: regulator: mark regulator-suspend-microvolt as deprecated
      commit: 20c4701b75a3d6ce09d61e17125aefe77e7eb333

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark

Acked-by: Conor Dooley <conor.dooley@microchip.com>
pw-bot: not-applicable