From: Daniel Kucera <linux-mmc@danman.eu>
To: Avri Altman <Avri.Altman@wdc.com>
Cc: linux-mmc@vger.kernel.org, ulf.hansson@linaro.org
Subject: Re: [PATCH v3] mmc: core: allow detection of locked cards
Date: Sun, 02 Jun 2024 14:37:33 +0200 [thread overview]
Message-ID: <4716f78bbe71f4d8262b16a546393758@danman.eu> (raw)
In-Reply-To: <DM6PR04MB65758D11355C0A516B10704DFCFE2@DM6PR04MB6575.namprd04.prod.outlook.com>
Hello Avri,
On 2024-06-02 07:26, Avri Altman wrote:
>> On 2024-05-23 15:20, 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 | 13 ++++++++++++-
>> > 1 file changed, 12 insertions(+), 1 deletion(-)
>> >
>> > diff --git a/drivers/mmc/core/sd.c b/drivers/mmc/core/sd.c index
>> > 1c8148cdd..ae821df7d 100644
>> > --- a/drivers/mmc/core/sd.c
>> > +++ b/drivers/mmc/core/sd.c
>> > @@ -928,8 +928,19 @@ 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.
>> > */
>>
>> Any feedback please?
> You didn't address my comment from your v1 -
> Since eMMC & SD shares the very same locking feature (non-COP SD that
> is) -
> You should at least explain in your commit log why it isn't an issue
> for eMMC,
> If indeed it is not.
I'm sorry, I didn't get what you mean by that. I am touching only the
sd.c code, not the mmc.c (where eMMC is initialized, am I correct?).
How should I address this?
Should I test with eMMC to SD adaptor? I don't have any currently.
I am sorry if these are stupid questions, I am a layman.
>
> Thanks,
> Avri
>
>>
>> D.
Thank you.
Daniel.
next prev parent reply other threads:[~2024-06-02 12:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 13:20 [PATCH v3] mmc: core: allow detection of locked cards linux-mmc
2024-06-01 21:43 ` Daniel Kucera
2024-06-02 5:26 ` Avri Altman
2024-06-02 12:37 ` Daniel Kucera [this message]
2024-06-02 12:59 ` Avri Altman
2024-06-06 8:17 ` Daniel Kucera
2024-06-06 8:39 ` 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=4716f78bbe71f4d8262b16a546393758@danman.eu \
--to=linux-mmc@danman.eu \
--cc=Avri.Altman@wdc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox