From: Shree Ramamoorthy <s-ramamoorthy@ti.com>
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>,
<jerome.neanne@baylibre.com>, <linux-omap@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>
Cc: <m-leonard@ti.com>, <praneeth@ti.com>, <christophe.jaillet@wanadoo.fr>
Subject: [PATCH v2 0/7] Add TI TPS65215 PMIC Regulator Support
Date: Fri, 3 Jan 2025 17:04:39 -0600 [thread overview]
Message-ID: <20250103230446.197597-1-s-ramamoorthy@ti.com> (raw)
TPS65215 is a Power Management Integrated Circuit (PMIC) that has
significant register map overlap with TPS65219. The series introduces
TPS65215 and restructures the existing driver to support multiple devices.
This follow-up series is dependent on the TPS65215 MFD Driver Series:
Commit c3cc37e8d23d ("mfd: tps65215: Add support for TI TPS65215 PMIC")
Commit 5f0f36835b90 ("mfd: tps65215: Remove regmap_read check")
TPS65219 Cleanup Series:
GPIO: https://lore.kernel.org/all/20241217204755.1011731-1-s-ramamoorthy@ti.com/
MFD: https://lore.kernel.org/all/20241217204935.1012106-1-s-ramamoorthy@ti.com/
Reg: https://lore.kernel.org/all/20241217204526.1010989-1-s-ramamoorthy@ti.com/
- Both TPS65215 and TPS65219 have 3 Buck regulators.
- TPS65215 has 2 LDOs, whereas TPS65219 has 4 LDOs.
- TPS65215 and TPS65219's LDO1 are the same.
- TPS65215's LDO2 maps to TPS65219's LDO3.
- TPS65215 has 1 GPO, whereas TPS65219 has 2 GPOs.
- The remaining features are the same.
TPS65215 TRM: https://www.ti.com/lit/pdf/slvucw5/
AM62L + TPS65215 Test Logs:
https://gist.github.com/ramamoorthyhs/7560eca6110fafc77b51894fa2c0fd22
---
Change Log:
v1 -> v2:
- have any PMIC lists be in alpha-numeric order: TPS65215, then TPS65219
- Add driver prefix to chip_data struct
- Have probe() helper functions use dev_err_probe instead of dev_err() to
log the error code in a human readable format & combined with return, it
saves a few LoC since { } can be removed.
- Add error handling of 'irq_data' in probe() as previously done.
---
Shree Ramamoorthy (7):
regulator: dt-bindings: Add TI TPS65215 PMIC bindings
regulator: tps65215: Update function & struct names
regulator: tps65215: Update IRQ structs to include TPS65215
regulator: tps65215: Add chip_data struct for multi-PMIC support
regulator: tps65215: Update platform_device_id table
regulator: tps65215: Define probe() helper functions
regulator: tps65215: Restructure probe() for multi-PMIC support
.../bindings/regulator/ti,tps65219.yaml | 9 +-
drivers/regulator/Kconfig | 7 +-
drivers/regulator/tps65219-regulator.c | 217 +++++++++++++-----
3 files changed, 177 insertions(+), 56 deletions(-)
--
2.34.1
next reply other threads:[~2025-01-03 23:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 23:04 Shree Ramamoorthy [this message]
2025-01-03 23:04 ` [PATCH v2 1/7] regulator: dt-bindings: Add TI TPS65215 PMIC bindings Shree Ramamoorthy
2025-01-04 10:13 ` Krzysztof Kozlowski
2025-01-06 19:50 ` Shree Ramamoorthy
2025-01-03 23:04 ` [PATCH v2 2/7] regulator: tps65215: Update function & struct names Shree Ramamoorthy
2025-01-04 8:38 ` kernel test robot
2025-01-04 10:37 ` kernel test robot
2025-01-03 23:04 ` [PATCH v2 3/7] regulator: tps65215: Update IRQ structs to include TPS65215 Shree Ramamoorthy
2025-01-03 23:04 ` [PATCH v2 4/7] regulator: tps65215: Add chip_data struct for multi-PMIC support Shree Ramamoorthy
2025-01-04 9:53 ` kernel test robot
2025-01-03 23:04 ` [PATCH v2 5/7] regulator: tps65215: Update platform_device_id table Shree Ramamoorthy
2025-01-04 10:14 ` Krzysztof Kozlowski
2025-01-07 22:15 ` Shree Ramamoorthy
2025-01-03 23:04 ` [PATCH v2 6/7] regulator: tps65215: Define probe() helper functions Shree Ramamoorthy
2025-01-03 23:04 ` [PATCH v2 7/7] regulator: tps65215: Restructure probe() for multi-PMIC support Shree Ramamoorthy
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=20250103230446.197597-1-s-ramamoorthy@ti.com \
--to=s-ramamoorthy@ti.com \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=broonie@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jerome.neanne@baylibre.com \
--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=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
all inboxes | Powered by JetHome®