From: Avri Altman <avri.altman@gmail.com>
To: Ulf Hansson <ulf.hansson@linaro.org>, linux-mmc@vger.kernel.org
Cc: Avri Altman <avri.altman@sandisk.com>
Subject: [PATCH v2 0/2] mmc: core: Extend manufacturing date beyond 2025
Date: Fri, 28 Nov 2025 07:20:09 +0200 [thread overview]
Message-ID: <20251128052011.204735-1-avri.altman@sandisk.com> (raw)
Hi Ulf,
This patch series addresses the upcoming exhaustion of the eMMC
manufacturing date (MDT) year field, which is limited to a 4-bit value
in the CID register. Under the current standard (EXT_CSD_REV=8), the
representable years end in 2025.
The first patch implements the recently approved JEDEC standard update
for EXT_CSD_REV=9. This update rolls over the 4-bit year codes to cover
a new 16-year period, extending the range up to 2038.
The second patch introduces a quirk to handle vendor-specific behavior.
Some eMMC vendors are not yet updating their devices to EXT_CSD_REV=9
but still need to report manufacturing dates for 2026 and beyond. These
devices re-purpose the year codes for 2010-2012 to represent 2026-2028.
Thanks,
Avri
---
Changes in v2:
- move the fixup to `mmc_ext_csd_fixups`
- State the correct spec release
- Fixed a typo in the commit message of the second patch.
---
Avri Altman (2):
mmc: core: Adjust MDT beyond 2025
mmc: core: Add quirk for incorrect manufacturing date
drivers/mmc/core/card.h | 6 ++++++
drivers/mmc/core/mmc.c | 12 ++++++++++++
drivers/mmc/core/quirks.h | 3 +++
include/linux/mmc/card.h | 1 +
4 files changed, 22 insertions(+)
--
2.34.1
next reply other threads:[~2025-11-28 5:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 5:20 Avri Altman [this message]
2025-11-28 5:20 ` [PATCH v2 1/2] mmc: core: Adjust MDT beyond 2025 Avri Altman
2025-11-28 5:20 ` [PATCH v2 2/2] mmc: core: Add quirk for incorrect manufacturing date Avri Altman
2025-12-08 9:34 ` [PATCH v2 0/2] mmc: core: Extend manufacturing date beyond 2025 Avri Altman
2025-12-09 11:42 ` Ulf Hansson
2025-12-15 15:43 ` Ulf Hansson
2025-12-15 16:28 ` Avri Altman
2025-12-17 13:44 ` Ulf Hansson
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=20251128052011.204735-1-avri.altman@sandisk.com \
--to=avri.altman@gmail.com \
--cc=avri.altman@sandisk.com \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.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