From: Peng Fan <peng.fan@oss.nxp.com>
To: "?????? (MW Park)" <mw.park@telechips.com>
Cc: "u-boot@lists.denx.de" <u-boot@lists.denx.de>,
"peng.fan@nxp.com" <peng.fan@nxp.com>,
"jh80.chung@samsung.com" <jh80.chung@samsung.com>
Subject: Re: [PATCH] mmc: allow forward compatibility for EXT_CSD_REV
Date: Thu, 9 Apr 2026 00:21:41 +0800 [thread overview]
Message-ID: <adaAlRvDAKs8mRWB@nxa18884-linux.ap.freescale.net> (raw)
In-Reply-To: <SLXP216MB114822C04834C4F0A78869A6F056A@SLXP216MB1148.KORP216.PROD.OUTLOOK.COM>
On Thu, Mar 26, 2026 at 05:55:32AM +0000, ?????? (MW Park) wrote:
>According to the JEDEC Standard, the EXT_CSD format is meant to be
>forward compatible. As long as CSD_STRUCTURE does not change, all
>values for EXT_CSD_REV are authorized.
>
>Currently, if an eMMC device with a newer EXT_CSD_REV (e.g., eMMC 5.1B
>with EXT_CSD_REV=9) is used, U-Boot fails to initialize it and returns
>-EINVAL because the revision is larger than the mmc_versions array size.
>
>Fix this by falling back to the latest supported version if the
>EXT_CSD_REV exceeds the known versions. This ensures forward
>compatibility with future eMMC specifications.
>
>Signed-off-by: MW Park <mw.park@telechips.com>
Would this patch works for you?
https://lore.kernel.org/u-boot/20260225211332.1896252-1-han.xu@nxp.com/
Regards,
Peng
next prev parent reply other threads:[~2026-04-08 15:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 5:55 [PATCH] mmc: allow forward compatibility for EXT_CSD_REV 박민우 (MW Park)
2026-04-08 16:21 ` Peng Fan [this message]
2026-04-09 1:23 ` 박민우 (MW Park)
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=adaAlRvDAKs8mRWB@nxa18884-linux.ap.freescale.net \
--to=peng.fan@oss.nxp.com \
--cc=jh80.chung@samsung.com \
--cc=mw.park@telechips.com \
--cc=peng.fan@nxp.com \
--cc=u-boot@lists.denx.de \
/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