From: Michael Haener <michael.haener@siemens.com>
To: Ulf Hansson <ulfh@kernel.org>
Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
Avri Altman <avri.altman@sandisk.com>,
Luke Wang <ziniu.wang_1@nxp.com>,
Michael Haener <michael.haener@siemens.com>
Subject: [PATCH 0/2] mmc: speed up secure erase on ISSI IS22TF128G eMMC
Date: Wed, 11 Nov 2026 13:07:57 +0100 [thread overview]
Message-ID: <20261111120759.100830-1-michael.haener@siemens.com> (raw)
Secure erasing a 33.5GiB partition on an ISSI IS22TF128G eMMC (NXP
i.MX8, sdhci-esdhc-imx) takes 5-7 hours, because the request is split
into roughly 10000 max_discard sized secure erase commands, each with a
large fixed overhead.
Patch 1 adds the card to MMC_QUIRK_FIXED_SECURE_ERASE_TRIM_TIME, which
brings the same operation down to about 6 minutes. It is tagged for
stable.
Patch 2 is hardening for the quirk: with qty no longer bound by
max_busy_timeout, the 32-bit erase timeout calculation can overflow for
cards with large ERASE_TIMEOUT_MULT * SEC_ERASE_MULT. None of the
currently quirked cards reach that limit (the ISSI card is at about
half of it), so it is not tagged for stable.
Michael Haener (2):
mmc: add ISSI IS22TF128G to fixed secure erase time quirk
mmc: core: saturate erase timeout instead of overflowing
drivers/mmc/core/card.h | 1 +
drivers/mmc/core/core.c | 19 ++++++++++++++-----
drivers/mmc/core/quirks.h | 9 +++++++++
3 files changed, 24 insertions(+), 5 deletions(-)
--
2.56.0
next reply other threads:[~2026-11-11 12:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 12:07 Michael Haener [this message]
2026-11-11 12:07 ` [PATCH 1/2] mmc: add ISSI IS22TF128G to fixed secure erase time quirk Michael Haener
2026-11-11 12:07 ` [PATCH 2/2] mmc: core: saturate erase timeout instead of overflowing Michael Haener
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=20261111120759.100830-1-michael.haener@siemens.com \
--to=michael.haener@siemens.com \
--cc=avri.altman@sandisk.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulfh@kernel.org \
--cc=ziniu.wang_1@nxp.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®