devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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, frowand.list@gmail.com,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 3/9] ARM: dts: imx28: add alternative muxing for mmc2_sck_cfg
Date: Thu,  9 Feb 2017 08:42:43 +0100	[thread overview]
Message-ID: <1486626169-20022-4-git-send-email-michael.heimpold@i2se.com> (raw)
In-Reply-To: <1486626169-20022-1-git-send-email-michael.heimpold@i2se.com>

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.dtsi | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/arch/arm/boot/dts/imx28.dtsi b/arch/arm/boot/dts/imx28.dtsi
index 857ca37..5c65fa1 100644
--- a/arch/arm/boot/dts/imx28.dtsi
+++ b/arch/arm/boot/dts/imx28.dtsi
@@ -613,6 +613,15 @@
 					fsl,pull-up = <MXS_PULL_DISABLE>;
 				};
 
+				mmc2_sck_cfg_b: mmc2-sck-cfg@1 {
+					reg = <1>;
+					fsl,pinmux-ids = <
+						MX28_PAD_SSP2_SCK__SSP2_SCK
+					>;
+					fsl,drive-strength = <MXS_DRIVE_12mA>;
+					fsl,pull-up = <MXS_PULL_DISABLE>;
+				};
+
 				i2c0_pins_a: i2c0@0 {
 					reg = <0>;
 					fsl,pinmux-ids = <
-- 
2.6.1

  parent reply	other threads:[~2017-02-09  7:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-09  7:42 [PATCH v4 0/9] ARM: dts: support I2SE Duckbill devices Michael Heimpold
2017-02-09  7:42 ` [PATCH v4 1/9] ARM: dts: imx28: add alternative pinmuxing for mmc2 Michael Heimpold
2017-02-09  7:42 ` [PATCH v4 2/9] ARM: dts: imx28: rename mmc2_sck_cfg Michael Heimpold
2017-02-09  7:42 ` Michael Heimpold [this message]
2017-02-09  7:42 ` [PATCH v4 4/9] ARM: dts: imx28-duckbill: update to match vendor distributed DT Michael Heimpold
2017-02-09  7:42 ` [PATCH v4 5/9] dt-bindings: arm: add entries for I2SE boards Michael Heimpold
2017-02-15 23:28   ` Rob Herring
2017-02-09  7:42 ` [PATCH v4 6/9] ARM: dts: add support for I2SE Duckbill 2 boards Michael Heimpold
     [not found]   ` <1486626169-20022-7-git-send-email-michael.heimpold-eS4NqCHxEME@public.gmane.org>
2017-04-10  8:24     ` Shawn Guo
2017-04-10  9:08       ` [PATCH] ARM: mxs: " Michael Heimpold
2017-04-11 10:32         ` Shawn Guo
2017-02-09  7:42 ` [PATCH v4 7/9] ARM: dts: add support for I2SE Duckbill 2 485 Michael Heimpold
2017-02-09  7:42 ` [PATCH v4 8/9] ARM: dts: add support for I2SE Duckbill 2 EnOcean Michael Heimpold
2017-02-09  7:42 ` [PATCH v4 9/9] ARM: dts: add support for I2SE Duckbill 2 SPI Michael Heimpold
2017-02-10 14:45 ` [PATCH v4 0/9] ARM: dts: support I2SE Duckbill devices Stefan Wahren
     [not found] ` <1486626169-20022-1-git-send-email-michael.heimpold-eS4NqCHxEME@public.gmane.org>
2017-03-08 14:21   ` 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=1486626169-20022-4-git-send-email-michael.heimpold@i2se.com \
    --to=michael.heimpold@i2se.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabio.estevam@nxp.com \
    --cc=frowand.list@gmail.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).