From: Neha Malcom Francis <n-francis@ti.com>
To: <robh@kernel.org>, <conor+dt@kernel.org>, <krzk+dt@kernel.org>,
<kristo@kernel.org>, <vigneshr@ti.com>, <nm@ti.com>,
<broonie@kernel.org>, <lgirdwood@gmail.com>
Cc: <marten.lindahl@axis.com>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<u-kumar1@ti.com>, <n-francis@ti.com>
Subject: [PATCH 1/5] regulator: dt-bindings: Unify compatible
Date: Tue, 7 May 2024 17:51:54 +0530 [thread overview]
Message-ID: <20240507122158.3739291-2-n-francis@ti.com> (raw)
In-Reply-To: <20240507122158.3739291-1-n-francis@ti.com>
TPS62870/1/2/3 devices have different output currents (6A/9A/12A/15A) of
the TPS6287x family. The I2C addresses are the same between them. There
is no need for different compatibles for each for these devices so drop
them and add a unified "ti,tps6287x" compatible.
Signed-off-by: Neha Malcom Francis <n-francis@ti.com>
---
.../devicetree/bindings/regulator/ti,tps62870.yaml | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/Documentation/devicetree/bindings/regulator/ti,tps62870.yaml b/Documentation/devicetree/bindings/regulator/ti,tps62870.yaml
index 386989544dac..2998773db990 100644
--- a/Documentation/devicetree/bindings/regulator/ti,tps62870.yaml
+++ b/Documentation/devicetree/bindings/regulator/ti,tps62870.yaml
@@ -15,10 +15,7 @@ allOf:
properties:
compatible:
enum:
- - ti,tps62870
- - ti,tps62871
- - ti,tps62872
- - ti,tps62873
+ - ti,tps6287x
reg:
maxItems: 1
@@ -40,7 +37,7 @@ examples:
#size-cells = <0>;
regulator@41 {
- compatible = "ti,tps62873";
+ compatible = "ti,tps6287x";
reg = <0x41>;
regulator-name = "+0.75V";
regulator-min-microvolt = <400000>;
--
2.34.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-05-07 12:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 12:21 [PATCH 0/5] arm64: ti: Add TPS6287 nodes Neha Malcom Francis
2024-05-07 12:21 ` Neha Malcom Francis [this message]
2024-05-07 21:11 ` [PATCH 1/5] regulator: dt-bindings: Unify compatible Rob Herring
2024-05-08 2:32 ` Neha Malcom Francis
2024-05-08 12:10 ` Mark Brown
2024-05-07 12:21 ` [PATCH 2/5] drivers: regulator: tps6287x: " Neha Malcom Francis
2024-05-07 12:21 ` [PATCH 3/5] arm64: boot: dts: ti: k3-am68-sk-base-board: Add LP8733 and TPS6287 nodes Neha Malcom Francis
2024-05-08 4:55 ` Kumar, Udit
2024-05-08 6:48 ` Neha Malcom Francis
2024-05-07 12:21 ` [PATCH 4/5] arm64: boot: dts: ti: k3-am69-sk: Add TPS62873 node Neha Malcom Francis
2024-05-07 12:21 ` [PATCH 5/5] arm64: boot: dts: ti: k3-j784s4-evm: " Neha Malcom Francis
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=20240507122158.3739291-2-n-francis@ti.com \
--to=n-francis@ti.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marten.lindahl@axis.com \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).