public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: 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, 24 Apr 2025 14:59:17 +0100	[thread overview]
Message-ID: <20250424135917.GE8734@google.com> (raw)
In-Reply-To: <174550310025.1376894.8036030194609947768.b4-ty@kernel.org>

On Thu, 24 Apr 2025, Lee Jones wrote:

> On Tue, 08 Apr 2025 11:40:24 +0300, 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.
> > 
> > [...]
> 
> Applied, thanks!
> 
> [01/14] dt-bindings: regulator: Add ROHM BD96802 PMIC
>         commit: 9effbfda6bfd677042434722a9c2f2e17d261dce
> [02/14] dt-bindings: mfd: Add ROHM BD96802 PMIC
>         commit: 9d851b2e016a13b0a673503f5600315b6601e025
> [03/14] dt-bindings: mfd: bd96801: Add ROHM BD96805
>         commit: d5a30228b6fa86cf841d8c12af0025c0bacb90fb
> [04/14] dt-bindings: mfd: bd96802: Add ROHM BD96806
>         commit: 82c218969eb0ec989d8e049878fd3d6a97ccd8ba
> [05/14] mfd: rohm-bd96801: Add chip info
>         commit: 7289d96ba557fb5e0a90813b7e24f3815127d14d
> [06/14] mfd: bd96801: Drop IC name from the regulator IRQ resources
>         commit: d082571fca4d1db5642ad4436cef22d65bfe4153
> [07/14] regulator: bd96801: Drop IC name from the IRQ resources
>         commit: 9cc957546e3865bc3adfd39ceeedc8074521024d
> [08/14] mfd: rohm-bd96801: Support ROHM BD96802
>         commit: 4094040b1a133206ed893da2cf5e17cc22f7ca7c
> [09/14] regulator: bd96801: Support ROHM BD96802
>         commit: 55606b9b20639b634560f44a070ff6153b59b557
> [10/14] mfd: bd96801: Support ROHM BD96805
>         commit: 6a309b489215f705c20cb4ed7f85d9c16f768e55
> [11/14] regulator: bd96801: Support ROHM BD96805 PMIC
>         commit: 7baf818d0d90e00c0688d8156bc7d9d1d1ee1dbb
> [12/14] mfd: bd96801: Support ROHM BD96806
>         commit: fecc18a9f59ce9c36eb3622ae77bff5fa5c6d976
> [13/14] regulator: bd96801: Support ROHM BD96806 PMIC
>         commit: 956e9363c8230a0dc9a83cf5de61200206a9154b
> [14/14] MAINTAINERS: Add BD96802 specific header
>         commit: 5d61bb1675ff7662f519ca203b1f8cdc455b9df4

Submitted for build testing.  Once they've passed, I'll submit a PR.

Note to self: ib-mfd-regulator-6.16

-- 
Lee Jones [李琼斯]

  reply	other threads:[~2025-04-24 13:59 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
2025-04-24 13:58 ` Lee Jones
2025-04-24 13:59   ` Lee Jones [this message]
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=20250424135917.GE8734@google.com \
    --to=lee@kernel.org \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mazziesaccount@gmail.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