From: Peter Korsgaard <peter@korsgaard.com>
To: Avri Altman <Avri.Altman@sandisk.com>
Cc: Shawn Lin <shawn.lin@rock-chips.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Avri Altman <avri.altman@wdc.com>,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH 1/2] mmc-utils: lsmmc.c: print_mmc_cid(): correct year/month parsing
Date: Wed, 05 Nov 2025 21:16:48 +0100 [thread overview]
Message-ID: <87jz046xqn.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <PH7PR16MB619676787C5B72C51598EFEBE5C5A@PH7PR16MB6196.namprd16.prod.outlook.com> (Avri Altman's message of "Wed, 5 Nov 2025 19:57:58 +0000")
>>>>> "Avri" == Avri Altman <Avri.Altman@sandisk.com> writes:
Hi,
> Yeah - they noticed that as well and proposed a similar approach by
> extending the ext-csd-rev to 9.0. I had the code ready for a while
> now but somehow failed to submit it yet. Here it is.
Ahh, great!
> Thanks for fixing the year-month misplacement.
> Thanks,
> Avri
> From c0e5ec1d3670161444943c8984b6cdafb82fac67 Mon Sep 17 00:00:00 2001
> From: Avri Altman <avri.altman@sandisk.com>
> Date: Thu, 13 Mar 2025 10:10:49 +0200
> Subject: [PATCH] mmc: core: Adjust MDT beyond 2025
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
> JEDEC JC64.1 proposal, which was recently approved, increases the
> manufacturing year limit for eMMC devices. The eMMC manufacturing year
> is stored in a 4-bit field in the CID register. Originally, it covered
> 1997–2012. Later, with EXT_CSD_REV=8, it was extended up to 2025. Now,
> with EXT_CSD_REV=9, the range is rolled over by another 16 years, up to
> 2038.
> The mapping is as follows:
> | cid[8..11] | ver ≤ 4 | rev > 4 | rev > 8 |
> |------------|---------|---------|---------|
> | 0 | 1997 | 2013 | 2029 |
> | 1 | 1998 | 2014 | 2030 |
> | 2 | 1999 | 2015 | 2031 |
> | 3 | 2000 | 2016 | 2032 |
> | 4 | 2001 | 2017 | 2033 |
> | 5 | 2002 | 2018 | 2034 |
> | 6 | 2003 | 2019 | 2035 |
> | 7 | 2004 | 2020 | 2036 |
> | 8 | 2005 | 2021 | 2037 |
> | 9 | 2006 | 2022 | 2038 |
> | 10 | 2007 | 2023 | |
> | 11 | 2008 | 2024 | |
> | 12 | 2009 | 2025 | |
> | 13 | 2010 | | 2026 |
> | 14 | 2011 | | 2027 |
> | 15 | 2012 | | 2028 |
> Signed-off-by: Avri Altman <avri.altman@sandisk.com>
Acked-by: Peter Korsgaard <peter@korsgaard.com>
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2025-11-05 20:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 20:00 [PATCH 1/2] mmc-utils: lsmmc.c: print_mmc_cid(): correct year/month parsing Peter Korsgaard
2025-11-04 20:00 ` [PATCH 2/2] mmc-utils: lsmmc.c: print_{mmc,sd}_cid(): correct month names Peter Korsgaard
2025-11-11 17:36 ` Ulf Hansson
2025-11-05 2:04 ` [PATCH 1/2] mmc-utils: lsmmc.c: print_mmc_cid(): correct year/month parsing Shawn Lin
2025-11-05 6:56 ` Peter Korsgaard
2025-11-05 7:07 ` Peter Korsgaard
2025-11-05 7:23 ` Shawn Lin
2025-11-05 19:57 ` Avri Altman
2025-11-05 20:16 ` Peter Korsgaard [this message]
2025-11-07 1:39 ` Shawn Lin
2025-11-11 17:26 ` Ulf Hansson
2025-11-11 17:36 ` 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=87jz046xqn.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=Avri.Altman@sandisk.com \
--cc=avri.altman@wdc.com \
--cc=linux-mmc@vger.kernel.org \
--cc=shawn.lin@rock-chips.com \
--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