From: "Christian Löhle" <CLoehle@hyperstone.com>
To: "Christian Löhle" <CLoehle@hyperstone.com>,
"Avri Altman" <Avri.Altman@wdc.com>,
"ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: RE: [PATCH] mmc-utils: Add basic erase error check
Date: Mon, 12 Dec 2022 14:08:43 +0000 [thread overview]
Message-ID: <21e4fd1b824f42d890df9a965a46344f@hyperstone.com> (raw)
In-Reply-To: <1f4cb8a2e7094b249a8f40b7f4eb01da@hyperstone.com>
> For SD a CMD13 after CMD38 is required, too.
> I guess I can add that.
Just realized that sending CMD13 is not sufficient as the kernel will poll because of R1B and clear the error flag.
Anyway I have this kernel patch for a write flag bit that aggregates errors during polling until card is in TRAN again.
I will send it then, since I don't think there is a good way of solving this for SD in mmc-utils, please consider this patch on its own.
Regards,
Christian
Hyperstone GmbH | Reichenaustr. 39a | 78467 Konstanz
Managing Director: Dr. Jan Peter Berns.
Commercial register of local courts: Freiburg HRB381782
next prev parent reply other threads:[~2022-12-12 14:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 9:21 [PATCH] mmc-utils: Add basic erase error check Christian Löhle
2022-12-12 13:44 ` Avri Altman
2022-12-12 14:00 ` Christian Löhle
2022-12-12 14:08 ` Christian Löhle [this message]
2022-12-13 14:00 ` Avri Altman
2022-12-13 15:26 ` Christian Löhle
2022-12-14 8:15 ` Avri Altman
2022-12-15 18:14 ` Christian Löhle
2022-12-16 6:11 ` Avri Altman
2023-01-02 12:01 ` Avri Altman
-- strict thread matches above, loose matches on Subject: below --
2023-01-16 10:49 Christian Löhle
2023-01-16 11:10 ` Avri Altman
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=21e4fd1b824f42d890df9a965a46344f@hyperstone.com \
--to=cloehle@hyperstone.com \
--cc=Avri.Altman@wdc.com \
--cc=adrian.hunter@intel.com \
--cc=linux-mmc@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.