From: Milan Broz <mbroz@redhat.com>
To: Hari Prasad <hariprasad2006@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Inquiry from Qualcomm on DM_CRYPT for Android ICS
Date: Wed, 08 Feb 2012 22:05:34 +0100 [thread overview]
Message-ID: <4F32E39E.1000508@redhat.com> (raw)
In-Reply-To: <CABOOXR4ssxieoRpf3gxkyMXQ-EcHcRYEPgc6kmpPGTWc6CwwKQ@mail.gmail.com>
On 02/08/2012 08:21 PM, Hari Prasad wrote:
> MY name is Hari, I work for Crypto SW team at Qualcomm Inc. We are
> using our Crypto HW to do all the necessary encryption & decryption.
> We are trying to use this DM-CRYPT in our setup, I am not sure how
> the HW device is mapped using DM_CRYPT, I don't see any of our code
> being called for HW when I run an encryption test (ENCRYPT PHONE in
> ICS Android build).
>
> I have attached the log (printk added in DM_CRYPT), I see that the
> device crashes or something happens (device disappears after few
> seconds of starting the ENCRYPT_PHONE).
>
> We register our HW through misc_register function call.
>
> It would be really helpful if I can get the solution to map our HW
> device using DM-CRYPT.
You need to write a driver for crypto API, then dmcrypt will use
your hw encryption automatically. Then you should see your implementation
in /proc/crypto
dmcrypt doesn't use any hw directly, all crypto functions are
handled through kernel crypto API interface.
(Usually hw crypto drivers have higher priority, so they
are preferred to sw implementation, see priority in /proc/crypto.)
You can ask on kernel crypto list if you need help with implementing
crypto driver - list is linux-crypto@vger.kernel.org
Milan
prev parent reply other threads:[~2012-02-08 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 19:21 [dm-crypt] Inquiry from Qualcomm on DM_CRYPT for Android ICS Hari Prasad
2012-02-08 21:05 ` Milan Broz [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=4F32E39E.1000508@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=hariprasad2006@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