From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mbroz@redhat.com>
Received: from mail.saout.de ([127.0.0.1])
 by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 0SJU_puN44qJ for <dm-crypt@saout.de>;
 Wed,  8 Feb 2012 22:05:39 +0100 (CET)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Wed,  8 Feb 2012 22:05:38 +0100 (CET)
Message-ID: <4F32E39E.1000508@redhat.com>
Date: Wed, 08 Feb 2012 22:05:34 +0100
From: Milan Broz <mbroz@redhat.com>
MIME-Version: 1.0
References: <CABOOXR4ssxieoRpf3gxkyMXQ-EcHcRYEPgc6kmpPGTWc6CwwKQ@mail.gmail.com>
In-Reply-To: <CABOOXR4ssxieoRpf3gxkyMXQ-EcHcRYEPgc6kmpPGTWc6CwwKQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] Inquiry from Qualcomm on DM_CRYPT for Android ICS
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: Hari Prasad <hariprasad2006@gmail.com>
Cc: dm-crypt@saout.de

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