From: Lee Jones <lee@kernel.org>
To: lgirdwood@gmail.com, broonie@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, aaro.koskinen@iki.fi,
andreas@kemnade.info, khilman@baylibre.com, rogerq@kernel.org,
tony@atomide.com, lee@kernel.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Shree Ramamoorthy <s-ramamoorthy@ti.com>
Cc: m-leonard@ti.com, praneeth@ti.com
Subject: Re: [PATCH v5 0/5] Add TI TPS65214 & TPS65215 PMIC MFD Driver Support
Date: Tue, 11 Feb 2025 15:02:37 +0000 [thread overview]
Message-ID: <173928615760.2233464.12306998726512431222.b4-ty@kernel.org> (raw)
In-Reply-To: <20250206173725.386720-1-s-ramamoorthy@ti.com>
On Thu, 06 Feb 2025 11:37:20 -0600, Shree Ramamoorthy wrote:
> TPS65214 and TPS65215 are Power Management Integrated Circuits (PMICs) that
> have significant register map overlap with TPS65219 and each other. The
> series introduces the 2 new PMICs and restructures the existing driver to
> support multiple devices.
>
> - TPS65214, TPS65215, and TPS65219 each have 3 Buck regulators
> - TPS65214 has 2 LDOS and 1 GPO, whereas TPS65219 has 4 LDOs and 2 GPOs.
> - TPS65214's LDO1 maps to TPS65219's LDO3.
> - A key difference between TPS65215 & TPS65214 are the LDO current and
> voltage output ranges and the configurable options available.
> - TPS65215 has 2 LDOs, whereas TPS65219 has 4 LDOs.
> - TPS65215's LDO2 maps to TPS65219's LDO3.
> - TPS65215 has 1 GPO, whereas TPS65219 has 2 GPOs.
>
> [...]
Applied, thanks!
[1/5] regulator: dt-bindings: Add TI TPS65215 PMIC bindings
commit: 85e7aef57a9e057545017d55b02073e3c4756b2c
[2/5] regulator: dt-bindings: Add TI TPS65214 PMIC bindings
commit: 34beb3c87cbb8747f521db5cf1b2a608833f3967
[3/5] mfd: tps65219: Remove regmap_read check
commit: 5342c8a9e04fc05f485a3886605b803a5180bd64
[4/5] mfd: tps65219: Add support for TI TPS65215 PMIC
commit: ebcbd21550853b16f307d7da8c846b862e138a98
[5/5] mfd: tps65219: Add support for TI TPS65214 PMIC
commit: c9878d8d9ac2ecfadfa4fa3543730026c66ad843
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2025-02-11 15:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 17:37 [PATCH v5 0/5] Add TI TPS65214 & TPS65215 PMIC MFD Driver Support Shree Ramamoorthy
2025-02-06 17:37 ` [PATCH v5 1/5] regulator: dt-bindings: Add TI TPS65215 PMIC bindings Shree Ramamoorthy
2025-02-06 17:37 ` [PATCH v5 2/5] regulator: dt-bindings: Add TI TPS65214 " Shree Ramamoorthy
2025-02-10 10:13 ` Krzysztof Kozlowski
2025-02-06 17:37 ` [PATCH v5 3/5] mfd: tps65219: Remove regmap_read check Shree Ramamoorthy
2025-02-06 17:37 ` [PATCH v5 4/5] mfd: tps65219: Add support for TI TPS65215 PMIC Shree Ramamoorthy
2025-02-06 17:37 ` [PATCH v5 5/5] mfd: tps65219: Add support for TI TPS65214 PMIC Shree Ramamoorthy
2025-02-11 15:02 ` Lee Jones [this message]
2025-03-05 21:09 ` [PATCH v5 0/5] Add TI TPS65214 & TPS65215 PMIC MFD Driver Support Shree Ramamoorthy
2025-03-06 7:26 ` Krzysztof Kozlowski
2025-03-06 22:56 ` Shree Ramamoorthy
2025-03-26 16:42 ` Kory Maincent
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=173928615760.2233464.12306998726512431222.b4-ty@kernel.org \
--to=lee@kernel.org \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=m-leonard@ti.com \
--cc=praneeth@ti.com \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=s-ramamoorthy@ti.com \
--cc=tony@atomide.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