From: Adrien Grassein <adrien.grassein@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: broonie@kernel.org, jagan@amarulasolutions.com,
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 v2 0/7] Fix issues on pf8x00 driver
Date: Wed, 16 Dec 2020 00:56:32 +0100 [thread overview]
Message-ID: <20201215235639.31516-1-adrien.grassein@gmail.com> (raw)
Hello,
this patch set aims is to fix some issues contains in the pf8x00 driver.
Some issues are documentation ones, some others are in code.
These issues where found while developing another version of the same
driver. I prefer to share with you the patch for it.
I do these patches on the master branch of the linux-next repository.
1: regulator_name property is useless in documentation.
2: there is a missing documentation when we build the driver as a
module.
3: nxp,phase-shift documentation was not optimal.
4: nxp,ilim-ma is useless since another property does (nearly) the same.
5: Same than 4, in driver code.
6: It's better to use a linear_range to describe the voltage of bucks.
7: Fix several mistakes in the handle of nxp,phase-shift property.
Changes introduced in v2:
Some patches were mixed (and did not compile separatly);
Add path 7 for the handle of nxp,phase-shift property.
Adrien Grassein (7):
regulator: dt-bindings: remove useless properties
regulator: pf8x00: add a doc for the module
regulator: dt-bindings: pf8x00: fix nxp,phase-shift doc
regulator: dt-bindings: pf8x00: remove nxp,ilim-ma property
regulator: pf8x00: remove nxp,ilim-ma property
regulator: pf8x00: use linear range for buck 1-6
regulator: pf8x00: fix nxp,phase-shift
.../regulator/nxp,pf8x00-regulator.yaml | 46 +----
drivers/regulator/Kconfig | 4 +
drivers/regulator/pf8x00-regulator.c | 174 ++++++++----------
3 files changed, 81 insertions(+), 143 deletions(-)
--
2.20.1
next reply other threads:[~2020-12-16 0:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 23:56 Adrien Grassein [this message]
2020-12-15 23:56 ` [PATCH v2 1/7] regulator: dt-bindings: remove useless properties Adrien Grassein
2020-12-17 17:31 ` Jagan Teki
2020-12-17 23:49 ` Rob Herring
2020-12-15 23:56 ` [PATCH v2 2/7] regulator: pf8x00: add a doc for the module Adrien Grassein
2020-12-17 17:32 ` Jagan Teki
2020-12-15 23:56 ` [PATCH v2 3/7] regulator: dt-bindings: pf8x00: fix nxp,phase-shift doc Adrien Grassein
2020-12-17 17:37 ` Jagan Teki
2020-12-17 23:51 ` Rob Herring
2020-12-15 23:56 ` [PATCH v2 4/7] regulator: dt-bindings: pf8x00: remove nxp,ilim-ma property Adrien Grassein
2020-12-17 23:51 ` Rob Herring
2020-12-15 23:56 ` [PATCH v2 5/7] regulator: " Adrien Grassein
2020-12-15 23:56 ` [PATCH v2 6/7] regulator: pf8x00: use linear range for buck 1-6 Adrien Grassein
2020-12-15 23:56 ` [PATCH v2 7/7] regulator: pf8x00: fix nxp,phase-shift Adrien Grassein
2020-12-17 17:41 ` Jagan Teki
2020-12-17 18:38 ` 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=20201215235639.31516-1-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).