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 04/14] dt-bindings: mfd: bd96802: Add ROHM BD96806
Date: Tue, 25 Mar 2025 17:14:43 +0000	[thread overview]
Message-ID: <20250325-resent-presuming-39ad42e2ceef@spud> (raw)
In-Reply-To: <99ffe94d642b6c73cd5199103e65419c93214533.1742802856.git.mazziesaccount@gmail.com>

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

On Mon, Mar 24, 2025 at 10:55:21AM +0200, Matti Vaittinen wrote:
> The ROHM BD96806 is very similar to the BD96802. The differences visible
> to the drivers is different tune voltage ranges.
> 
> Add compatible for the ROHM BD96805 PMIC.
> 
> Signed-off-by: Matti Vaittinen <mazziesaccount@gmail.com>
> 
> ---
> Revision history:
>  v1 => :
>   - No changes
> ---
>  .../bindings/mfd/rohm,bd96802-pmic.yaml       | 19 ++++++++++---------
>  1 file changed, 10 insertions(+), 9 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/mfd/rohm,bd96802-pmic.yaml b/Documentation/devicetree/bindings/mfd/rohm,bd96802-pmic.yaml
> index d5d9e69dc0c2..c6e6be4015b2 100644
> --- a/Documentation/devicetree/bindings/mfd/rohm,bd96802-pmic.yaml
> +++ b/Documentation/devicetree/bindings/mfd/rohm,bd96802-pmic.yaml
> @@ -4,23 +4,23 @@
>  $id: http://devicetree.org/schemas/mfd/rohm,bd96802-pmic.yaml#
>  $schema: http://devicetree.org/meta-schemas/core.yaml#
>  
> -title: ROHM BD96802 Scalable Power Management Integrated Circuit
> +title: ROHM BD96802 / BD96806Scalable Power Management Integrated Circuit
                                ^ Missing space here :)

>  
>  maintainers:
>    - Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
>  
>  description: |
> -  BD96802Qxx-C is an automotive grade configurable Power Management
> -  Integrated Circuit supporting Functional Safety features for application
> +  BD96802Qxx-C and BD96806 are automotive grade configurable Power Management
> +  Integrated Circuits supporting Functional Safety features for application
>    processors, SoCs and FPGAs
>  
>  properties:
>    compatible:
> -    const: rohm,bd96802
> +    enum:
> +      - rohm,bd96802
> +      - rohm,bd96806
>  
>    reg:
> -    description:
> -      I2C slave address.

I'd just drop this from the original.

>      maxItems: 1
>  
>    interrupts:
> @@ -29,7 +29,8 @@ properties:
>        for fatal IRQs which will cause the PMIC to shut down power outputs.
>        In many systems this will shut down the SoC contolling the PMIC and
>        connecting/handling the errb can be omitted. However, there are cases
> -      where the SoC is not powered by the PMIC. In that case it may be
> +      where the SoC is not powered by the PMIC or has a short time backup
> +      energy to handle shutdown of critical hardware. In that case it may be
>        useful to connect the errb and handle errb events.
>      minItems: 1
>      maxItems: 2
> @@ -69,7 +70,7 @@ examples:
>              interrupt-names = "intb", "errb";
>  
>              regulators {
> -                buck1: BUCK1 {
> +                buck1 {

Here too?

>                      regulator-name = "buck1";
>                      regulator-ramp-delay = <1250>;
>                      /* 0.5V min INITIAL - 150 mV tune */
> @@ -84,7 +85,7 @@ examples:
>                      regulator-temp-protection-kelvin = <1>;
>                      regulator-temp-warn-kelvin = <0>;
>                  };
> -                buck2: BUCK2 {

and here?

> +                buck2 {
>                      regulator-name = "buck2";
>                      regulator-min-microvolt = <350000>;
>                      regulator-max-microvolt = <3450000>;
> -- 
> 2.49.0
> 



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

  reply	other threads:[~2025-03-25 17:14 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
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 [this message]
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=20250325-resent-presuming-39ad42e2ceef@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