From: Luke Wang <ziniu.wang_1@nxp.com>

This patch series optimize secure erase performance for certain Kingston
eMMC devices (IY2964 and IB2932) that take a fixed ~2 seconds per secure
erase operation regardless of size.

Currently, a 1GB secure erase requires ~300 operations (limited by max
discard size), taking ~10 minutes. With these changes, the same secure
erase completes in a single operation, reducing time to just 2 seconds.

---
Changes in v4:
- Add back blk_queue_get_max_sectors() changes
Changes in v3:
- Refactor to use helper function __bio_split_discard()
Changes in v2:
- Rebased on v6.19-rc1 as requested
- Cover letter: terminology fix (command -> operation)
---

Luke Wang (2):
  block: decouple secure erase size limit from discard size limit
  mmc: add quirk to optimize certain Kingston eMMC secure erase/trim
    performance

 block/blk-merge.c         | 21 +++++++++++++++++----
 block/blk.h               |  6 +++++-
 drivers/mmc/core/card.h   |  5 +++++
 drivers/mmc/core/queue.c  |  9 +++++++--
 drivers/mmc/core/quirks.h |  9 +++++++++
 include/linux/mmc/card.h  |  1 +
 6 files changed, 44 insertions(+), 7 deletions(-)

-- 
2.34.1

On Wed, 04 Feb 2026 11:40:01 +0800, ziniu.wang_1@nxp.com wrote:
> This patch series optimize secure erase performance for certain Kingston
> eMMC devices (IY2964 and IB2932) that take a fixed ~2 seconds per secure
> erase operation regardless of size.
> 
> Currently, a 1GB secure erase requires ~300 operations (limited by max
> discard size), taking ~10 minutes. With these changes, the same secure
> erase completes in a single operation, reducing time to just 2 seconds.
> 
> [...]

Applied, thanks!

[1/2] block: decouple secure erase size limit from discard size limit
      commit: ee81212f74a57c5d2b56cf504f40d528dac6faaf

Best regards,
-- 
Jens Axboe