From: Andrea Merello <andrea.merello@gmail.com>
To: ulf.hansson@linaro.org, mcoquelin.stm32@gmail.com,
alexandre.torgue@st.com
Cc: linux-mmc@vger.kernel.org, bruherrera@gmail.com,
Andrea Merello <andrea.merello@gmail.com>
Subject: [PATCH v2 6/9] DT: stm32f429: add pin map for SDIO controller
Date: Tue, 10 Jan 2017 09:42:13 +0100 [thread overview]
Message-ID: <1484037736-25029-7-git-send-email-andrea.merello@gmail.com> (raw)
In-Reply-To: <1484037736-25029-1-git-send-email-andrea.merello@gmail.com>
Signed-off-by: Andrea Merello <andrea.merello@gmail.com>
---
arch/arm/boot/dts/stm32f429.dtsi | 33 ++++++++++++++++++++++++++++++++-
1 file changed, 32 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/stm32f429.dtsi b/arch/arm/boot/dts/stm32f429.dtsi
index e4dae0e..de7b9c3 100644
--- a/arch/arm/boot/dts/stm32f429.dtsi
+++ b/arch/arm/boot/dts/stm32f429.dtsi
@@ -336,7 +336,38 @@
};
};
- ethernet_mii: mii@0 {
+ sdio_pins: sdio_pins@0 {
+ pins {
+ pinmux = <STM32F429_PC8_FUNC_SDIO_D0>,
+ <STM32F429_PC9_FUNC_SDIO_D1>,
+ <STM32F429_PC10_FUNC_SDIO_D2>,
+ <STM32F429_PC11_FUNC_SDIO_D3>,
+ <STM32F429_PC12_FUNC_SDIO_CK>,
+ <STM32F429_PD2_FUNC_SDIO_CMD>;
+ drive-push-pull;
+ slew-rate = <2>;
+ };
+ };
+
+ sdio_pins_od: sdio_pins_od@0 {
+ pins1 {
+ pinmux = <STM32F429_PC8_FUNC_SDIO_D0>,
+ <STM32F429_PC9_FUNC_SDIO_D1>,
+ <STM32F429_PC10_FUNC_SDIO_D2>,
+ <STM32F429_PC11_FUNC_SDIO_D3>,
+ <STM32F429_PC12_FUNC_SDIO_CK>;
+ drive-push-pull;
+ slew-rate = <2>;
+ };
+
+ pins2 {
+ pinmux = <STM32F429_PD2_FUNC_SDIO_CMD>;
+ drive-open-drain;
+ slew-rate = <2>;
+ };
+ };
+
+ ethernet0_mii: mii@0 {
pins {
pinmux = <STM32F429_PG13_FUNC_ETH_MII_TXD0_ETH_RMII_TXD0>,
<STM32F429_PG14_FUNC_ETH_MII_TXD1_ETH_RMII_TXD1>,
--
2.7.4
next prev parent reply other threads:[~2017-01-10 8:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 8:42 [PATCH v2 0/9] mmc: mmci: add support for STM32 SD controller Andrea Merello
2017-01-10 8:42 ` [PATCH v2 1/9] mmc: mmci: don't pretend IP variants with only one IRQ to have two mask regs Andrea Merello
2017-01-10 8:42 ` [PATCH v2 2/9] mmc: mmci: add support for not-amba, but still compatible, variants Andrea Merello
2017-01-10 8:42 ` [PATCH v2 3/9] mmc: mmci: don't pretend all variants to have MCI_STARBITERR flag Andrea Merello
2017-01-10 8:42 ` [PATCH v2 4/9] mmc: mmci: add support for setting pad type via pinctrl Andrea Merello
2017-01-10 8:42 ` [PATCH v2 5/9] mmc: mmci: add STM32 variant Andrea Merello
2017-01-10 8:42 ` Andrea Merello [this message]
2017-01-10 9:06 ` [PATCH v2 6/9] DT: stm32f429: add pin map for SDIO controller Alexandre Torgue
2017-01-10 8:42 ` [PATCH v2 7/9] DT: stm32f429: add node " Andrea Merello
2017-01-10 9:15 ` Alexandre Torgue
2017-01-10 8:42 ` [PATCH v2 8/9] DT: stm32f469-disco: " Andrea Merello
2017-01-10 9:18 ` Alexandre Torgue
2017-01-12 7:25 ` Andrea Merello
2017-01-12 8:34 ` Alexandre Torgue
2017-01-12 8:53 ` Andrea Merello
2017-01-13 15:01 ` Andrea Merello
2017-01-13 15:52 ` Alexandre Torgue
2017-01-13 16:12 ` Andrea Merello
2017-01-13 16:28 ` Alexandre Torgue
2017-01-13 18:40 ` Andrea Merello
2017-01-10 8:42 ` [PATCH v2 9/9] Documentation: document mmci STM32 DT binding Andrea Merello
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=1484037736-25029-7-git-send-email-andrea.merello@gmail.com \
--to=andrea.merello@gmail.com \
--cc=alexandre.torgue@st.com \
--cc=bruherrera@gmail.com \
--cc=linux-mmc@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=ulf.hansson@linaro.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