From: Marek Vasut <marex@denx.de>
To: Avri Altman <Avri.Altman@wdc.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Cc: "Christian Löhle" <CLoehle@hyperstone.com>,
"Adrian Hunter" <adrian.hunter@intel.com>,
"Jens Axboe" <axboe@kernel.dk>,
"Michael Wu" <michael@allwinnertech.com>,
"Ming Lei" <ming.lei@redhat.com>,
"Seunghui Lee" <sh043.lee@samsung.com>,
"Ulf Hansson" <ulf.hansson@linaro.org>
Subject: Re: [PATCH] [RFC] Revert "mmc: core: Fixup support for writeback-cache for eMMC and SD"
Date: Wed, 31 May 2023 13:34:44 +0200 [thread overview]
Message-ID: <ae221597-8956-0ca1-2e67-e2a7c72252a0@denx.de> (raw)
In-Reply-To: <DM6PR04MB65757BA6C2B6FFFF3C16A901FC489@DM6PR04MB6575.namprd04.prod.outlook.com>
On 5/31/23 08:01, Avri Altman wrote:
>> This reverts commit 08ebf903af57cda6d773f3dd1671b64f73b432b8.
>>
>> On STM32MP153C DHCOR DRC Compact with microSD card Kingston Canvas
>> Go! Plus MicroSDXC I 64 GiB U3/V30/A2 SDCG3/64GB it is no longer possible
>> to mount ext4 filesystem.
>>
>> Git bisect points to this commit which is being reverted here. A bit of
>> investigation shows that for non-working microSD cards
>> cache_enabled=TRUE fua_enabled=false
>> For working microSD card (Kingston Canvas React Plus, MicroSDXC II
>> 64 GiB U3/V90/A1 SDCR2/64GB)
>> cache_enabled=FALSE fua_enabled=false
>>
>> It seems enabling the cache for SD cards causes the issue. Before the reverted
>> commit, the cache was not reported enabled for SD cards. I am not sure
>> whether such blunt revert is the correct solution however, any ideas ?
> The commit you are reverting has a couple of fixes tags - so reverting it will re-introduce those issues it aims to fix.
> If I recall correctly, I asked our sd system engineering to follow up on this,
> And they had no problem with the logic.
>
> I think that we need more data to establish the root cause of this issue,
> Provided that it is not a specific-vendor issue.
I just sent Adrian the command log, but I don't see anything obvious in it.
prev parent reply other threads:[~2023-05-31 11:35 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
2023-05-31 6:01 ` Avri Altman
2023-05-31 11:34 ` Marek Vasut [this message]
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=ae221597-8956-0ca1-2e67-e2a7c72252a0@denx.de \
--to=marex@denx.de \
--cc=Avri.Altman@wdc.com \
--cc=CLoehle@hyperstone.com \
--cc=adrian.hunter@intel.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 \
/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