From: Michael Heimpold <michael.heimpold@i2se.com>
To: shawnguo@kernel.org, kernel@pengutronix.de, robh+dt@kernel.org,
mark.rutland@arm.com
Cc: stefan.wahren@i2se.com, devicetree@vger.kernel.org,
Michael Heimpold <michael.heimpold@i2se.com>,
fabio.estevam@nxp.com, linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/9] ARM: dts: imx28: rename mmc2_sck_cfg
Date: Tue, 31 Jan 2017 07:51:08 +0100 [thread overview]
Message-ID: <1485845475-3129-3-git-send-email-michael.heimpold@i2se.com> (raw)
In-Reply-To: <1485845475-3129-1-git-send-email-michael.heimpold@i2se.com>
This patch renames mmc2_sck_cfg in order to prepare for an alternative
muxing setup.
Signed-off-by: Michael Heimpold <michael.heimpold@i2se.com>
Cc: Stefan Wahren <stefan.wahren@i2se.com>
Acked-by: Stefan Wahren <stefan.wahren@i2se.com>
---
arch/arm/boot/dts/imx28-m28cu3.dts | 2 +-
arch/arm/boot/dts/imx28.dtsi | 3 ++-
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/imx28-m28cu3.dts b/arch/arm/boot/dts/imx28-m28cu3.dts
index 2df63be..bb53294 100644
--- a/arch/arm/boot/dts/imx28-m28cu3.dts
+++ b/arch/arm/boot/dts/imx28-m28cu3.dts
@@ -57,7 +57,7 @@
pinctrl-names = "default";
pinctrl-0 = <&mmc2_4bit_pins_a
&mmc2_cd_cfg
- &mmc2_sck_cfg>;
+ &mmc2_sck_cfg_a>;
bus-width = <4>;
vmmc-supply = <®_vddio_sd1>;
status = "okay";
diff --git a/arch/arm/boot/dts/imx28.dtsi b/arch/arm/boot/dts/imx28.dtsi
index bc5cf41..857ca37 100644
--- a/arch/arm/boot/dts/imx28.dtsi
+++ b/arch/arm/boot/dts/imx28.dtsi
@@ -604,7 +604,8 @@
fsl,pull-up = <MXS_PULL_DISABLE>;
};
- mmc2_sck_cfg: mmc2-sck-cfg {
+ mmc2_sck_cfg_a: mmc2-sck-cfg@0 {
+ reg = <0>;
fsl,pinmux-ids = <
MX28_PAD_SSP0_DATA7__SSP2_SCK
>;
--
2.6.1
next prev parent reply other threads:[~2017-01-31 6:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 6:51 [PATCH v3 0/9] ARM: dts: support I2SE Duckbill devices Michael Heimpold
2017-01-31 6:51 ` [PATCH v3 1/9] ARM: dts: imx28: add alternative pinmuxing for mmc2 Michael Heimpold
2017-01-31 6:51 ` Michael Heimpold [this message]
2017-01-31 6:51 ` [PATCH v3 3/9] ARM: dts: imx28: add alternative muxing for mmc2_sck_cfg Michael Heimpold
[not found] ` <1485845475-3129-1-git-send-email-michael.heimpold-eS4NqCHxEME@public.gmane.org>
2017-01-31 6:51 ` [PATCH v3 4/9] ARM: dts: imx28-duckbill: update to match vendor distributed DT Michael Heimpold
2017-01-31 6:51 ` [PATCH v3 5/9] Documentation: DT: add entries for I2SE boards Michael Heimpold
[not found] ` <1485845475-3129-6-git-send-email-michael.heimpold-eS4NqCHxEME@public.gmane.org>
2017-02-01 17:18 ` Rob Herring
2017-02-08 6:43 ` Michael Heimpold
[not found] ` <769dba11-e290-50e0-d894-9f4ea08eb652-eS4NqCHxEME@public.gmane.org>
2017-02-08 14:37 ` Rob Herring
2017-01-31 6:51 ` [PATCH v3 6/9] ARM: dts: add support for I2SE Duckbill 2 boards Michael Heimpold
2017-01-31 6:51 ` [PATCH v3 7/9] ARM: dts: add support for I2SE Duckbill 2 485 Michael Heimpold
2017-01-31 6:51 ` [PATCH v3 8/9] ARM: dts: add support for I2SE Duckbill 2 EnOcean Michael Heimpold
2017-01-31 6:51 ` [PATCH v3 9/9] ARM: dts: add support for I2SE Duckbill 2 SPI Michael Heimpold
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=1485845475-3129-3-git-send-email-michael.heimpold@i2se.com \
--to=michael.heimpold@i2se.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=stefan.wahren@i2se.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).