From: Marek Vasut <marex@denx.de>
To: Ulf Hansson <ulf.hansson@linaro.org>,
Adrian Hunter <adrian.hunter@intel.com>
Cc: linux-mmc@vger.kernel.org,
"Christian Löhle" <CLoehle@hyperstone.com>,
"Avri Altman" <avri.altman@wdc.com>,
"Jens Axboe" <axboe@kernel.dk>,
"Michael Wu" <michael@allwinnertech.com>,
"Ming Lei" <ming.lei@redhat.com>,
"Seunghui Lee" <sh043.lee@samsung.com>,
xander_li@kingston.com.tw
Subject: Re: [PATCH] [RFC] Revert "mmc: core: Fixup support for writeback-cache for eMMC and SD"
Date: Fri, 16 Jun 2023 12:20:51 +0200 [thread overview]
Message-ID: <4a8ae652-b930-3cd3-00df-c6dd1dd2a31d@denx.de> (raw)
In-Reply-To: <CAPDyKFoe0WWs2-wSETMZR5shjmWnLfD4GPwOXJNhyKd8xntq8A@mail.gmail.com>
On 6/15/23 17:14, Ulf Hansson wrote:
I finally got around testing the other card, there are changes in CSD
and SSR which indicate there was a HW change, but nothing significant.
Considering we still have a non-working card sample size 1, I wonder
whether I should just consider this card defective and archive it. Or
would you prefer a quirk based on manufacturing date ? I am also CCing
Xander, maybe they can check internally at Kingston .
Old 2019 card:
--------------
mmc1: host does not support reading read-only switch, assuming write-enable
mmc1: new ultra high speed SDR104 SDXC card at address 5048
mmcblk1: mmc1:5048 SD64G 58.0 GiB
mmcblk1: p1
~ # grep -H . /sys/class/mmc_host/mmc1/mmc1\:5048/*
/sys/class/mmc_host/mmc1/mmc1:5048/cid:9f544953443634476136980065013b00
/sys/class/mmc_host/mmc1/mmc1:5048/csd:400e00325b590001cfff7f800a400000
/sys/class/mmc_host/mmc1/mmc1:5048/date:11/2019
/sys/class/mmc_host/mmc1/mmc1:5048/dsr:0x404
/sys/class/mmc_host/mmc1/mmc1:5048/erase_size:512
/sys/class/mmc_host/mmc1/mmc1:5048/fwrev:0x1
/sys/class/mmc_host/mmc1/mmc1:5048/hwrev:0x6
/sys/class/mmc_host/mmc1/mmc1:5048/manfid:0x00009f
/sys/class/mmc_host/mmc1/mmc1:5048/name:SD64G
/sys/class/mmc_host/mmc1/mmc1:5048/ocr:0x00300000
/sys/class/mmc_host/mmc1/mmc1:5048/oemid:0x5449
/sys/class/mmc_host/mmc1/mmc1:5048/preferred_erase_size:4194304
/sys/class/mmc_host/mmc1/mmc1:5048/rca:0x5048
/sys/class/mmc_host/mmc1/mmc1:5048/scr:0205848701006432
/sys/class/mmc_host/mmc1/mmc1:5048/serial:0x36980065
/sys/class/mmc_host/mmc1/mmc1:5048/ssr:000000000800000004009000011b391e000800000002ff0003000000000000000000000000000000000000000000000000000000000000000000000000000000
/sys/class/mmc_host/mmc1/mmc1:5048/type:SD
/sys/class/mmc_host/mmc1/mmc1:5048/uevent:DRIVER=mmcblk
/sys/class/mmc_host/mmc1/mmc1:5048/uevent:MMC_TYPE=SD
/sys/class/mmc_host/mmc1/mmc1:5048/uevent:MMC_NAME=SD64G
/sys/class/mmc_host/mmc1/mmc1:5048/uevent:MODALIAS=mmc:block
New 2023 card:
--------------
mmc1: host does not support reading read-only switch, assuming write-enable
mmc1: new ultra high speed SDR104 SDXC card at address 5048
mmcblk1: mmc1:5048 SD64G 58.0 GiB
mmcblk1: p1
~ # grep -H . /sys/class/mmc_host/mmc1/mmc1\:5048/*
/sys/class/mmc_host/mmc1/mmc1:5048/cid:9f54495344363447614890060a017500
/sys/class/mmc_host/mmc1/mmc1:5048/csd:400e00325b590001cf9f7f800a400000
/sys/class/mmc_host/mmc1/mmc1:5048/date:05/2023
/sys/class/mmc_host/mmc1/mmc1:5048/dsr:0x404
/sys/class/mmc_host/mmc1/mmc1:5048/erase_size:512
/sys/class/mmc_host/mmc1/mmc1:5048/fwrev:0x1
/sys/class/mmc_host/mmc1/mmc1:5048/hwrev:0x6
/sys/class/mmc_host/mmc1/mmc1:5048/manfid:0x00009f
/sys/class/mmc_host/mmc1/mmc1:5048/name:SD64G
/sys/class/mmc_host/mmc1/mmc1:5048/ocr:0x00300000
/sys/class/mmc_host/mmc1/mmc1:5048/oemid:0x5449
/sys/class/mmc_host/mmc1/mmc1:5048/preferred_erase_size:4194304
/sys/class/mmc_host/mmc1/mmc1:5048/rca:0x5048
/sys/class/mmc_host/mmc1/mmc1:5048/scr:0205848701006432
/sys/class/mmc_host/mmc1/mmc1:5048/serial:0x4890060a
/sys/class/mmc_host/mmc1/mmc1:5048/ssr:000000000800000004009000010f391e000800000002ff0003000000000000000000000000000000000000000000000000000000000000000000000000000000
/sys/class/mmc_host/mmc1/mmc1:5048/type:SD
/sys/class/mmc_host/mmc1/mmc1:5048/uevent:DRIVER=mmcblk
/sys/class/mmc_host/mmc1/mmc1:5048/uevent:MMC_TYPE=SD
/sys/class/mmc_host/mmc1/mmc1:5048/uevent:MMC_NAME=SD64G
/sys/class/mmc_host/mmc1/mmc1:5048/uevent:MODALIAS=mmc:block
diff (-old 2019, +new 2023):
----------------------------
-/sys/class/mmc_host/mmc1/mmc1:5048/cid:9f544953443634476136980065013b00
-/sys/class/mmc_host/mmc1/mmc1:5048/csd:400e00325b590001cfff7f800a400000
-/sys/class/mmc_host/mmc1/mmc1:5048/date:11/2019
+/sys/class/mmc_host/mmc1/mmc1:5048/cid:9f54495344363447614890060a017500
+/sys/class/mmc_host/mmc1/mmc1:5048/csd:400e00325b590001cf9f7f800a400000
+/sys/class/mmc_host/mmc1/mmc1:5048/date:05/2023
/sys/class/mmc_host/mmc1/mmc1:5048/dsr:0x404
/sys/class/mmc_host/mmc1/mmc1:5048/erase_size:512
/sys/class/mmc_host/mmc1/mmc1:5048/fwrev:0x1
@@ -18,10 +18,15 @@
/sys/class/mmc_host/mmc1/mmc1:5048/preferred_erase_size:4194304
/sys/class/mmc_host/mmc1/mmc1:5048/rca:0x5048
/sys/class/mmc_host/mmc1/mmc1:5048/scr:0205848701006432
-/sys/class/mmc_host/mmc1/mmc1:5048/serial:0x36980065
-/sys/class/mmc_host/mmc1/mmc1:5048/ssr:000000000800000004009000011b391e000800000002ff0003000000000000000000000000000000000000000000000000000000000000000000000000000000
+/sys/class/mmc_host/mmc1/mmc1:5048/serial:0x4890060a
+/sys/class/mmc_host/mmc1/mmc1:5048/ssr:000000000800000004009000010f391e000800000002ff0003000000000000000000000000000000000000000000000000000000000000000000000000000000
/sys/class/mmc_host/mmc1/mmc1:5048/type:SD
/sys/class/mmc_host/mmc1/mmc1:5048/uevent:DRIVER=mmcblk
/sys/class/mmc_host/mmc1/mmc1:5048/uevent:MMC_TYPE=SD
/sys/class/mmc_host/mmc1/mmc1:5048/uevent:MMC_NAME=SD64G
/sys/class/mmc_host/mmc1/mmc1:5048/uevent:MODALIAS=mmc:block
Changes:
--------
CID: PSN (serial number), MDT (manufacturing date)
CSD: C_SIZE: 0x1cfff -> 0x1cf9f
SSR: ERASE_TIMEOUT: 6 -> 3
next prev parent reply other threads:[~2023-06-16 10:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 0:27 [PATCH] [RFC] Revert "mmc: core: Fixup support for writeback-cache for eMMC and SD" Marek Vasut
2023-05-31 5:46 ` Adrian Hunter
2023-05-31 11:34 ` Marek Vasut
2023-05-31 13:08 ` Christian Loehle
2023-05-31 21:33 ` Marek Vasut
2023-05-31 13:13 ` Adrian Hunter
2023-05-31 21:31 ` Marek Vasut
2023-06-01 6:20 ` Adrian Hunter
2023-06-02 21:46 ` Marek Vasut
2023-06-04 16:30 ` Adrian Hunter
2023-06-07 20:43 ` Marek Vasut
2023-06-12 4:59 ` Adrian Hunter
2023-06-12 8:59 ` Marek Vasut
2023-06-12 9:29 ` Adrian Hunter
2023-06-15 15:14 ` Ulf Hansson
2023-06-15 15:32 ` Marek Vasut
2023-06-15 15:35 ` Adrian Hunter
2023-06-15 15:36 ` Marek Vasut
2023-06-16 10:02 ` Ulf Hansson
2023-06-16 10:24 ` Marek Vasut
2023-06-16 10:33 ` Ulf Hansson
2023-06-20 1:44 ` Marek Vasut
2023-06-16 10:20 ` Marek Vasut [this message]
2023-05-31 6:01 ` Avri Altman
2023-05-31 11:34 ` Marek Vasut
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=4a8ae652-b930-3cd3-00df-c6dd1dd2a31d@denx.de \
--to=marex@denx.de \
--cc=CLoehle@hyperstone.com \
--cc=adrian.hunter@intel.com \
--cc=avri.altman@wdc.com \
--cc=axboe@kernel.dk \
--cc=linux-mmc@vger.kernel.org \
--cc=michael@allwinnertech.com \
--cc=ming.lei@redhat.com \
--cc=sh043.lee@samsung.com \
--cc=ulf.hansson@linaro.org \
--cc=xander_li@kingston.com.tw \
/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