devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrien Grassein <adrien.grassein@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: lgirdwood@gmail.com, broonie@kernel.org, robh+dt@kernel.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	troy.kisky@boundarydevices.com, gary.bisson@boundarydevices.com,
	Adrien Grassein <adrien.grassein@gmail.com>
Subject: [PATCH v3 0/2] Add support of nxp pf8x00 regulator
Date: Mon, 14 Dec 2020 23:58:49 +0100	[thread overview]
Message-ID: <20201214225851.23342-1-adrien.grassein@gmail.com> (raw)

Hello,

this set of patch intends to add the support of the pf8x00 PMIC
regulators. This family of PMIC contains 12 regulators (7 bucks
converters, 4 LDO, 1 RTC supply). All these 12 regulators are
configurable via an OTP memory and by i2c at runtime for some
specific properties.

1: Adds the dt-binding corresponding to the new driver;
2: Adds the driver itself. 

This is th 3rd version of the patch set. In this version I fixed:
  - Bad default values were described in the description;
  - The configuration is now done at parsing time;
  - The code doesn't attempt to parse the regulator properties;
  - Remove the unnecessary new "nxp,illim-microamp" property;
  - Use the "regulator-max-microamp" of the regulator instead;
  - Cut the code in multiple function to obtain a better readability.
  - Rework some code part;

Thanks,

Adrien Grassein (2):
  dt-bindings: regulator: add pf8x00 PMIC
  regulator: pf8x00: add support of nxp pf8x00 regulator

 .../regulator/nxp,pf8x00-regulator.yaml       | 220 +++++
 MAINTAINERS                                   |   7 +
 drivers/regulator/Kconfig                     |  12 +
 drivers/regulator/Makefile                    |   1 +
 drivers/regulator/pf8x00-regulator.c          | 798 ++++++++++++++++++
 5 files changed, 1038 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/regulator/nxp,pf8x00-regulator.yaml
 create mode 100644 drivers/regulator/pf8x00-regulator.c

-- 
2.20.1


             reply	other threads:[~2020-12-14 23:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-14 22:58 Adrien Grassein [this message]
2020-12-14 22:58 ` [PATCH v3 1/2] dt-bindings: regulator: add pf8x00 PMIC Adrien Grassein
2020-12-15 14:26   ` Rob Herring
2020-12-15 15:00   ` Rob Herring
2020-12-14 22:58 ` [PATCH v3 2/2] regulator: pf8x00: add support of nxp pf8x00 regulator Adrien Grassein
2020-12-15 13:06 ` [PATCH v3 0/2] Add " Mark Brown
2020-12-15 13:14   ` Adrien Grassein
2020-12-15 13:20     ` Fabio Estevam
2020-12-15 13:24       ` Mark Brown
2020-12-15 13:33         ` Adrien Grassein
2020-12-15 20:17   ` Jagan Teki

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=20201214225851.23342-1-adrien.grassein@gmail.com \
    --to=adrien.grassein@gmail.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gary.bisson@boundarydevices.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).