From: "Andreas Färber" <afaerber@suse.de>
To: linux-arm-kernel@lists.infradead.org
Cc: "Shawn Guo" <shawnguo@kernel.org>,
"Sascha Hauer" <kernel@pengutronix.de>,
"Fabio Estevam" <fabio.estevam@nxp.com>,
"Ettore Chimenti" <ettore.chimenti@udoo.org>,
"Andreas Färber" <afaerber@suse.de>,
"Sudeep Holla" <sudeep.holla@arm.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Russell King" <linux@armlinux.org.uk>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: [PATCH 1/3] ARM: dts: imx6sx-sabreauto: Fix misspelled property
Date: Tue, 5 Jul 2016 06:04:08 +0200 [thread overview]
Message-ID: <1467691450-22975-2-git-send-email-afaerber@suse.de> (raw)
In-Reply-To: <1467691450-22975-1-git-send-email-afaerber@suse.de>
In commit 99fc5ba0bfb6 ("ARM: dts: imx6sx: add i.mx6sx sabreauto board
support") it should've been enable-sdio-wakeup (not -wakup). But that is
now considered a legacy name for wakeup-source, so directly use the new
name instead, as done in commit 26cefdd15db1 for the other occurrence.
Fixes: 26cefdd15db1 ("ARM: dts: imx: replace legacy wakeup property with 'wakeup-source'")
Cc: Sudeep Holla <sudeep.holla@arm.com>
Cc: Shawn Guo <shawnguo@kernel.org>
Signed-off-by: Andreas Färber <afaerber@suse.de>
---
arch/arm/boot/dts/imx6sx-sabreauto.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/imx6sx-sabreauto.dts b/arch/arm/boot/dts/imx6sx-sabreauto.dts
index 96ea936eeeb0..240a2864d044 100644
--- a/arch/arm/boot/dts/imx6sx-sabreauto.dts
+++ b/arch/arm/boot/dts/imx6sx-sabreauto.dts
@@ -64,7 +64,7 @@
cd-gpios = <&gpio7 11 GPIO_ACTIVE_LOW>;
no-1-8-v;
keep-power-in-suspend;
- enable-sdio-wakup;
+ wakeup-source;
status = "okay";
};
--
2.6.6
next prev parent reply other threads:[~2016-07-05 4:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 4:04 [PATCH 0/3] ARM: dts: imx6sx: Initial UDOO Neo enablement Andreas Färber
2016-07-05 4:04 ` Andreas Färber [this message]
[not found] ` <1467691450-22975-2-git-send-email-afaerber-l3A5Bk7waGM@public.gmane.org>
2016-07-05 8:54 ` [PATCH 1/3] ARM: dts: imx6sx-sabreauto: Fix misspelled property Sudeep Holla
2016-08-08 13:58 ` Shawn Guo
2016-07-05 4:04 ` [PATCH 2/3] ARM: dts: imx6sx: Add UDOO Neo support Andreas Färber
2016-07-05 6:27 ` Uwe Kleine-König
[not found] ` <20160705062736.GL16643-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2016-07-05 14:46 ` Andreas Färber
[not found] ` <1467691450-22975-3-git-send-email-afaerber-l3A5Bk7waGM@public.gmane.org>
2016-07-05 12:04 ` Fabio Estevam
2016-07-05 13:55 ` Andreas Färber
2016-07-05 18:33 ` Uwe Kleine-König
2016-08-08 14:04 ` Shawn Guo
[not found] ` <1467691450-22975-1-git-send-email-afaerber-l3A5Bk7waGM@public.gmane.org>
2016-07-05 4:04 ` [PATCH 3/3] ARM: dts: imx6sx-udoo-neo: Add SD Andreas Färber
2016-08-08 14:12 ` Shawn Guo
2016-08-08 15:00 ` Andreas Färber
[not found] ` <16912a4e-88c8-b11a-16bb-927ee6bf1775-l3A5Bk7waGM@public.gmane.org>
2016-08-15 12:38 ` 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=1467691450-22975-2-git-send-email-afaerber@suse.de \
--to=afaerber@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=ettore.chimenti@udoo.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=sudeep.holla@arm.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 NNTP newsgroup(s).