From: Marek Vasut <marex@denx.de>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: "Adrian Hunter" <adrian.hunter@intel.com>,
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: Tue, 20 Jun 2023 03:44:25 +0200 [thread overview]
Message-ID: <a0115a9d-90b1-81ac-3a57-c7939a8367b7@denx.de> (raw)
In-Reply-To: <CAPDyKFrY84vairXcWo3hRo26nV8=7KZmEaDua-pna6pj5LLRyw@mail.gmail.com>
On 6/16/23 12:33, Ulf Hansson wrote:
Hi,
[...]
>>>>>> I have been trying to follow the progress around this matter. If I
>>>>>> understand correctly we are leaning towards making a card quirk for
>>>>>> this particular SD, to avoid us from turning on and using a broken
>>>>>> cache feature.
>>>>>>
>>>>>> Or what are you thinking?
>>>>>
>>>>> That is probably the simplest option.
>>>>
>>>> Just give me a day or two to test the other newer card.
>>>>
>>>> What would you base that quirk off of ? Date ? We don't know when the
>>>> "fixed" cards started to be produced .
>>>
>>> Right. It seems like the best we can do is to make a quirk for that
>>> particular version of card that you proved to have failed.
>>
>> I just sent a few more data points . It is either date, or C_SIZE, or
>> ERASE_TIMEOUT (if I decode it right). I can also just archive the card,
>> since we have sample size of the defective card equal 1 . It could just
>> be a defective card after all, although the fact that only cache would
>> be defective is unusual.
>
> I wouldn't mind having a card quirk and to use "date". But it looks
> like it's your call to make. :-)
I sent the quirk patch:
[PATCH] mmc: Add MMC_QUIRK_BROKEN_SD_CACHE for Kingston Canvas Go Plus
from 11/2019
It seems it is a bit bigger than I though it would originally be.
next prev parent reply other threads:[~2023-06-20 1:44 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 [this message]
2023-06-16 10:20 ` Marek Vasut
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=a0115a9d-90b1-81ac-3a57-c7939a8367b7@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