devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Huacai Chen <chenhuacai@kernel.org>,
	WANG Xuerui <kernel@xen0n.name>,
	devicetree@vger.kernel.org, loongarch@lists.linux.dev
Subject: [PATCH 6/7] LoongArch: dts: use proper node names for GPIO based I2C busses
Date: Mon, 19 May 2025 14:15:06 +0200	[thread overview]
Message-ID: <20250519121512.5657-7-wsa+renesas@sang-engineering.com> (raw)
In-Reply-To: <20250519121512.5657-1-wsa+renesas@sang-engineering.com>

There shall not be a '-' before the number.

Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
---
 arch/loongarch/boot/dts/loongson-2k1000.dtsi | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/loongarch/boot/dts/loongson-2k1000.dtsi b/arch/loongarch/boot/dts/loongson-2k1000.dtsi
index 1da3beb00f0e..ddf63801eef0 100644
--- a/arch/loongarch/boot/dts/loongson-2k1000.dtsi
+++ b/arch/loongarch/boot/dts/loongson-2k1000.dtsi
@@ -46,7 +46,7 @@ cpuintc: interrupt-controller {
 	};
 
 	/* i2c of the dvi eeprom edid */
-	i2c-gpio-0 {
+	i2c-gpio0 {
 		compatible = "i2c-gpio";
 		scl-gpios = <&gpio0 0 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>;
 		sda-gpios = <&gpio0 1 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>;
@@ -57,7 +57,7 @@ i2c-gpio-0 {
 	};
 
 	/* i2c of the eeprom edid */
-	i2c-gpio-1 {
+	i2c-gpio1 {
 		compatible = "i2c-gpio";
 		scl-gpios = <&gpio0 33 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>;
 		sda-gpios = <&gpio0 32 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>;
-- 
2.47.2


  parent reply	other threads:[~2025-05-19 12:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-19 12:15 [PATCH 0/7] archs: use proper node names for GPIO based I2C busses Wolfram Sang
2025-05-19 12:15 ` [PATCH 1/7] arm64: dts: exynos: " Wolfram Sang
2025-05-19 13:54   ` Krzysztof Kozlowski
2025-05-19 14:45     ` Wolfram Sang
2025-05-19 15:05       ` Krzysztof Kozlowski
2025-05-19 15:14         ` Wolfram Sang
2025-05-19 16:11           ` Krzysztof Kozlowski
2025-05-19 16:25             ` Wolfram Sang
2025-05-19 18:50               ` Wolfram Sang
2025-06-12  7:46                 ` Krzysztof Kozlowski
2025-06-12  7:50                   ` Wolfram Sang
2025-06-12  9:02                     ` Krzysztof Kozlowski
2025-06-12  9:49                     ` Krzysztof Kozlowski
2025-06-12  9:54                       ` Wolfram Sang
2025-05-19 16:28             ` Herve Codina
2025-05-19 12:15 ` [PATCH 2/7] arm64: dts: mediatek: " Wolfram Sang
2025-05-19 12:15 ` [PATCH 3/7] ARM: dts: microchip: " Wolfram Sang
2025-05-19 12:15 ` [PATCH 4/7] ARM: dts: samsung: " Wolfram Sang
2025-05-19 12:15 ` [PATCH 5/7] ARM: dts: stm32: " Wolfram Sang
2025-05-19 12:15 ` Wolfram Sang [this message]
2025-05-19 12:15 ` [PATCH 7/7] riscv: dts: allwinner: " Wolfram Sang
2025-05-19 13:10   ` Chen-Yu Tsai
2025-05-19 12:54 ` [PATCH 0/7] archs: " Geert Uytterhoeven
2025-05-19 14:47   ` Wolfram Sang
2025-05-19 18:59 ` Wolfram Sang

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=20250519121512.5657-7-wsa+renesas@sang-engineering.com \
    --to=wsa+renesas@sang-engineering.com \
    --cc=chenhuacai@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@xen0n.name \
    --cc=krzk+dt@kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --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;
as well as URLs for NNTP newsgroup(s).