From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Grzegorz Szymaszek <gszymaszek@short.pl>
Cc: "Ahmad Fatoum" <a.fatoum@pengutronix.de>,
"Marcin Słoniewski" <marcin.sloniewski@gmail.com>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH] ARM: dts: stm32: fix stm32mp157c-odyssey card detect pin
Date: Tue, 1 Jun 2021 11:27:03 +0200 [thread overview]
Message-ID: <74029811-6417-7c0b-1abd-6ea15de7f1ae@foss.st.com> (raw)
In-Reply-To: <YHH9+Xrn5Quge4Jt@nx64de-df6d00>
On 4/10/21 9:35 PM, Grzegorz Szymaszek wrote:
> The microSD card detect pin is physically connected to the MPU pin PI3.
> The Device Tree configuration of the card detect pin was wrong—it was
> set to pin PB7 instead. If such configuration was used, the kernel would
> hang on “Waiting for root device” when booting from a microSD card.
>
> Signed-off-by: Grzegorz Szymaszek <gszymaszek@short.pl>
> ---
> arch/arm/boot/dts/stm32mp157c-odyssey.dts | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/stm32mp157c-odyssey.dts b/arch/arm/boot/dts/stm32mp157c-odyssey.dts
> index a7ffec8f1516..be1dd5e9e744 100644
> --- a/arch/arm/boot/dts/stm32mp157c-odyssey.dts
> +++ b/arch/arm/boot/dts/stm32mp157c-odyssey.dts
> @@ -64,7 +64,7 @@ &sdmmc1 {
> pinctrl-0 = <&sdmmc1_b4_pins_a>;
> pinctrl-1 = <&sdmmc1_b4_od_pins_a>;
> pinctrl-2 = <&sdmmc1_b4_sleep_pins_a>;
> - cd-gpios = <&gpiob 7 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>;
> + cd-gpios = <&gpioi 3 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>;
> disable-wp;
> st,neg-edge;
> bus-width = <4>;
>
Hi Grzegorz
Applied on stm32-next.
Thanks.
Alex
prev parent reply other threads:[~2021-06-01 9:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 19:35 [PATCH] ARM: dts: stm32: fix stm32mp157c-odyssey card detect pin Grzegorz Szymaszek
2021-05-27 19:59 ` Grzegorz Szymaszek
2021-06-01 9:27 ` Alexandre TORGUE [this message]
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=74029811-6417-7c0b-1abd-6ea15de7f1ae@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=a.fatoum@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=gszymaszek@short.pl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=marcin.sloniewski@gmail.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@kernel.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).