From: cy_huang <u0084500@gmail.com>
To: broonie@kernel.org, robh+dt@kernel.org
Cc: krzysztof.kozlowski@canonical.com, lgirdwood@gmail.com,
cy_huang@richtek.com, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: [PATCH v2 0/2] Add Richtek RT5190A PMIC support
Date: Wed, 9 Mar 2022 16:01:41 +0800 [thread overview]
Message-ID: <1646812903-32496-1-git-send-email-u0084500@gmail.com> (raw)
From: ChiYuan Huang <cy_huang@richtek.com>
This patch series add Richtek RT5190A PMIC support.
v2:
1. use standard bindings regulator-min/max-microvolt to replace
fixed-microvolt property
2. change dt-bindings sample node name from rt5190a@64 to pmic@64.
3. add dt-binding header to defin e the opmode mapping number.
4. refine 'richtek,mute-enable' description in dt-binding.
4. due to fixed-microvolt property removal, use of_regulator_match to get
the regulator init data.
5. fix checkpatch warning and error.
ChiYuan Huang (2):
dt-bindings: regulator: Add bindings for Richtek RT5190A PMIC
regulator: rt5190a: Add support for Richtek RT5190A PMIC
.../regulator/richtek,rt5190a-regulator.yaml | 141 ++++++
drivers/regulator/Kconfig | 10 +
drivers/regulator/Makefile | 1 +
drivers/regulator/rt5190a-regulator.c | 513 +++++++++++++++++++++
.../regulator/richtek,rt5190a-regulator.h | 15 +
5 files changed, 680 insertions(+)
create mode 100644 Documentation/devicetree/bindings/regulator/richtek,rt5190a-regulator.yaml
create mode 100644 drivers/regulator/rt5190a-regulator.c
create mode 100644 include/dt-bindings/regulator/richtek,rt5190a-regulator.h
--
2.7.4
next reply other threads:[~2022-03-09 8:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 8:01 cy_huang [this message]
2022-03-09 8:01 ` [PATCH v2 1/2] dt-bindings: regulator: Add bindings for Richtek RT5190A PMIC cy_huang
2022-03-09 9:08 ` Krzysztof Kozlowski
2022-03-09 8:01 ` [PATCH v2 2/2] regulator: rt5190a: Add support " cy_huang
2022-03-10 11:35 ` [PATCH v2 0/2] Add Richtek RT5190A PMIC support Mark Brown
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=1646812903-32496-1-git-send-email-u0084500@gmail.com \
--to=u0084500@gmail.com \
--cc=broonie@kernel.org \
--cc=cy_huang@richtek.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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).