Re: [PATCH 4/5] crypto:s5p-sss: Exynos5 SoCs too can select SSS driver

From: Naveen Krishna Ch
Date: Wed Jan 08 2014 - 23:28:13 EST


Hello Tomasz,

On 8 January 2014 06:00, Tomasz Figa <tomasz.figa@xxxxxxxxx> wrote:
> On Tuesday 07 of January 2014 17:21:48 Naveen Krishna Ch wrote:
>> This patch modifies Kconfig such that ARCH_EXYNOS5 SoCs
>> can also select Samsung SSS(Security SubSystem) driver.
>>
>> Signed-off-by: Naveen Krishna Ch <ch.naveen@xxxxxxxxxxx>
>> CC: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
>> CC: David S. Miller <davem@xxxxxxxxxxxxx>
>> CC: Vladimir Zapolskiy <vzapolskiy@xxxxxxxxx>
>> TO: <linux-crypto@xxxxxxxxxxxxxxx>
>> CC: <linux-samsung-soc@xxxxxxxxxxxxxxx>
>> ---
>> drivers/crypto/Kconfig | 8 ++++----
>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/crypto/Kconfig b/drivers/crypto/Kconfig
>> index f4fd837..137dcd8 100644
>> --- a/drivers/crypto/Kconfig
>> +++ b/drivers/crypto/Kconfig
>> @@ -300,15 +300,15 @@ config CRYPTO_DEV_DCP
>> capabilities of the DCP co-processor
>>
>> config CRYPTO_DEV_S5P
>> - tristate "Support for Samsung S5PV210 crypto accelerator"
>> - depends on ARCH_S5PV210
>> + tristate "Support for Samsung crypto accelerator"
>> + depends on ARCH_S5PV210 || ARCH_EXYNOS5
>> select CRYPTO_AES
>> select CRYPTO_ALGAPI
>> select CRYPTO_BLKCIPHER
>> help
>> This option allows you to have support for S5P crypto acceleration.
>> - Select this to offload Samsung S5PV210 or S5PC110 from AES
>> - algorithms execution.
>> + Select this to offload Samsung S5PV210 or S5PC110, Exynos5250
>> + and Exynos5420 from AES algorithms execution.
>
> What about Exynos4 SoCs?
The SSS module as such looks alike on Exynos5250, Exynso5420 and Exynos4210.
I couldn't test it right now. I should also verify on other Exynos4 SoCs.
>
> Best regards,
> Tomasz
>



--
Shine bright,
(: Nav :)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/