From: Adam Ford <aford173@gmail.com>
To: linux-omap@vger.kernel.org
Cc: aford@beaconembedded.com, "Adam Ford" <aford173@gmail.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Tony Lindgren" <tony@atomide.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] arm: dts: omap3: Migrate hsmmc driver to sdhci driver
Date: Tue, 13 Feb 2024 06:41:45 -0600 [thread overview]
Message-ID: <20240213124146.202391-1-aford173@gmail.com> (raw)
The sdhci driver has been around for several years, and it supports
the OMAP3 family. Instead of using the older driver, let's finally
migrate to the newer one.
Signed-off-by: Adam Ford <aford173@gmail.com>
diff --git a/arch/arm/boot/dts/ti/omap/omap3.dtsi b/arch/arm/boot/dts/ti/omap/omap3.dtsi
index 92cd4c99dae7..218d7212c749 100644
--- a/arch/arm/boot/dts/ti/omap/omap3.dtsi
+++ b/arch/arm/boot/dts/ti/omap/omap3.dtsi
@@ -507,7 +507,7 @@ hdqw1w: 1w@480b2000 {
};
mmc1: mmc@4809c000 {
- compatible = "ti,omap3-hsmmc";
+ compatible = "ti,omap3-sdhci";
reg = <0x4809c000 0x200>;
interrupts = <83>;
ti,hwmods = "mmc1";
@@ -518,7 +518,7 @@ mmc1: mmc@4809c000 {
};
mmc2: mmc@480b4000 {
- compatible = "ti,omap3-hsmmc";
+ compatible = "ti,omap3-sdhci";
reg = <0x480b4000 0x200>;
interrupts = <86>;
ti,hwmods = "mmc2";
@@ -527,7 +527,7 @@ mmc2: mmc@480b4000 {
};
mmc3: mmc@480ad000 {
- compatible = "ti,omap3-hsmmc";
+ compatible = "ti,omap3-sdhci";
reg = <0x480ad000 0x200>;
interrupts = <94>;
ti,hwmods = "mmc3";
--
2.43.0
next reply other threads:[~2024-02-13 12:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 12:41 Adam Ford [this message]
2024-02-13 12:56 ` [PATCH] arm: dts: omap3: Migrate hsmmc driver to sdhci driver Tony Lindgren
2024-02-13 13:02 ` Tony Lindgren
2024-02-13 13:29 ` Adam Ford
2024-02-13 13:36 ` Tony Lindgren
2024-02-13 13:52 ` Adam Ford
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=20240213124146.202391-1-aford173@gmail.com \
--to=aford173@gmail.com \
--cc=aford@beaconembedded.com \
--cc=bcousson@baylibre.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=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).