From: "Andreas Färber" <afaerber@suse.de>
To: linux-samsung-soc@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
"Stephan van Schaik" <stephan@synkhronix.com>,
"Vincent Palatin" <vpalatin@chromium.org>,
"Doug Anderson" <dianders@chromium.org>,
"Javier Martinez Canillas" <javier.martinez@collabora.co.uk>,
"Andreas Färber" <afaerber@suse.de>,
"Jaehoon Chung" <jh80.chung@samsung.com>,
"Ben Dooks" <ben-linux@fluff.org>,
"Kukjin Kim" <kgene.kim@samsung.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Pawel Moll" <pawel.moll@arm.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
"Kumar Gala" <galak@codeaurora.org>,
"Russell King" <linux@arm.linux.org.uk>,
"open list" <linux-kernel@vger.kernel.org>
Subject: [PATCH v3 1/4] ARM: dts: Fix MMC pinctrl for exynos5250-snow
Date: Wed, 30 Jul 2014 15:50:41 +0200 [thread overview]
Message-ID: <1406728244-5105-2-git-send-email-afaerber@suse.de> (raw)
In-Reply-To: <1406728244-5105-1-git-send-email-afaerber@suse.de>
The pinctrl properties should be on the device directly and not on the
slot sub-node.
Reported-by: Doug Anderson <dianders@chromium.org>
Cc: Jaehoon Chung <jh80.chung@samsung.com>
Signed-off-by: Andreas Färber <afaerber@suse.de>
---
v3: New (Doug Anderson)
Redundant with Jaehoon Chung's general slot@0 deprecation,
in case that hits the tree earlier.
arch/arm/boot/dts/exynos5250-snow.dts | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/arch/arm/boot/dts/exynos5250-snow.dts b/arch/arm/boot/dts/exynos5250-snow.dts
index f2b8c4116541..eb437f6afec1 100644
--- a/arch/arm/boot/dts/exynos5250-snow.dts
+++ b/arch/arm/boot/dts/exynos5250-snow.dts
@@ -240,10 +240,8 @@
*/
mmc@12230000 {
status = "okay";
- slot@0 {
- pinctrl-names = "default";
- pinctrl-0 = <&sd3_clk &sd3_cmd &sd3_bus4>;
- };
+ pinctrl-names = "default";
+ pinctrl-0 = <&sd3_clk &sd3_cmd &sd3_bus4>;
};
i2c@12CD0000 {
--
1.9.3
next prev parent reply other threads:[~2014-07-30 13:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 13:50 [PATCH v3 0/4] ARM: dts: exynos: Prepare Spring Andreas Färber
2014-07-30 13:50 ` Andreas Färber [this message]
2014-07-30 13:50 ` [PATCH v3 2/4] ARM: dts: Fold exynos5250-cros-common into exynos5250-snow Andreas Färber
2014-07-30 13:50 ` [PATCH v3 3/4] ARM: dts: Clean up exynos5250-snow Andreas Färber
2014-07-30 13:50 ` [PATCH v3 4/4] ARM: dts: Add exynos5250-spring device tree Andreas Färber
[not found] ` <1406728244-5105-5-git-send-email-afaerber-l3A5Bk7waGM@public.gmane.org>
2014-07-31 9:26 ` Andreas Färber
2014-07-31 9:49 ` Ajay kumar
[not found] ` <CAEC9eQNuPN+WiKGOtCosCwcR48MNawQL7dU4S8=dbA4eFXB_-w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-31 9:53 ` Andreas Färber
2014-07-31 10:01 ` Ajay kumar
2014-07-30 14:17 ` [PATCH v3 0/4] ARM: dts: exynos: Prepare Spring Andreas Färber
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=1406728244-5105-2-git-send-email-afaerber@suse.de \
--to=afaerber@suse.de \
--cc=ben-linux@fluff.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=javier.martinez@collabora.co.uk \
--cc=jh80.chung@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=stephan@synkhronix.com \
--cc=vpalatin@chromium.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).