From: rentao.bupt@gmail.com
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@codeconstruct.com.au>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Andrew Lunn <andrew@lunn.ch>, Tao Ren <taoren@meta.com>
Cc: Tao Ren <rentao.bupt@gmail.com>
Subject: [PATCH v2 1/9] ARM: dts: aspeed: wedge400: Fix DTB warnings
Date: Sat, 5 Jul 2025 21:23:51 -0700 [thread overview]
Message-ID: <20250706042404.138128-2-rentao.bupt@gmail.com> (raw)
In-Reply-To: <20250706042404.138128-1-rentao.bupt@gmail.com>
From: Tao Ren <rentao.bupt@gmail.com>
Fix the deprecated spi-gpio properties in wedge400 dts.
Signed-off-by: Tao Ren <rentao.bupt@gmail.com>
---
Changes in v2:
- None (the patch is introduced in v2).
arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-wedge400.dts | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-wedge400.dts b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-wedge400.dts
index 5a8169bbda87..3e4d30f0884d 100644
--- a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-wedge400.dts
+++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-wedge400.dts
@@ -75,9 +75,9 @@ spi_gpio: spi {
#size-cells = <0>;
cs-gpios = <&gpio ASPEED_GPIO(R, 2) GPIO_ACTIVE_LOW>;
- gpio-sck = <&gpio ASPEED_GPIO(R, 3) GPIO_ACTIVE_HIGH>;
- gpio-mosi = <&gpio ASPEED_GPIO(R, 4) GPIO_ACTIVE_HIGH>;
- gpio-miso = <&gpio ASPEED_GPIO(R, 5) GPIO_ACTIVE_HIGH>;
+ sck-gpios = <&gpio ASPEED_GPIO(R, 3) GPIO_ACTIVE_HIGH>;
+ mosi-gpios = <&gpio ASPEED_GPIO(R, 4) GPIO_ACTIVE_HIGH>;
+ miso-gpios = <&gpio ASPEED_GPIO(R, 5) GPIO_ACTIVE_HIGH>;
num-chipselects = <1>;
tpm@0 {
--
2.47.1
next prev parent reply other threads:[~2025-07-06 4:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-06 4:23 [PATCH v2 0/9] ARM: dts: aspeed: Add Meta Darwin dts rentao.bupt
2025-07-06 4:23 ` rentao.bupt [this message]
2025-07-06 4:23 ` [PATCH v2 2/9] ARM: dts: aspeed: fuji: Fix DTB warnings rentao.bupt
2025-07-06 4:23 ` [PATCH v2 3/9] ARM: dts: aspeed: Fix DTB warnings in ast2600-facebook-netbmc-common.dtsi rentao.bupt
2025-07-06 4:23 ` [PATCH v2 4/9] ARM: dts: aspeed: Add facebook-bmc-flash-layout-128-data64.dtsi rentao.bupt
2025-07-06 4:23 ` [PATCH v2 5/9] ARM: dts: aspeed: wedge400: Extend data0 partition to 64MB rentao.bupt
2025-07-21 1:12 ` Andrew Jeffery
2025-07-21 5:55 ` Tao Ren
2025-07-06 4:23 ` [PATCH v2 6/9] ARM: dts: aspeed: Move flash layout out of Facebook netbmc-common.dtsi rentao.bupt
2025-07-21 1:13 ` Andrew Jeffery
2025-07-06 4:23 ` [PATCH v2 7/9] ARM: dts: aspeed: Move eMMC out of ast2600-facebook-netbmc-common.dtsi rentao.bupt
2025-07-06 4:23 ` [PATCH v2 8/9] dt-bindings: arm: aspeed: add Facebook Darwin board rentao.bupt
2025-07-06 7:24 ` Krzysztof Kozlowski
2025-07-06 4:23 ` [PATCH v2 9/9] ARM: dts: aspeed: Add Facebook Darwin (AST2600) BMC rentao.bupt
2025-07-06 4:37 ` [PATCH v2 0/9] ARM: dts: aspeed: Add Meta Darwin dts Tao Ren
2025-07-07 17:55 ` Rob Herring (Arm)
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=20250706042404.138128-2-rentao.bupt@gmail.com \
--to=rentao.bupt@gmail.com \
--cc=andrew@codeconstruct.com.au \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=taoren@meta.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).