From: Daniel Kucera <linux-mmc@danman.eu>
To: linux-mmc@vger.kernel.org, ulf.hansson@linaro.org
Subject: Re: [PATCH v2] mmc: core: allow detection of locked cards
Date: Thu, 23 May 2024 14:37:43 +0200 [thread overview]
Message-ID: <333b38e44daa8d6d8e3e173eb754d86e@danman.eu> (raw)
In-Reply-To: <20240523111317.594583-1-linux-mmc@danman.eu>
On 2024-05-23 13:13, linux-mmc@danman.eu wrote:
> From: Daniel Kucera <linux-mmc@danman.eu>
>
> Locked card will not reply to SEND_SCR or SD_STATUS commands
> so it was failing to initialize previously. When skipped,
> the card will get initialized and CMD42 can be sent using
> ioctl to unlock the card or remove password protection.
> Until unlocked, all read/write calls will timeout.
>
> Signed-off-by: Daniel Kucera <linux-mmc@danman.eu>
> ---
> drivers/mmc/core/sd.c | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/mmc/core/sd.c b/drivers/mmc/core/sd.c
> index 1c8148cdd..0eebfea02 100644
> --- a/drivers/mmc/core/sd.c
> +++ b/drivers/mmc/core/sd.c
> @@ -928,8 +928,20 @@ int mmc_sd_setup_card(struct mmc_host *host,
> struct mmc_card *card,
> bool reinit)
> {
> int err;
> + u32 card_status;
>
> - if (!reinit) {
> + err = mmc_send_status(card, &card_status);
> + if (err){
> + pr_err("%s: unable to get card status\n",
> + mmc_hostname(host));
> + return err;
> + }
> +
> + if (card_status & R1_CARD_IS_LOCKED){
> + pr_warn("%s: card is locked\n", mmc_hostname(host));
> + }
> +
> + if (!reinit && !(card_status & R1_CARD_IS_LOCKED)) {
> /*
> * Fetch SCR from card.
> */
Please forget this one, it doesn't work.
prev parent reply other threads:[~2024-05-23 12:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 11:13 [PATCH v2] mmc: core: allow detection of locked cards linux-mmc
2024-05-23 12:37 ` Daniel Kucera [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=333b38e44daa8d6d8e3e173eb754d86e@danman.eu \
--to=linux-mmc@danman.eu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox