linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Andrew Lunn <andrew@lunn.ch>,
	Claudiu Beznea <claudiu.beznea@tuxon.dev>,
	Conor Dooley <conor+dt@kernel.org>,
	devicetree@vger.kernel.org,
	Gregory Clement <gregory.clement@bootlin.com>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Nicolas Ferre <nicolas.ferre@microchip.com>,
	Rob Herring <robh@kernel.org>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: [PATCH 0/4] ARM: dts: use recent scl/sda gpio bindings
Date: Mon, 19 May 2025 13:21:02 +0200	[thread overview]
Message-ID: <20250519112107.2980-1-wsa+renesas@sang-engineering.com> (raw)

Some ARM boards still use the deprecated 'gpios' property to describe a
GPIO based I2C bus. Let them use the proper '{scl|sda}-gpios' property.

Based on linux-next as of 20250516. No dependencies. I suggest that
patches go via their subsystem trees.

Tested on Calao USB boards using AT91 chipsets.

Wolfram Sang (4):
  ARM: dts: cirrus: ep7211: use recent scl/sda gpio bindings
  ARM: dts: marvell: kirkwood: use recent scl/sda gpio bindings
  ARM: dts: microchip: use recent scl/sda gpio bindings
  ARM: dts: stm32: use recent scl/sda gpio bindings

 arch/arm/boot/dts/cirrus/ep7211-edb7211.dts       |  4 ++--
 arch/arm/boot/dts/marvell/kirkwood-km_common.dtsi |  4 ++--
 arch/arm/boot/dts/microchip/at91rm9200.dtsi       |  5 ++---
 arch/arm/boot/dts/microchip/at91sam9260.dtsi      |  5 ++---
 arch/arm/boot/dts/microchip/at91sam9261.dtsi      |  4 ++--
 arch/arm/boot/dts/microchip/at91sam9263.dtsi      |  5 ++---
 arch/arm/boot/dts/microchip/at91sam9g45.dtsi      |  5 ++---
 arch/arm/boot/dts/microchip/at91sam9n12.dtsi      |  5 ++---
 arch/arm/boot/dts/microchip/at91sam9rl.dtsi       |  8 ++++----
 arch/arm/boot/dts/microchip/at91sam9x5.dtsi       | 15 ++++++---------
 arch/arm/boot/dts/st/ste-nomadik-s8815.dts        |  4 ++--
 11 files changed, 28 insertions(+), 36 deletions(-)

-- 
2.47.2



             reply	other threads:[~2025-05-19 11:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-19 11:21 Wolfram Sang [this message]
2025-05-19 11:21 ` [PATCH 1/4] ARM: dts: cirrus: ep7211: use recent scl/sda gpio bindings Wolfram Sang
2025-05-19 11:21 ` [PATCH 2/4] ARM: dts: marvell: kirkwood: " Wolfram Sang
2025-05-19 14:31   ` Gregory CLEMENT
2025-05-19 11:21 ` [PATCH 3/4] ARM: dts: microchip: " Wolfram Sang
2025-06-07 11:17   ` Claudiu Beznea
2025-06-24  7:13   ` Claudiu Beznea
2025-05-19 11:21 ` [PATCH 4/4] ARM: dts: stm32: " 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=20250519112107.2980-1-wsa+renesas@sang-engineering.com \
    --to=wsa+renesas@sang-engineering.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregory.clement@bootlin.com \
    --cc=krzk+dt@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=nicolas.ferre@microchip.com \
    --cc=robh@kernel.org \
    --cc=sebastian.hesselbarth@gmail.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 NNTP newsgroup(s).