From: Kishon Vijay Abraham I <kishon@ti.com>
To: Tony Lindgren <tony@atomide.com>,
Rob Herring <robh+dt@kernel.org>, <nsekhar@ti.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Russell King <linux@armlinux.org.uk>,
<linux-omap@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-mmc@vger.kernel.org>,
<kishon@ti.com>
Subject: [PATCH v2 4/8] ARM: dts: am57xx-beagle-x15-revb1: Fix supply name used for MMC1 IO lines
Date: Wed, 7 Jun 2017 15:07:45 +0530 [thread overview]
Message-ID: <20170607093749.15656-5-kishon@ti.com> (raw)
In-Reply-To: <20170607093749.15656-1-kishon@ti.com>
The dt binding documentation of omap-hsmmc recommends using
"vmmc_aux" for IO supply lines. However
commit 0af28cc92690d8c ("ARM: dts: am57xx-beagle-x15: Add support
for rev B1") added it as "vmmc-aux". Now that anyways it
needs to be fixed, use the generic "vqmmc" binding instead of
the deprecated "vmmc_aux".
Fixes: commit 0af28cc92690d8c ("ARM: dts: am57xx-beagle-x15: Add
support for rev B1")
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
---
arch/arm/boot/dts/am57xx-beagle-x15-revb1.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/am57xx-beagle-x15-revb1.dts b/arch/arm/boot/dts/am57xx-beagle-x15-revb1.dts
index 39a92aff0a0d..578398c781b1 100644
--- a/arch/arm/boot/dts/am57xx-beagle-x15-revb1.dts
+++ b/arch/arm/boot/dts/am57xx-beagle-x15-revb1.dts
@@ -20,7 +20,7 @@
&mmc1 {
vmmc-supply = <&vdd_3v3>;
- vmmc-aux-supply = <&ldo1_reg>;
+ vqmmc-supply = <&ldo1_reg>;
};
/* errata i880 "Ethernet RGMII2 Limited to 10/100 Mbps" */
--
2.11.0
next prev parent reply other threads:[~2017-06-07 9:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 9:37 [PATCH v2 0/8] omap*: Fixes/Cleanups for MMC devicetree node Kishon Vijay Abraham I
2017-06-07 9:37 ` [PATCH v2 1/8] ARM: dts: dra72-evm-common: Correct vmmc-supply for mmc2 Kishon Vijay Abraham I
2017-06-07 9:37 ` [PATCH v2 2/8] ARM: dts: dra72-evm: Add vqmmc supply to mmc1 Kishon Vijay Abraham I
2017-06-07 9:37 ` [PATCH v2 3/8] ARM: dts: dra72-evm-revc: " Kishon Vijay Abraham I
2017-06-07 9:37 ` Kishon Vijay Abraham I [this message]
2017-06-07 9:37 ` [PATCH v2 5/8] ARM: dts: dra7-evm: Correct the vmmc-supply for mmc2 Kishon Vijay Abraham I
2017-06-07 9:37 ` [PATCH v2 6/8] ARM: dts: dra7: Add "max-frequency" property to MMC dt nodes Kishon Vijay Abraham I
2017-06-07 9:37 ` [PATCH v2 7/8] ARM: OMAP2+: Add pdata-quirks for MMC/SD on DRA74x EVM Kishon Vijay Abraham I
2017-06-07 9:37 ` [PATCH v2 8/8] ARM: dts: omap*: Replace deprecated "vmmc_aux" with "vqmmc" Kishon Vijay Abraham I
2017-06-09 12:08 ` [PATCH v3] " Kishon Vijay Abraham I
2017-06-08 7:20 ` [PATCH v2 0/8] omap*: Fixes/Cleanups for MMC devicetree node Ulf Hansson
2017-06-08 8:46 ` Tony Lindgren
2017-06-09 12:21 ` Kishon Vijay Abraham I
2017-06-09 8:05 ` Kishon Vijay Abraham I
2017-06-09 10:41 ` Ulf Hansson
2017-08-03 11:18 ` Kishon Vijay Abraham I
2017-08-07 6:48 ` Tony Lindgren
2017-08-10 16:13 ` Tony Lindgren
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=20170607093749.15656-5-kishon@ti.com \
--to=kishon@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.com \
--cc=ulf.hansson@linaro.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