From: Arnd Bergmann <arnd@arndb.de>
To: Chris Ball <cjb@laptop.org>
Cc: "John Calixto" <john.calixto@modsystems.com>,
linux-mmc@vger.kernel.org,
"Andrei Warkentin" <andreiw@motorola.com>,
"Michał Mirosław" <mirqus@gmail.com>
Subject: Re: [PATCH v6] mmc: Add mmc CMD+ACMD passthrough ioctl
Date: Thu, 21 Apr 2011 12:47:35 +0200 [thread overview]
Message-ID: <201104211247.35903.arnd@arndb.de> (raw)
In-Reply-To: <m3wrioesql.fsf@pullcord.laptop.org>
On Wednesday 20 April 2011, Chris Ball wrote:
> On Wed, Apr 20 2011, John Calixto wrote:
> > Have you had the chance to look at v6 of this patch? If so, what do you
> > think?
>
> Looks good to me. Since Arnd's been reviewing, it'd be nice to get a
> Reviewed-by: tag from him and acknowledgement that his concerns are all
> addressed, and then I'll merge it.
Once the pointer passing is worked out, I think we have basically resolved
the technical issues. One more thing that I just noticed: The
__u64 data_ptr needs to be aligned, otherwise you get a problem
on x86, which uses different alignment for 64 bit members in structures
between 32 and 64 bit ABIs. Putting the 64 bit members first in the data
structure, and adding padding at the end to have a size that is a multiple
of 8 bytes should take care of this.
I don't quite understand the timeout stuff in there, so I'm not sure how
I'd fill these from an application like qemu that blindly passes down
commands. I'd feel more comfortable if we didn't have to specify these
in the interface, but I have no strict objection if you think that passing
those is a reasonable requirement.
The more important question that is still unresolved however is the
nontechnical one:
Do we want users to use this interface for DRM applications?
I would still prefer having a more high-level interface for this, ideally
something where we just export a block device for the encrypted partition,
with an ioctl interface to do the authentication. Alternatively, I could
imagine an ioctl interface that exports each SD security command as a
separate ioctl command, including the block read/write ones.
The information to do this seems to be available in
http://issuu.com/sravan/docs/sd_card, which describes the ACMDs.
It shouldn't be too hard to implement them in a high-level API.
What I don't know is whether we have a clear policy about implementing
SD standard interfaces in the kernel that are not part of the redacted
specs.
Arnd
next prev parent reply other threads:[~2011-04-21 10:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 0:34 v6 changelog for mmc ioctl patch John Calixto
2011-04-14 0:38 ` [PATCH v6] mmc: Add mmc CMD+ACMD passthrough ioctl John Calixto
2011-04-20 17:12 ` John Calixto
2011-04-20 17:29 ` Chris Ball
2011-04-21 10:47 ` Arnd Bergmann [this message]
2011-04-20 17:31 ` Michał Mirosław
2011-04-20 17:38 ` John Calixto
2011-04-20 18:06 ` Michał Mirosław
2011-04-20 18:23 ` Michał Mirosław
2011-04-20 19:06 ` John Calixto
2011-04-20 19:17 ` Arnd Bergmann
2011-04-20 19:34 ` John Calixto
2011-04-20 19:38 ` Arnd Bergmann
2011-04-20 19:46 ` Michał Mirosław
2011-04-20 20:47 ` John Calixto
2011-04-20 22:28 ` Chris Ball
2011-04-21 5:11 ` Arnd Bergmann
2011-04-21 10:28 ` Michał Mirosław
2011-04-21 11:15 ` Arnd Bergmann
2011-04-21 11:47 ` Michał Mirosław
2011-04-21 12:39 ` Arnd Bergmann
2011-04-21 13:40 ` Michał Mirosław
2011-04-20 22:13 ` Chris Ball
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=201104211247.35903.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=andreiw@motorola.com \
--cc=cjb@laptop.org \
--cc=john.calixto@modsystems.com \
--cc=linux-mmc@vger.kernel.org \
--cc=mirqus@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox