[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210108225006.153700-4-adrien.grassein@gmail.com>
Date: Fri, 8 Jan 2021 23:50:03 +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,
Adrien Grassein <adrien.grassein@...il.com>,
Rob Herring <robh@...nel.org>
Subject: [PATCH v3 3/6] 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>
Reviewed-by: Rob Herring <robh@...nel.org>
---
.../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 095cfdae7b67..05d5e9a2219c 100644
--- a/Documentation/devicetree/bindings/regulator/nxp,pf8x00-regulator.yaml
+++ b/Documentation/devicetree/bindings/regulator/nxp,pf8x00-regulator.yaml
@@ -58,19 +58,6 @@ properties:
description:
should be "buck1", ..., "buck7"
- 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"
default: 0
--
2.25.1
Powered by blists - more mailing lists