From: Stefan Agner <stefan@agner.ch>
To: shawnguo@kernel.org, s.hauer@pengutronix.de
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
max.krummenacher@toradex.com, marcel.ziswiler@toradex.com,
linux-kernel@vger.kernel.org, Stefan Agner <stefan@agner.ch>,
maitysanchayan@gmail.com, robh+dt@kernel.org, linux-imx@nxp.com,
kernel@pengutronix.de, fabio.estevam@nxp.com,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/8] ARM: dts: imx6qdl-apalis/-colibri: disable read-only switch
Date: Mon, 9 Jul 2018 17:48:44 +0200 [thread overview]
Message-ID: <20180709154848.5401-4-stefan@agner.ch> (raw)
In-Reply-To: <20180709154848.5401-1-stefan@agner.ch>
Use the disable-wp to indicate that Apalis and Colibri iMX6 do not
make use of the native write-protect signal available on the i.MX 6
SoCs. This prevents warnings:
mmc0: host does not support reading read-only switch, assuming write-enable
Signed-off-by: Stefan Agner <stefan@agner.ch>
---
arch/arm/boot/dts/imx6qdl-apalis.dtsi | 2 ++
arch/arm/boot/dts/imx6qdl-colibri.dtsi | 1 +
2 files changed, 3 insertions(+)
diff --git a/arch/arm/boot/dts/imx6qdl-apalis.dtsi b/arch/arm/boot/dts/imx6qdl-apalis.dtsi
index 55bcea245df6..f9bacc9ff2b6 100644
--- a/arch/arm/boot/dts/imx6qdl-apalis.dtsi
+++ b/arch/arm/boot/dts/imx6qdl-apalis.dtsi
@@ -457,6 +457,7 @@
pinctrl-0 = <&pinctrl_usdhc1_4bit &pinctrl_usdhc1_8bit>;
vqmmc-supply = <®_3p3v>;
bus-width = <8>;
+ disable-wp;
no-1-8-v;
status = "disabled";
};
@@ -467,6 +468,7 @@
pinctrl-0 = <&pinctrl_usdhc2>;
vqmmc-supply = <®_3p3v>;
bus-width = <4>;
+ disable-wp;
no-1-8-v;
status = "disabled";
};
diff --git a/arch/arm/boot/dts/imx6qdl-colibri.dtsi b/arch/arm/boot/dts/imx6qdl-colibri.dtsi
index bb44829dacbe..8ae17fdf6cf6 100644
--- a/arch/arm/boot/dts/imx6qdl-colibri.dtsi
+++ b/arch/arm/boot/dts/imx6qdl-colibri.dtsi
@@ -387,6 +387,7 @@
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_usdhc1 &pinctrl_mmc_cd>;
cd-gpios = <&gpio2 5 GPIO_ACTIVE_LOW>; /* MMCD */
+ disable-wp;
vqmmc-supply = <®_3p3v>;
bus-width = <4>;
no-1-8-v;
--
2.18.0
next prev parent reply other threads:[~2018-07-09 15:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 15:48 [PATCH 1/8] ARM: dts: imx6q-apalis: add chosen node Stefan Agner
2018-07-09 15:48 ` [PATCH 2/8] ARM: dts: imx6q-apalis-eval: add carrier board 3.3V supply Stefan Agner
2018-07-09 15:48 ` [PATCH 3/8] ARM: dts: imx6qdl-apalis/-colibri: prevent 1.8V modes Stefan Agner
2018-07-09 15:48 ` Stefan Agner [this message]
2018-07-09 15:48 ` [PATCH 5/8] ARM: dts: imx6qdl-apalis/-colibri: remove 1.8V regulator Stefan Agner
2018-07-09 15:48 ` [PATCH 6/8] ARM: dts: imx6qdl-apalis/-colibri: fix on-module regulators Stefan Agner
2018-07-09 15:48 ` [PATCH 7/8] ARM: dts: imx6qdl-apalis/-colibri: assign VDDD to SGTL5000 Stefan Agner
2018-07-09 15:48 ` [PATCH 8/8] ARM: dts: imx6qdl-apalis/-colibri: remove unused pinctrl groups Stefan Agner
2018-07-11 13:01 ` [PATCH 1/8] ARM: dts: imx6q-apalis: add chosen node Shawn Guo
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=20180709154848.5401-4-stefan@agner.ch \
--to=stefan@agner.ch \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maitysanchayan@gmail.com \
--cc=marcel.ziswiler@toradex.com \
--cc=mark.rutland@arm.com \
--cc=max.krummenacher@toradex.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.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;
as well as URLs for NNTP newsgroup(s).