From: Anderson Briglia <anderson.briglia@indt.org.br>
To: linux-kernel@vger.kernel.org,
"Linux-omap-open-source@linux.omap.com"
<linux-omap-open-source@linux.omap.com>
Cc: linux@arm.linux.org.uk,
"Lizardo Anderson (EXT-INdT/Manaus)"
<anderson.lizardo@indt.org.br>,
drzeus-list@drzeus.cx
Subject: [patch 5/5] Add MMC password protection (lock/unlock) support V3
Date: Mon, 09 Jan 2006 18:17:10 -0400 [thread overview]
Message-ID: <43C2E0E6.30600@indt.org.br> (raw)
[-- Attachment #1: Type: text/plain, Size: 5 bytes --]
[-- Attachment #2: mmc_omap_blklen.diff --]
[-- Type: text/x-patch, Size: 1182 bytes --]
The MMC_LOCK_UNLOCK command requires the block length to be exactly the
password length + 2 bytes, but hardware-specific drivers force a "power of 2"
block size.
This patch sends the exact block size (password + 2 bytes) to the host. OMAP
specific.
Signed-off-by: Anderson Briglia <anderson.briglia@indt.org.br>
Signed-off-by: Anderson Lizardo <anderson.lizardo@indt.org.br>
Signed-off-by: Carlos Eduardo Aguiar <carlos.aguiar@indt.org.br>
Index: linux-2.6.15-rc4/drivers/mmc/omap.c
===================================================================
--- linux-2.6.15-rc4.orig/drivers/mmc/omap.c 2005-12-27 17:42:49.000000000 -0400
+++ linux-2.6.15-rc4/drivers/mmc/omap.c 2005-12-27 17:43:57.000000000 -0400
@@ -889,8 +889,12 @@ mmc_omap_prepare_data(struct mmc_omap_ho
return;
}
-
- block_size = 1 << data->blksz_bits;
+ /* password protection: we need to send the exact block size to the
+ * card (password + 2), not a 2-exponent. */
+ if (req->cmd->opcode == MMC_LOCK_UNLOCK)
+ block_size = data->sg[0].length;
+ else
+ block_size = 1 << data->blksz_bits;
OMAP_MMC_WRITE(host->base, NBLK, data->blocks - 1);
OMAP_MMC_WRITE(host->base, BLEN, block_size - 1);
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
reply other threads:[~2006-01-09 22:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=43C2E0E6.30600@indt.org.br \
--to=anderson.briglia@indt.org.br \
--cc=anderson.lizardo@indt.org.br \
--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 \
/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