Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Roger Quadros <rogerq@kernel.org>
To: Shree Ramamoorthy <s-ramamoorthy@ti.com>,
	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, 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
Subject: Re: [PATCH v1 1/7] regulator: dt-bindings: Add TI TPS65215 PMIC bindings
Date: Sat, 4 Jan 2025 20:28:19 +0200	[thread overview]
Message-ID: <918d3b67-9bb3-4da2-a779-69ae9e9c4f6b@kernel.org> (raw)
In-Reply-To: <20241226215412.395822-2-s-ramamoorthy@ti.com>



On 26/12/2024 23:54, Shree Ramamoorthy wrote:
> TPS65215 is a Power Management IC with 3 Buck regulators and 2 LDOs.
> 
> TPS65215 has 2 LDOS and 1 GPO, whereas TPS65219 has 4 LDOs and 2 GPOs. The
> remaining features for both devices are the same.
> 
> Signed-off-by: Shree Ramamoorthy <s-ramamoorthy@ti.com>
> ---
>  .../devicetree/bindings/regulator/ti,tps65219.yaml       | 9 ++++++++-
>  1 file changed, 8 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/devicetree/bindings/regulator/ti,tps65219.yaml b/Documentation/devicetree/bindings/regulator/ti,tps65219.yaml
> index 78e64521d401..ba5f6fcf5219 100644
> --- a/Documentation/devicetree/bindings/regulator/ti,tps65219.yaml
> +++ b/Documentation/devicetree/bindings/regulator/ti,tps65219.yaml
> @@ -4,7 +4,7 @@
>  $id: http://devicetree.org/schemas/regulator/ti,tps65219.yaml#
>  $schema: http://devicetree.org/meta-schemas/core.yaml#
>  
> -title: TI tps65219 Power Management Integrated Circuit regulators
> +title: TI TPS65215/TPS65219 Power Management Integrated Circuit
>  
>  maintainers:
>    - Jerome Neanne <jerome.neanne@baylibre.com>
> @@ -12,10 +12,17 @@ maintainers:
>  description: |
>    Regulator nodes should be named to buck<number> and ldo<number>.
>  
> +  TI TPS65219 is a Power Management IC with 3 Buck regulators, 4 Low
> +  Drop-out Regulators (LDOs), 1 GPIO, 2 GPOs, and power-button.
> +
> +  TI TPS65215 is a derivative of TPS65219 with 3 Buck regulators, 2 Low
> +  Drop-out Regulators (LDOs), 1 GPIO, 1 GPO, and power-button.
> +
>  properties:
>    compatible:
>      enum:
>        - ti,tps65219
> +      - ti,tps65215

Could be sorted alphanumerically.

>  
>    reg:
>      maxItems: 1

-- 
cheers,
-roger


  parent reply	other threads:[~2025-01-04 18:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-26 21:54 [PATCH v1 0/7] Add TI TPS65215 PMIC Regulator Support Shree Ramamoorthy
2024-12-26 21:54 ` [PATCH v1 1/7] regulator: dt-bindings: Add TI TPS65215 PMIC bindings Shree Ramamoorthy
2024-12-27 17:45   ` Conor Dooley
2025-01-04 18:28   ` Roger Quadros [this message]
2024-12-26 21:54 ` [PATCH v1 2/7] regulator: tps65215: Update platform_device_id table Shree Ramamoorthy
2025-01-01 10:49   ` Christophe JAILLET
2024-12-26 21:54 ` [PATCH v1 3/7] regulator: tps65215: Update function & struct names Shree Ramamoorthy
2025-01-04 18:35   ` Roger Quadros
2024-12-26 21:54 ` [PATCH v1 4/7] regulator: tps65215: Update IRQ structs to include TPS65215 Shree Ramamoorthy
2024-12-26 21:54 ` [PATCH v1 5/7] regulator: tps65215: Add chip_data struct for multi-PMIC support Shree Ramamoorthy
2024-12-26 21:54 ` [PATCH v1 6/7] regulator: tps65215: Define probe() helper functions Shree Ramamoorthy
2025-01-01 11:01   ` Christophe JAILLET
2025-01-02 23:41     ` Shree Ramamoorthy
2025-01-03 13:10       ` Christophe JAILLET
2025-01-04 18:42       ` Roger Quadros
2025-01-04 18:45   ` Roger Quadros
2025-01-06 22:02     ` Shree Ramamoorthy
2025-01-06 22:57       ` Andrew Davis
2025-01-07 21:09         ` Shree Ramamoorthy
2024-12-26 21:54 ` [PATCH v1 7/7] regulator: tps65215: Restructure probe() for multi-PMIC support Shree Ramamoorthy
2025-01-01 11:04   ` Christophe JAILLET
2025-01-02 23:46     ` Shree Ramamoorthy
2025-01-04 18:47   ` Roger Quadros
2025-01-07 21:12     ` 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=918d3b67-9bb3-4da2-a779-69ae9e9c4f6b@kernel.org \
    --to=rogerq@kernel.org \
    --cc=aaro.koskinen@iki.fi \
    --cc=andreas@kemnade.info \
    --cc=broonie@kernel.org \
    --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=s-ramamoorthy@ti.com \
    --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