public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
	Lee Jones <lee@kernel.org>, 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 v2 01/14] dt-bindings: regulator: Add ROHM BD96802 PMIC
Date: Wed, 26 Mar 2025 18:09:22 +0000	[thread overview]
Message-ID: <20250326-candy-endocrine-2e7b2182e53b@spud> (raw)
In-Reply-To: <f8b0553d-d74d-47c5-89f1-6c61ed0951bc@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3858 bytes --]

On Wed, Mar 26, 2025 at 08:15:05AM +0200, Matti Vaittinen wrote:
> Hi Conor,
> 
> Thanks for taking a look at this :)
> 
> On 25/03/2025 19:23, Conor Dooley wrote:
> > On Mon, Mar 24, 2025 at 10:54:44AM +0200, Matti Vaittinen wrote:
> > > BD96802Qxx-C is an automotive grade configurable Power Management
> > > Integrated Circuit supporting Functional Safety features for application
> > > processors, SoCs and FPGAs. BD96802 is controlled via I2C, provides two
> > > interrupt lines and has two controllable buck regulators.
> > > 
> > > The BD96802 belongs to the family of ROHM Scalable PMICs and is intended
> > > to be used as a companion PMIC for the BD96801.
> > > 
> > > Signed-off-by: Matti Vaittinen <mazziesaccount@gmail.com>
> > > 
> > > ---
> > > Revision history:
> > >   v1 => :
> > >    - No changes
> > > ---
> > >   .../regulator/rohm,bd96802-regulator.yaml     | 44 +++++++++++++++++++
> > >   1 file changed, 44 insertions(+)
> > >   create mode 100644 Documentation/devicetree/bindings/regulator/rohm,bd96802-regulator.yaml
> > > 
> > > diff --git a/Documentation/devicetree/bindings/regulator/rohm,bd96802-regulator.yaml b/Documentation/devicetree/bindings/regulator/rohm,bd96802-regulator.yaml
> > > new file mode 100644
> > > index 000000000000..671eaf1096d3
> > > --- /dev/null
> > > +++ b/Documentation/devicetree/bindings/regulator/rohm,bd96802-regulator.yaml
> > > @@ -0,0 +1,44 @@
> > > +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> > > +%YAML 1.2
> > > +---
> > > +$id: http://devicetree.org/schemas/regulator/rohm,bd96802-regulator.yaml#
> > > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > > +
> > > +title: ROHM BD96802 Power Management Integrated Circuit regulators
> > > +
> > > +maintainers:
> > > +  - Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
> > > +
> > > +description:
> > > +  This module is part of the ROHM BD96802 MFD device. For more details
> > > +  see Documentation/devicetree/bindings/mfd/rohm,bd96802-pmic.yaml.
> > > +
> > > +  The regulator controller is represented as a sub-node of the PMIC node
> > > +  on the device tree.
> > > +
> > > +  Regulator nodes should be named to buck1 and buck2.
> > 
> > Is it really needed to add a new binding for this, rather than including
> > it in the mfd binding,
> 
> A valid question. I did this because that's what I've used with all the
> other PMIC's regulator bindings. All of these have MFD counterpart:
> 
> rohm,bd71815-regulator.yaml
> rohm,bd71828-regulator.yaml
> rohm,bd71837-regulator.yaml
> rohm,bd71847-regulator.yaml
> rohm,bd9576-regulator.yaml
> rohm,bd96801-regulator.yaml
> 
> Basically, none of the MFD bindings I've written for ROHM PMICs contain the
> regulator descriptions.
> 
> The thing is that users might be used to look for the regulator bindings
> from the regulator folder. I'd like to keep this consistent, especially with
> the BD96801 because the BD96802 is intended to be used together with it.
> (BD96802 is used as a companion PMIC for the BD96801 to extend it's
> capabilities).
> 
> > particularly when this isn't actually a binding
> > for the regulator but the pattern section applies to the mfd.
> 
> Hmmm? I am not sure I understand what you mean here. I know I am really bad
> with the YAML and bindings, but if I read correctly what I've copied - the
> pattern section describes what is inside the 'regulators' node. I think this
> is similar to what we have with the rest of the ROHM PMIC bindings. Should
> they all be somehow modified?

I just think it is weird to be honest, describing the contents of
regulators node, rather than the individual regulators themselves, but
if Rob and Krzysztof, which they seem to be, I will not object.

Acked-by: Conor Dooley <conor.dooley@microchip.com>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-03-26 18:09 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-24  8:54 [PATCH v2 00/14] Support ROHM Scalable PMIC family Matti Vaittinen
2025-03-24  8:54 ` [PATCH v2 01/14] dt-bindings: regulator: Add ROHM BD96802 PMIC Matti Vaittinen
2025-03-25 17:23   ` Conor Dooley
2025-03-26  6:15     ` Matti Vaittinen
2025-03-26 18:09       ` Conor Dooley [this message]
2025-03-24  8:54 ` [PATCH v2 02/14] dt-bindings: mfd: " Matti Vaittinen
2025-03-24  8:55 ` [PATCH v2 03/14] dt-bindings: mfd: bd96801: Add ROHM BD96805 Matti Vaittinen
2025-03-25 17:15   ` Conor Dooley
2025-03-24  8:55 ` [PATCH v2 04/14] dt-bindings: mfd: bd96802: Add ROHM BD96806 Matti Vaittinen
2025-03-25 17:14   ` Conor Dooley
2025-03-26  6:18     ` Matti Vaittinen
2025-03-24  8:55 ` [PATCH v2 05/14] mfd: rohm-bd96801: Add chip info Matti Vaittinen
2025-03-24  8:55 ` [PATCH v2 06/14] mfd: bd96801: Drop IC name from the regulator IRQ resources Matti Vaittinen
2025-03-24  8:55 ` [PATCH v2 07/14] regulator: bd96801: Drop IC name from the " Matti Vaittinen
2025-03-24  8:56 ` [PATCH v2 08/14] mfd: rohm-bd96801: Support ROHM BD96802 Matti Vaittinen
2025-03-24  8:56 ` [PATCH v2 09/14] regulator: bd96801: " Matti Vaittinen
2025-03-24  8:56 ` [PATCH v2 10/14] mfd: bd96801: Support ROHM BD96805 Matti Vaittinen
2025-03-24  8:56 ` [PATCH v2 11/14] regulator: bd96801: Support ROHM BD96805 PMIC Matti Vaittinen
2025-03-26 13:11   ` Mark Brown
2025-03-24  8:57 ` [PATCH v2 12/14] mfd: bd96801: Support ROHM BD96806 Matti Vaittinen
2025-03-24  8:57 ` [PATCH v2 13/14] regulator: bd96801: Support ROHM BD96806 PMIC Matti Vaittinen
2025-03-26 13:12   ` Mark Brown
2025-04-02  9:32   ` Matti Vaittinen
2025-03-24  8:57 ` [PATCH v2 14/14] MAINTAINERS: Add BD96802 specific header Matti Vaittinen
2025-04-04 15:43 ` [PATCH v2 00/14] Support ROHM Scalable PMIC family Lee Jones
2025-04-07  5:09   ` Matti Vaittinen
2025-04-08  8:05   ` Matti Vaittinen
2025-04-10  8:02     ` Lee Jones
2025-04-10  8:15       ` Matti Vaittinen
2025-04-09  4:38   ` Matti Vaittinen

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=20250326-candy-endocrine-2e7b2182e53b@spud \
    --to=conor@kernel.org \
    --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=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