From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Grzegorz Szymaszek <gszymaszek@short.pl>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Ahmad Fatoum <a.fatoum@pengutronix.de>,
Marcin Sloniewski <marcin.sloniewski@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 the Odyssey SoM eMMC VQMMC supply
Date: Thu, 10 Jun 2021 15:46:10 +0200 [thread overview]
Message-ID: <af63b0d2-fce7-1e29-e36e-02da08f14d83@foss.st.com> (raw)
In-Reply-To: <YLj4AMTCi84yO9GO@nx64de-df6d00>
Hi
On 6/3/21 5:40 PM, Grzegorz Szymaszek wrote:
> The Seeed SoM-STM32MP157C device tree had the eMMC’s (SDMMC2) VQMMC
> supply set to v3v3 (buck4), the same as the VMMC supply. That was
> incorrect, as on the SoM, the VQMMC supply is provided from vdd (buck3)
> instead.
>
> Signed-off-by: Grzegorz Szymaszek <gszymaszek@short.pl>
> ---
> arch/arm/boot/dts/stm32mp157c-odyssey-som.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/stm32mp157c-odyssey-som.dtsi b/arch/arm/boot/dts/stm32mp157c-odyssey-som.dtsi
> index 6cf49a0a9e69..b5601d270c8f 100644
> --- a/arch/arm/boot/dts/stm32mp157c-odyssey-som.dtsi
> +++ b/arch/arm/boot/dts/stm32mp157c-odyssey-som.dtsi
> @@ -269,7 +269,7 @@ &sdmmc2 {
> st,neg-edge;
> bus-width = <8>;
> vmmc-supply = <&v3v3>;
> - vqmmc-supply = <&v3v3>;
> + vqmmc-supply = <&vdd>;
> mmc-ddr-3_3v;
> status = "okay";
> };
>
Applied on stm32-next.
Thanks.
Alex
prev parent reply other threads:[~2021-06-10 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 15:40 [PATCH] ARM: dts: stm32: fix the Odyssey SoM eMMC VQMMC supply Grzegorz Szymaszek
2021-06-10 13:46 ` 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=af63b0d2-fce7-1e29-e36e-02da08f14d83@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).