From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Sebastian Reichel <sre@kernel.org>
Cc: Tony Lindgren <tony@atomide.com>,
devicetree@vger.kernel.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org,
Sebastian Reichel <sebastian.reichel@collabora.com>
Subject: [PATCH v2 7/7] ARM: dts: omap3: use generic node name for hsi clients
Date: Wed, 27 Mar 2024 20:11:38 +0100 [thread overview]
Message-ID: <20240327-hsi-dt-binding-v2-7-110fab4c32ae@collabora.com> (raw)
In-Reply-To: <20240327-hsi-dt-binding-v2-0-110fab4c32ae@collabora.com>
The HSI peripheral node name should reflect the generic type of
device for the node.
Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>
---
arch/arm/boot/dts/ti/omap/omap3-n900.dts | 2 +-
arch/arm/boot/dts/ti/omap/omap3-n950-n9.dtsi | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/ti/omap/omap3-n900.dts b/arch/arm/boot/dts/ti/omap/omap3-n900.dts
index b906b57371ce..bec31faf86db 100644
--- a/arch/arm/boot/dts/ti/omap/omap3-n900.dts
+++ b/arch/arm/boot/dts/ti/omap/omap3-n900.dts
@@ -1123,7 +1123,7 @@ &ssi_port1 {
ti,ssi-cawake-gpios = <&gpio5 23 GPIO_ACTIVE_HIGH>; /* 151 */
- modem: hsi-client {
+ modem: modem {
compatible = "nokia,n900-modem";
pinctrl-names = "default";
diff --git a/arch/arm/boot/dts/ti/omap/omap3-n950-n9.dtsi b/arch/arm/boot/dts/ti/omap/omap3-n950-n9.dtsi
index 6e0db8275227..7e6dbc1968aa 100644
--- a/arch/arm/boot/dts/ti/omap/omap3-n950-n9.dtsi
+++ b/arch/arm/boot/dts/ti/omap/omap3-n950-n9.dtsi
@@ -450,7 +450,7 @@ &ssi_port1 {
ti,ssi-cawake-gpios = <&gpio5 23 GPIO_ACTIVE_HIGH>; /* 151 */
- modem: hsi-client {
+ modem: modem {
pinctrl-names = "default";
pinctrl-0 = <&modem_pins1 &modem_pins2>;
--
2.43.0
next prev parent reply other threads:[~2024-03-27 19:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 19:11 [PATCH v2 0/7] Convert MIPI HSI DT bindings to YAML Sebastian Reichel
2024-03-27 19:11 ` [PATCH v2 1/7] dt-bindings: hsi: hsi-client: convert " Sebastian Reichel
2024-03-28 9:27 ` Krzysztof Kozlowski
2024-03-27 19:11 ` [PATCH v2 2/7] dt-bindings: hsi: nokia-modem: " Sebastian Reichel
2024-03-28 9:28 ` Krzysztof Kozlowski
2024-03-27 19:11 ` [PATCH v2 3/7] dt-bindings: hsi: omap-ssi: " Sebastian Reichel
2024-03-28 9:30 ` Krzysztof Kozlowski
2024-03-27 19:11 ` [PATCH v2 4/7] ARM: dts: omap4: fix hsi-port node name Sebastian Reichel
2024-03-28 9:30 ` Krzysztof Kozlowski
2024-03-27 19:11 ` [PATCH v2 5/7] ARM: dts: omap3: fix ssi-port " Sebastian Reichel
2024-03-28 9:30 ` Krzysztof Kozlowski
2024-03-27 19:11 ` [PATCH v2 6/7] ARM: dts: omap3: fix ti,ssi-cawake-gpio property name Sebastian Reichel
2024-03-28 9:30 ` Krzysztof Kozlowski
2024-03-27 19:11 ` Sebastian Reichel [this message]
2024-03-28 9:31 ` [PATCH v2 7/7] ARM: dts: omap3: use generic node name for hsi clients Krzysztof Kozlowski
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=20240327-hsi-dt-binding-v2-7-110fab4c32ae@collabora.com \
--to=sebastian.reichel@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sre@kernel.org \
--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