From: Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org>
To: javier Martin <javier.martin@vista-silicon.com>
Cc: linux-crypto@vger.kernel.org, swarren@nvidia.com,
herbert@gondor.apana.org.au, arnd@arndb.de,
linux-doc@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
kernel@pengutronix.de, shawn.guo@linaro.org, davem@davemloft.net,
linux-arm-kernel@lists.infradead.org, gcembed@gmail.com
Subject: Re: [PATCH v2 2/3] crypto: sahara: Add driver for SAHARA2 accelerator.
Date: Fri, 01 Mar 2013 08:28:40 +0100 [thread overview]
Message-ID: <87fw0fh93r.fsf@lebrac.rtp-net.org> (raw)
In-Reply-To: <CACKLOr0y6M4O82KRVWSny-wzwmZPGS3pOGkZtdgc1aynH94LRQ@mail.gmail.com> (javier Martin's message of "Thu, 28 Feb 2013 15:08:13 +0100")
javier Martin <javier.martin@vista-silicon.com> writes:
Hi,
> Hi Arnaud,
>
> On 28 February 2013 12:07, Arnaud Patard <arnaud.patard@rtp-net.org> wrote:
>> Javier Martin <javier.martin@vista-silicon.com> writes:
>>
>> Hi,
>>
>>> SAHARA2 HW module is included in the i.MX27 SoC from
>>> Freescale. It is capable of performing cipher algorithms
>>> such as AES, 3DES..., hashing and RNG too.
>>
>> The rmmod oops is gone with this version, thanks.
>>
>>>
>>> This driver provides support for AES-CBC and AES-ECB
>>> by now.
>>>
>>> Signed-off-by: Javier Martin <javier.martin@vista-silicon.com>
>>> ---
>>> drivers/crypto/Kconfig | 10 +
>>> drivers/crypto/Makefile | 1 +
>>> drivers/crypto/sahara.c | 1070 +++++++++++++++++++++++++++++++++++++++++++++++
>>> 3 files changed, 1081 insertions(+)
>>> create mode 100644 drivers/crypto/sahara.c
>>>
>>> diff --git a/drivers/crypto/Kconfig b/drivers/crypto/Kconfig
>>> index 87ec4d0..7d73f5a 100644
>>> --- a/drivers/crypto/Kconfig
>>> +++ b/drivers/crypto/Kconfig
>>> @@ -276,6 +276,16 @@ config CRYPTO_DEV_PICOXCELL
>>>
>>> Saying m here will build a module named pipcoxcell_crypto.
>>>
>>> +config CRYPTO_DEV_SAHARA
>>> + tristate "Support for SAHARA crypto accelerator"
>>> + depends on MACH_MX27 && EXPERIMENTAL && OF
>>
>> maybe switch to ARCH_MXC instead of MAC_MX27 ?
>>
>> [...]
>>
>>> +static struct platform_driver sahara_driver = {
>>> + .probe = sahara_probe,
>>> + .remove = __devexit_p(sahara_remove),
>>
>> Please remove the __devexit_p too.
>>
>>
>> For information, you'll find below what I've changed to test the driver on my
>> imx51. It's not perfect but it's enough for testing things.
>>
>>
>
> Since I have to send v3 anyway to comply with Sascha's request maybe
> it would be worth to include your changes to provide support for
> i.mx51 too.
If you feel like including my changes or something based on my changes
in your v3, it's fine for me.
Arnaud
WARNING: multiple messages have this Message-ID (diff)
From: arnaud.patard@rtp-net.org (Arnaud Patard (Rtp))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/3] crypto: sahara: Add driver for SAHARA2 accelerator.
Date: Fri, 01 Mar 2013 08:28:40 +0100 [thread overview]
Message-ID: <87fw0fh93r.fsf@lebrac.rtp-net.org> (raw)
In-Reply-To: <CACKLOr0y6M4O82KRVWSny-wzwmZPGS3pOGkZtdgc1aynH94LRQ@mail.gmail.com> (javier Martin's message of "Thu, 28 Feb 2013 15:08:13 +0100")
javier Martin <javier.martin@vista-silicon.com> writes:
Hi,
> Hi Arnaud,
>
> On 28 February 2013 12:07, Arnaud Patard <arnaud.patard@rtp-net.org> wrote:
>> Javier Martin <javier.martin@vista-silicon.com> writes:
>>
>> Hi,
>>
>>> SAHARA2 HW module is included in the i.MX27 SoC from
>>> Freescale. It is capable of performing cipher algorithms
>>> such as AES, 3DES..., hashing and RNG too.
>>
>> The rmmod oops is gone with this version, thanks.
>>
>>>
>>> This driver provides support for AES-CBC and AES-ECB
>>> by now.
>>>
>>> Signed-off-by: Javier Martin <javier.martin@vista-silicon.com>
>>> ---
>>> drivers/crypto/Kconfig | 10 +
>>> drivers/crypto/Makefile | 1 +
>>> drivers/crypto/sahara.c | 1070 +++++++++++++++++++++++++++++++++++++++++++++++
>>> 3 files changed, 1081 insertions(+)
>>> create mode 100644 drivers/crypto/sahara.c
>>>
>>> diff --git a/drivers/crypto/Kconfig b/drivers/crypto/Kconfig
>>> index 87ec4d0..7d73f5a 100644
>>> --- a/drivers/crypto/Kconfig
>>> +++ b/drivers/crypto/Kconfig
>>> @@ -276,6 +276,16 @@ config CRYPTO_DEV_PICOXCELL
>>>
>>> Saying m here will build a module named pipcoxcell_crypto.
>>>
>>> +config CRYPTO_DEV_SAHARA
>>> + tristate "Support for SAHARA crypto accelerator"
>>> + depends on MACH_MX27 && EXPERIMENTAL && OF
>>
>> maybe switch to ARCH_MXC instead of MAC_MX27 ?
>>
>> [...]
>>
>>> +static struct platform_driver sahara_driver = {
>>> + .probe = sahara_probe,
>>> + .remove = __devexit_p(sahara_remove),
>>
>> Please remove the __devexit_p too.
>>
>>
>> For information, you'll find below what I've changed to test the driver on my
>> imx51. It's not perfect but it's enough for testing things.
>>
>>
>
> Since I have to send v3 anyway to comply with Sascha's request maybe
> it would be worth to include your changes to provide support for
> i.mx51 too.
If you feel like including my changes or something based on my changes
in your v3, it's fine for me.
Arnaud
next prev parent reply other threads:[~2013-03-01 7:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 10:41 [PATCH v2 0/3] crypto: sahara: Add support for SAHARA in i.MX27 Javier Martin
2013-02-27 10:41 ` Javier Martin
2013-02-27 10:41 ` [PATCH v2 1/3] i.MX27: Add clock support for SAHARA2 Javier Martin
2013-02-27 10:41 ` Javier Martin
2013-02-27 10:41 ` [PATCH v2 2/3] crypto: sahara: Add driver for SAHARA2 accelerator Javier Martin
2013-02-27 10:41 ` Javier Martin
2013-02-27 10:47 ` Arnd Bergmann
2013-02-27 10:47 ` Arnd Bergmann
2013-02-28 11:07 ` Arnaud Patard
2013-02-28 11:07 ` Arnaud Patard (Rtp)
2013-02-28 14:08 ` javier Martin
2013-02-28 14:08 ` javier Martin
2013-03-01 7:28 ` Arnaud Patard [this message]
2013-03-01 7:28 ` Arnaud Patard (Rtp)
2013-02-27 10:41 ` [PATCH v2 3/3] crypto: sahara: Add device tree binding for SAHARA2 Javier Martin
2013-02-27 10:41 ` Javier Martin
2013-02-27 20:05 ` Sascha Hauer
2013-02-27 20:05 ` Sascha Hauer
2013-02-28 7:51 ` javier Martin
2013-02-28 7:51 ` javier Martin
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=87fw0fh93r.fsf@lebrac.rtp-net.org \
--to=arnaud.patard@rtp-net.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=gcembed@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=javier.martin@vista-silicon.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=shawn.guo@linaro.org \
--cc=swarren@nvidia.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 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.