From: Maurus Cuelenaere <mcuelenaere@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: kmpark@infradead.org, linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org, herbert@gondor.apana.org.au
Subject: Re: [RFC 9/9] crypto: Add Samsung crypto engine driver
Date: Fri, 13 Aug 2010 13:17:53 +0200 [thread overview]
Message-ID: <4C6529E1.8020300@gmail.com> (raw)
In-Reply-To: <20100812.153208.48514514.davem@davemloft.net>
Op 13-08-10 00:32, David Miller schreef:
> From: Maurus Cuelenaere <mcuelenaere@gmail.com>
> Date: Thu, 12 Aug 2010 13:47:24 +0200
>
>> The main issues still remain (DMA not working at all and FIFO not
>> working for some (T)DES transfers). Additionally, I couldn't get
>> tcrypt to test the s3c-sss driver for some reason, it always picked
>> the standard AES/TDES/DES driver (even though s3c-sss has a higher
>> priority and succeeded the self-test).
> I forget the details of your driver, but were your encryption algorithms
> implemented async?
Yes, all are async (also the not-yet-working hash algorithms).
> tcrypt can validate async crypto algorithms, but cannot performance
> test them just yet. I can performance test async hash algorithms,
> for which I added the code for a few months ago.
Hmm ok, I suppose implementing support for performance testing async crypto
algorithms isn't trivial?
--
Maurus Cuelenaere
WARNING: multiple messages have this Message-ID (diff)
From: mcuelenaere@gmail.com (Maurus Cuelenaere)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 9/9] crypto: Add Samsung crypto engine driver
Date: Fri, 13 Aug 2010 13:17:53 +0200 [thread overview]
Message-ID: <4C6529E1.8020300@gmail.com> (raw)
In-Reply-To: <20100812.153208.48514514.davem@davemloft.net>
Op 13-08-10 00:32, David Miller schreef:
> From: Maurus Cuelenaere <mcuelenaere@gmail.com>
> Date: Thu, 12 Aug 2010 13:47:24 +0200
>
>> The main issues still remain (DMA not working at all and FIFO not
>> working for some (T)DES transfers). Additionally, I couldn't get
>> tcrypt to test the s3c-sss driver for some reason, it always picked
>> the standard AES/TDES/DES driver (even though s3c-sss has a higher
>> priority and succeeded the self-test).
> I forget the details of your driver, but were your encryption algorithms
> implemented async?
Yes, all are async (also the not-yet-working hash algorithms).
> tcrypt can validate async crypto algorithms, but cannot performance
> test them just yet. I can performance test async hash algorithms,
> for which I added the code for a few months ago.
Hmm ok, I suppose implementing support for performance testing async crypto
algorithms isn't trivial?
--
Maurus Cuelenaere
next prev parent reply other threads:[~2010-08-13 11:18 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1276284559.git.mcuelenaere@gmail.com>
2010-06-11 19:48 ` [PATCH 1/9] ARM: S3C64XX: Add SDMA clocks Maurus Cuelenaere
2010-06-11 19:48 ` Maurus Cuelenaere
2010-06-11 19:48 ` [PATCH 2/9] ARM: S3C64XX: Add SDMA support to DMA core Maurus Cuelenaere
2010-06-11 19:48 ` Maurus Cuelenaere
2010-06-11 19:48 ` [PATCH 3/9] ARM: S3C64XX: Stop and flush requests on freeing Maurus Cuelenaere
2010-06-11 19:48 ` Maurus Cuelenaere
2010-06-11 19:48 ` [PATCH 4/9] ARM: S3C64XX: Add support for secur clock Maurus Cuelenaere
2010-06-11 19:48 ` Maurus Cuelenaere
2010-06-11 19:49 ` [PATCH 5/9] ARM: S3C64XX: Add crypto engine register definitions Maurus Cuelenaere
2010-06-11 19:49 ` Maurus Cuelenaere
2010-06-11 19:49 ` [PATCH 6/9] ARM: S5PC100: " Maurus Cuelenaere
2010-06-11 19:49 ` Maurus Cuelenaere
2010-06-11 19:49 ` [PATCH 7/9] ARM: SAMSUNG: Add crypto engine platform definition Maurus Cuelenaere
2010-06-11 19:49 ` Maurus Cuelenaere
2010-06-11 19:49 ` [RFC 8/9] ARM: SAMSUNG: Add crypto engine register definitions Maurus Cuelenaere
2010-06-11 19:49 ` Maurus Cuelenaere
2010-06-11 19:49 ` [RFC 9/9] crypto: Add Samsung crypto engine driver Maurus Cuelenaere
2010-06-11 19:49 ` Maurus Cuelenaere
2010-06-27 4:07 ` David Miller
2010-06-27 4:07 ` David Miller
2010-06-27 11:06 ` Maurus Cuelenaere
2010-06-27 11:06 ` Maurus Cuelenaere
2010-06-28 4:57 ` David Miller
2010-06-28 4:57 ` David Miller
2010-08-03 4:44 ` Kyungmin Park
2010-08-03 4:44 ` Kyungmin Park
2010-08-12 11:47 ` Maurus Cuelenaere
2010-08-12 11:47 ` Maurus Cuelenaere
2010-08-12 22:32 ` David Miller
2010-08-12 22:32 ` David Miller
2010-08-13 11:17 ` Maurus Cuelenaere [this message]
2010-08-13 11:17 ` Maurus Cuelenaere
2010-08-13 21:45 ` David Miller
2010-08-13 21:45 ` David Miller
2010-08-13 22:56 ` Kim Phillips
2010-08-13 22:56 ` Kim Phillips
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=4C6529E1.8020300@gmail.com \
--to=mcuelenaere@gmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kmpark@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
/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.