From: Adrien Grassein <adrien.grassein@gmail.com>
To: broonie@kernel.org, jagan@amarulasolutions.com
Cc: lgirdwood@gmail.com, robh+dt@kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
troy.kisky@boundarydevices.com,
Adrien Grassein <adrien.grassein@gmail.com>
Subject: [PATCH 4/6] regulator: dt-bindings: pf8x00: remove nxp,ilim-ma property
Date: Tue, 15 Dec 2020 21:48:56 +0100 [thread overview]
Message-ID: <20201215204858.8186-5-adrien.grassein@gmail.com> (raw)
In-Reply-To: <20201215204858.8186-1-adrien.grassein@gmail.com>
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, 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@gmail.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
next prev parent reply other threads:[~2020-12-15 20:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 20:48 [PATCH 0/6] Fix issues on pf8x00 driver Adrien Grassein
2020-12-15 20:48 ` [PATCH 1/6] regulator: dt-bindings: remove useless properties Adrien Grassein
2020-12-15 20:48 ` [PATCH 2/6] regulator: pf8x00: add a doc for the module Adrien Grassein
2020-12-15 20:48 ` [PATCH 3/6] regulator: dt-bindings: pf8x00: fix nxp,phase-shift doc Adrien Grassein
2020-12-15 21:06 ` Jagan Teki
2020-12-15 21:09 ` Adrien Grassein
2020-12-15 20:48 ` Adrien Grassein [this message]
2020-12-15 20:48 ` [PATCH 5/6] regulator: pf8x00: remove nxp,ilim-ma property Adrien Grassein
2020-12-15 20:48 ` [PATCH 6/6] regulator: pf8x00: use linear range for buck 1-6 Adrien Grassein
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=20201215204858.8186-5-adrien.grassein@gmail.com \
--to=adrien.grassein@gmail.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jagan@amarulasolutions.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=troy.kisky@boundarydevices.com \
/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;
as well as URLs for NNTP newsgroup(s).