API spec).
-Petri
> -Original Message-
> From: lng-odp [mailto:lng-odp-boun...@lists.linaro.org] On Behalf Of Maxim
> Uvarov
> Sent: Monday, January 16, 2017 6:35 PM
> To: lng-odp@lists.linaro.org
> Subject: Re: [lng-odp] [API-NEXT PATCH 1/4] validation: crypto: fi
Merged,
Maxim.
On 01/12/17 09:01, Krishna Garapati wrote:
> for this series,
>
> Reviewed-by: Balakrishna Garapati
>
> /Krishna
>
> On 10 January 2017 at 13:09, Matias Elo wrote:
>
>> Some algorithms may be implemented using hardware and some using software.
>> All supported algorithms shoul
> Can we add sync/Async in capabilities and add similar check before running
> synchronous and asynchronous suites?
>
> Regards
> Nikhil
>
This would require crypto API changes. Adding simple sync/async capability
flags may not be enough since used algorithm/packet size may determine if a
pa
@lists.linaro.org
Subject: [lng-odp] [API-NEXT PATCH 1/4] validation: crypto: fix hw cipher/auth
algorithm check
Some algorithms may be implemented using hardware and some using software.
All supported algorithms should be set in capacity.auths /capacity.ciphers
independent of implementation types.
Signed
for this series,
Reviewed-by: Balakrishna Garapati
/Krishna
On 10 January 2017 at 13:09, Matias Elo wrote:
> Some algorithms may be implemented using hardware and some using software.
> All supported algorithms should be set in capacity.auths /capacity.ciphers
> independent of implementation
Some algorithms may be implemented using hardware and some using software.
All supported algorithms should be set in capacity.auths /capacity.ciphers
independent of implementation types.
Signed-off-by: Matias Elo
---
.../validation/api/crypto/odp_crypto_test_inp.c| 69 ++
