From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Anderson Briglia <anderson.briglia@indt.org.br>
Cc: linux-kernel@vger.kernel.org,
"Linux-omap-open-source@linux.omap.com"
<linux-omap-open-source@linux.omap.com>,
linux@arm.linux.org.uk, ext David Brownell <david-b@pacbell.net>,
Tony Lindgren <tony@atomide.com>,
drzeus-list@drzeus.cx,
"Aguiar Carlos (EXT-INdT/Manaus)" <carlos.aguiar@indt.org.br>,
"Lizardo Anderson (EXT-INdT/Manaus)"
<anderson.lizardo@indt.org.br>
Subject: Re: [patch 1/5] Add MMC password protection (lock/unlock) support V3
Date: Mon, 9 Jan 2006 22:29:02 +0000 [thread overview]
Message-ID: <20060109222902.GF19131@flint.arm.linux.org.uk> (raw)
In-Reply-To: <43C2E064.90500@indt.org.br>
Please send patches as text/plain - it makes it difficult to reply to
them otherwise.
On Mon, Jan 09, 2006 at 06:15:00PM -0400, Anderson Briglia wrote:
> When a card is locked, only commands from the "basic" and "lock card" classes
> are accepted. To be able to use the other commands, the card must be unlocked
> first.
I don't think this works as you intend.
When a card is initially inserted, we discover the cards via mmc_setup()
and mmc_discover_cards(). This means that we'll never set the locked
status for newly inserted cards.
> ===================================================================
> --- linux-2.6.15-rc4.orig/drivers/mmc/mmc.c 2005-12-15 14:06:52.000000000 -0400
> +++ linux-2.6.15-rc4/drivers/mmc/mmc.c 2005-12-15 17:00:37.000000000 -0400
> @@ -986,10 +986,15 @@ static void mmc_check_cards(struct mmc_h
> cmd.flags = MMC_RSP_R1;
>
> err = mmc_wait_for_cmd(host, &cmd, CMD_RETRIES);
> - if (err == MMC_ERR_NONE)
> + if (err != MMC_ERR_NONE) {
> + mmc_card_set_dead(card);
> continue;
> + }
>
> - mmc_card_set_dead(card);
> + if (cmd.resp[0] & R1_CARD_IS_LOCKED)
> + mmc_card_set_locked(card);
> + else
> + card->state &= ~MMC_STATE_LOCKED;
We need a mmc_card_clear_locked() here.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2006-01-09 22:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 22:15 [patch 1/5] Add MMC password protection (lock/unlock) support V3 Anderson Briglia
2006-01-09 22:15 ` Anderson Briglia
2006-01-09 22:29 ` Russell King [this message]
2006-01-11 13:16 ` Anderson Briglia
2006-01-11 14:44 ` Russell King
2006-01-11 18:14 ` Tony Lindgren
2006-01-11 19:27 ` Anderson Briglia
2006-01-11 19:49 ` Tony Lindgren
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=20060109222902.GF19131@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=anderson.briglia@indt.org.br \
--cc=anderson.lizardo@indt.org.br \
--cc=carlos.aguiar@indt.org.br \
--cc=david-b@pacbell.net \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap-open-source@linux.omap.com \
--cc=linux@arm.linux.org.uk \
--cc=tony@atomide.com \
/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.