From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Lee Jones <lee@kernel.org>
Cc: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 00/14] Support ROHM Scalable PMIC family
Date: Thu, 10 Apr 2025 11:12:42 +0300 [thread overview]
Message-ID: <ea291459-5c25-40bc-997a-490fe2a42a12@gmail.com> (raw)
In-Reply-To: <20250410075817.GN372032@google.com>
On 10/04/2025 10:58, Lee Jones wrote:
> On Tue, 08 Apr 2025, Matti Vaittinen wrote:
>
>> Support ROHM BD96802, BD96805 and BD96806 PMICs
>>
>> The ROHM BD96801 [1] and BD96805 [2] are almost identical PMICs what comes
>> to the digital interface. Main difference is voltage tuning range.
>> Supporting BD96805 with BD96801 drivers is mostly just a matter of being
>> able to differentiate the PMICs (done based on the devicetree
>> compatible) and then providing separate voltage tables.
>>
>> The ROHM BD96802 [3] is a companion PMIC which is intended to be used to
>> provide more capacity on systems where the BD96801 alone is not
>> sufficient. Startup sequence of these PMICs can be synchronized in
>> hardware level, and there seems to be some mechanisms which allow
>> delivering the companion PMIC (BD96802) status to the main PMIC
>> (BD96801/BD96805). This patch series does treat the companion PMIC(s) as
>> individual PMICs and allows using them from software point of view as a
>> stand alone ICs. From the digital point of view, the BD96802 is a subset
>> of BD96801, providing only buck1 and buck2 regulators. Please see the
>> data sheet
>>
>> The ROHM BD96806 [4] is similar to the BD96802, except that it does also
>> provide different voltage tuning ranges.
>>
>> This series adds basic voltage monitoring and control as well as a
>> watchdog support for these PMICs using the BD96801 drivers.
>>
>> Similarly to the BD96801, these PMICs too have a few configurations
>> which can only be done when the PMIC is in STBY state. Similarly to the
>> BD96801, doing these configurations isn't supported by the driver. The
>> original BD96801 RFC [5] driver should be able to cover those
>> configurations, if modified to support these models.
>>
>> [1]: ROHM BD96801 data sheet:
>> https://fscdn.rohm.com/en/products/databook/datasheet/ic/power/switching_regulator_system/product_brief_bd96801qxx-c-e.pdf
>> [2]: ROHM BD96805 data sheet:
>> https://fscdn.rohm.com/en/products/databook/datasheet/ic/power/switching_regulator_system/product_brief_bd96805qxx-c-e.pdf
>> [3]: ROHM BD96802 data sheet:
>> https://fscdn.rohm.com/en/products/databook/datasheet/ic/power/switching_regulator_system/product_brief_bd96802qxx-c-e.pdf
>> [4]: ROHM BD96806 data sheet:
>> https://fscdn.rohm.com/en/products/databook/datasheet/ic/power/switching_regulator_system/product_brief_bd96806qxx-c-e.pdf
>> [5]: Original BD96801 RFC:
>> https://lore.kernel.org/all/cover.1712058690.git.mazziesaccount@gmail.com/
>>
>> Revision history:
>> v2 => v3:
>> - Fix BD96806 voltages
>> - Use defines for voltages to ease spotting (copy-paste) errors in
>> regulator descs
>> - Use lowercase node names in the BD96802 dt-binding
>> v1 => v2: MFD driver changes after review by Lee
>> - Use enum for chip type instead of picking the data directly from the
>> of_match_data.
>> - rename "chip data" variable 'cd' to more widely used 'ddata'.
>> link to v1:
>> https://lore.kernel.org/all/cover.1741864404.git.mazziesaccount@gmail.com/
>>
>>
>> Matti Vaittinen (14):
>> dt-bindings: regulator: Add ROHM BD96802 PMIC
>> dt-bindings: mfd: Add ROHM BD96802 PMIC
>> dt-bindings: mfd: bd96801: Add ROHM BD96805
>> dt-bindings: mfd: bd96802: Add ROHM BD96806
>> mfd: rohm-bd96801: Add chip info
>> mfd: bd96801: Drop IC name from the regulator IRQ resources
>> regulator: bd96801: Drop IC name from the IRQ resources
>> mfd: rohm-bd96801: Support ROHM BD96802
>> regulator: bd96801: Support ROHM BD96802
>> mfd: bd96801: Support ROHM BD96805
>> regulator: bd96801: Support ROHM BD96805 PMIC
>> mfd: bd96801: Support ROHM BD96806
>> regulator: bd96801: Support ROHM BD96806 PMIC
>> MAINTAINERS: Add BD96802 specific header
>>
>> .../bindings/mfd/rohm,bd96801-pmic.yaml | 10 +-
>> .../bindings/mfd/rohm,bd96802-pmic.yaml | 101 ++++
>> .../regulator/rohm,bd96802-regulator.yaml | 44 ++
>> MAINTAINERS | 1 +
>> drivers/mfd/rohm-bd96801.c | 565 ++++++++++++++----
>> drivers/regulator/bd96801-regulator.c | 455 ++++++++++++--
>> include/linux/mfd/rohm-bd96801.h | 2 +
>> include/linux/mfd/rohm-bd96802.h | 74 +++
>> include/linux/mfd/rohm-generic.h | 3 +
>> 9 files changed, 1073 insertions(+), 182 deletions(-)
>> create mode 100644 Documentation/devicetree/bindings/mfd/rohm,bd96802-pmic.yaml
>> create mode 100644 Documentation/devicetree/bindings/regulator/rohm,bd96802-regulator.yaml
>> create mode 100644 include/linux/mfd/rohm-bd96802.h
>
> This set good to go now?
Yes :)
Yours,
-- Matti
next prev parent reply other threads:[~2025-04-10 8:12 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 8:40 [PATCH v3 00/14] Support ROHM Scalable PMIC family Matti Vaittinen
2025-04-08 8:40 ` [PATCH v3 01/14] dt-bindings: regulator: Add ROHM BD96802 PMIC Matti Vaittinen
2025-04-08 16:16 ` Conor Dooley
2025-04-09 4:30 ` Matti Vaittinen
2025-04-09 5:43 ` Matti Vaittinen
2025-04-08 8:40 ` [PATCH v3 02/14] dt-bindings: mfd: " Matti Vaittinen
2025-04-08 16:11 ` Conor Dooley
2025-04-08 8:41 ` [PATCH v3 03/14] dt-bindings: mfd: bd96801: Add ROHM BD96805 Matti Vaittinen
2025-04-08 8:44 ` [PATCH v3 04/14] dt-bindings: mfd: bd96802: Add ROHM BD96806 Matti Vaittinen
2025-04-08 16:09 ` Conor Dooley
2025-04-08 8:44 ` [PATCH v3 05/14] mfd: rohm-bd96801: Add chip info Matti Vaittinen
2025-04-08 8:45 ` [PATCH v3 06/14] mfd: bd96801: Drop IC name from the regulator IRQ resources Matti Vaittinen
2025-04-08 8:45 ` [PATCH v3 07/14] regulator: bd96801: Drop IC name from the " Matti Vaittinen
2025-04-08 20:19 ` Mark Brown
2025-04-08 8:45 ` [PATCH v3 08/14] mfd: rohm-bd96801: Support ROHM BD96802 Matti Vaittinen
2025-04-08 8:46 ` [PATCH v3 09/14] regulator: bd96801: " Matti Vaittinen
2025-04-08 20:19 ` Mark Brown
2025-04-08 8:46 ` [PATCH v3 10/14] mfd: bd96801: Support ROHM BD96805 Matti Vaittinen
2025-04-08 8:46 ` [PATCH v3 11/14] regulator: bd96801: Support ROHM BD96805 PMIC Matti Vaittinen
2025-04-08 8:47 ` [PATCH v3 12/14] mfd: bd96801: Support ROHM BD96806 Matti Vaittinen
2025-04-08 8:47 ` [PATCH v3 13/14] regulator: bd96801: Support ROHM BD96806 PMIC Matti Vaittinen
2025-04-08 8:47 ` [PATCH v3 14/14] MAINTAINERS: Add BD96802 specific header Matti Vaittinen
2025-04-10 7:58 ` [PATCH v3 00/14] Support ROHM Scalable PMIC family Lee Jones
2025-04-10 8:12 ` Matti Vaittinen [this message]
2025-04-24 13:58 ` Lee Jones
2025-04-24 13:59 ` Lee Jones
2025-05-02 7:47 ` [GIT PULL] Immutable branch between MFD and Regulator due for the v6.16 merge window Lee Jones
2025-05-02 23:25 ` Mark Brown
2025-05-06 5:28 ` Matti Vaittinen
2025-05-06 14:10 ` Mark Brown
2025-05-06 14:29 ` Matti Vaittinen
2025-05-07 10:33 ` Lee Jones
2025-05-07 10:36 ` Lee Jones
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=ea291459-5c25-40bc-997a-490fe2a42a12@gmail.com \
--to=mazziesaccount@gmail.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=robh@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