From: Christophe KERELLO <christophe.kerello@foss.st.com>
To: Mateusz Nowicki <mateusz.nowicki@posteo.net>,
Ulf Hansson <ulfh@kernel.org>, <linux-mmc@vger.kernel.org>
Cc: Russell King <linux@armlinux.org.uk>,
Linus Walleij <linusw@kernel.org>,
Yann Gautier <yann.gautier@foss.st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH v2 3/5] mmc: mmci: stm32: use the delay block above 100 MHz on stm32mp25 SoC
Date: Thu, 5 Nov 2026 09:17:08 +0100 [thread overview]
Message-ID: <4f90060d-6eae-4cf9-9533-6adc51f52423@foss.st.com> (raw)
In-Reply-To: <20261104152657.14909-4-mateusz.nowicki@posteo.net>
Hello Mateusz,
On 11/4/26 16:27, Mateusz Nowicki wrote:
> From: Christophe Kerello<christophe.kerello@foss.st.com>
>
> On stm32mp25 SoC, the delay block has to be used only for an external
> data frequency above 100 MHz. Skip the tuning up to that frequency, keep
> 50 MHz for stm32mp15 as before.
>
> Fixes: b5c3eb385797 ("mmc: mmci: stm32: add delay block support for STM32MP25")
> Cc:stable@vger.kernel.org
> Signed-off-by: Christophe Kerello<christophe.kerello@foss.st.com>
> [Mateusz: reworded the commit message, check dlyb before reading
> min_freq, added Fixes and Cc stable]
Thanks for the fix.
> Signed-off-by: Mateusz Nowicki<mateusz.nowicki@posteo.net>
> ---
>
> Notes:
> On the STM32MP257F-DK (SDMMC2 kernel clock 200 MHz, eMMC in HS200 at
> 100 MHz) the writes failed with I/O errors in all 9 test runs without
> this change, with sdmmc2 pins_a or pins_b and with or without NEGEDGE.
> With it all 6 runs were correct, on both pin groups.
>
> drivers/mmc/host/mmci_stm32_sdmmc.c | 16 +++++++++++-----
> 1 file changed, 11 insertions(+), 5 deletions(-)
Reviewed-by: Christophe Kerello <christophe.kerello@foss.st.com>
Regards,
Christophe Kerello.
next prev parent reply other threads:[~2026-11-05 8:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 15:27 [PATCH v2 0/5] mmc: mmci: stm32: silent data corruption and HS200 fixes Mateusz Nowicki
2026-11-04 15:27 ` [PATCH v2 1/5] mmc: mmci: do not count a data CRC error as a complete transfer Mateusz Nowicki
2026-11-04 15:27 ` [PATCH v2 2/5] mmc: mmci: stm32: release the delay block before enabling it Mateusz Nowicki
2026-11-05 8:16 ` Christophe KERELLO
2026-11-04 15:27 ` [PATCH v2 3/5] mmc: mmci: stm32: use the delay block above 100 MHz on stm32mp25 SoC Mateusz Nowicki
2026-11-05 8:17 ` Christophe KERELLO [this message]
2026-11-04 15:27 ` [PATCH v2 4/5] arm64: dts: st: use sdmmc2 pins_a on stm32mp257f-dk Mateusz Nowicki
2026-11-05 8:18 ` Christophe KERELLO
2026-11-04 15:27 ` [PATCH v2 5/5] arm64: dts: st: remove sdmmc2 pins_b from stm32mp25 Mateusz Nowicki
2026-11-05 8:18 ` Christophe KERELLO
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=4f90060d-6eae-4cf9-9533-6adc51f52423@foss.st.com \
--to=christophe.kerello@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=mateusz.nowicki@posteo.net \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh@kernel.org \
--cc=stable@vger.kernel.org \
--cc=ulfh@kernel.org \
--cc=yann.gautier@foss.st.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
all inboxes | Powered by JetHome®