From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>
Cc: linux-tegra@vger.kernel.org
Subject: [PATCH v1 1/3] ARM: tegra: nexus7: Add aliases for MMC
Date: Sun, 6 Sep 2020 22:00:06 +0300 [thread overview]
Message-ID: <20200906190008.25247-1-digetx@gmail.com> (raw)
MMC core now supports binding to a specific ID, which is very handy for
embedded devices, like Nexus 7, because MMC ID may change depending on
kernel version or configuration which affects MMC driver probe order.
Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
---
arch/arm/boot/dts/tegra30-asus-nexus7-grouper-common.dtsi | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/tegra30-asus-nexus7-grouper-common.dtsi b/arch/arm/boot/dts/tegra30-asus-nexus7-grouper-common.dtsi
index 21387a91c40f..ca44f9596753 100644
--- a/arch/arm/boot/dts/tegra30-asus-nexus7-grouper-common.dtsi
+++ b/arch/arm/boot/dts/tegra30-asus-nexus7-grouper-common.dtsi
@@ -16,6 +16,9 @@ aliases {
serial1 = &uartc; /* Bluetooth */
serial2 = &uartb; /* GPS */
+
+ mmc0 = &sdmmc4; /* eMMC */
+ mmc1 = &sdmmc3; /* WiFi */
};
/*
@@ -970,7 +973,7 @@ brcm_wifi_pwrseq: wifi-pwrseq {
power-off-delay-us = <300>;
};
- mmc@78000400 {
+ sdmmc3: mmc@78000400 {
status = "okay";
#address-cells = <1>;
@@ -999,7 +1002,7 @@ wifi@1 {
};
};
- mmc@78000600 {
+ sdmmc4: mmc@78000600 {
status = "okay";
bus-width = <8>;
vmmc-supply = <&vcore_emmc>;
--
2.27.0
next reply other threads:[~2020-09-06 19:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-06 19:00 Dmitry Osipenko [this message]
2020-09-06 19:00 ` [PATCH v1 2/3] ARM: tegra: acer-a500: Add aliases for MMC Dmitry Osipenko
2020-09-17 10:17 ` Thierry Reding
2020-09-06 19:00 ` [PATCH v1 3/3] ARM: tegra: acer-a500: Remove atmel,cfg_name property Dmitry Osipenko
2020-09-17 10:17 ` Thierry Reding
2020-09-17 10:17 ` [PATCH v1 1/3] ARM: tegra: nexus7: Add aliases for MMC Thierry Reding
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=20200906190008.25247-1-digetx@gmail.com \
--to=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@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