[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20201215235639.31516-5-adrien.grassein@gmail.com>
Date: Wed, 16 Dec 2020 00:56:36 +0100
From: Adrien Grassein <adrien.grassein@...il.com>
To: unlisted-recipients:; (no To-header on input)
Cc: broonie@...nel.org, jagan@...rulasolutions.com,
lgirdwood@...il.com, robh+dt@...nel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
troy.kisky@...ndarydevices.com,
Adrien Grassein <adrien.grassein@...il.com>
Subject: [PATCH v2 4/7] regulator: dt-bindings: pf8x00: remove nxp,ilim-ma property
This property seems useless because we can use the
regulator-max-microamp generic property to do the same
and using generic code.
The only things it changes is the default value. The original
code was using "2100" (mA) as default one, but I think we should
keep the value in the OTP memory as the default one. This value
is automatically loaded in the register by the chip.
Signed-off-by: Adrien Grassein <adrien.grassein@...il.com>
---
.../bindings/regulator/nxp,pf8x00-regulator.yaml | 13 -------------
1 file changed, 13 deletions(-)
diff --git a/Documentation/devicetree/bindings/regulator/nxp,pf8x00-regulator.yaml b/Documentation/devicetree/bindings/regulator/nxp,pf8x00-regulator.yaml
index 1da724c6e2ba..b6ea3b8eb811 100644
--- a/Documentation/devicetree/bindings/regulator/nxp,pf8x00-regulator.yaml
+++ b/Documentation/devicetree/bindings/regulator/nxp,pf8x00-regulator.yaml
@@ -45,19 +45,6 @@ properties:
Properties for single BUCK regulator.
properties:
- nxp,ilim-ma:
- $ref: "/schemas/types.yaml#/definitions/uint32"
- minimum: 2100
- maximum: 4500
- description:
- BUCK regulators current limit in mA.
-
- Listed current limits in mA are,
- 2100 (default)
- 2600
- 3000
- 4500
-
nxp,phase-shift:
$ref: "/schemas/types.yaml#/definitions/uint32"
minimum: 0
--
2.20.1
Powered by blists - more mailing lists