From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: <linux-arm-kernel@lists.infradead.org>,
<herbert@gondor.apana.org.au>, <linux-crypto@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <eric@eukrea.com>
Subject: Re: [PATCH RESEND 0/7] crypto: at91/atmel: add Device Tree support
Date: Wed, 20 Nov 2013 11:43:26 +0100 [thread overview]
Message-ID: <528C924E.50206@atmel.com> (raw)
In-Reply-To: <cover.1383922546.git.nicolas.ferre@atmel.com>
On 08/11/2013 16:08, Nicolas Ferre :
> This series adds Device Tree support to the Atmel crypto drivers
> (AES/[T]DES/SHA). The Device Tree entries are very simple and only
> declare the reg/irq values and the link to DMA.
Herbert,
ping?
Could I have your "Acked-by" for taking these patches through the
arm-soc git tree, or do you want that we split this series so that you
can take the driver part of it?
Best regards,
> Some trivial patches are preceding this move to Device Tree to clean
> things up beforehand.
>
> The series has already been sent but a little bit scattered. So I collect
> everything, this time.
>
> Nicolas Ferre (7):
> ARM: at91/dt/trivial: use macro for AES irq type
> ARM: at91/dt/trivial: before sama5d3, Atmel MPU were using at91 prefix
> ARM: at91/dt/sama5d3: add DMA information to SHA/AES/TDES nodes
> crypto: atmel-aes - add support for Device Tree
> crypto: atmel-tdes - add support for Device Tree
> crypto: atmel-sha - add support for Device Tree
> crypto: atmel-sha - add sha information to the log
>
> .../devicetree/bindings/crypto/atmel-crypto.txt | 68 ++++++++++
> arch/arm/boot/dts/sama5d3.dtsi | 16 ++-
> drivers/crypto/atmel-aes.c | 143 ++++++++++++++-------
> drivers/crypto/atmel-sha.c | 103 +++++++++++----
> drivers/crypto/atmel-tdes.c | 143 ++++++++++++++-------
> 5 files changed, 346 insertions(+), 127 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/crypto/atmel-crypto.txt
>
--
Nicolas Ferre
WARNING: multiple messages have this Message-ID (diff)
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND 0/7] crypto: at91/atmel: add Device Tree support
Date: Wed, 20 Nov 2013 11:43:26 +0100 [thread overview]
Message-ID: <528C924E.50206@atmel.com> (raw)
In-Reply-To: <cover.1383922546.git.nicolas.ferre@atmel.com>
On 08/11/2013 16:08, Nicolas Ferre :
> This series adds Device Tree support to the Atmel crypto drivers
> (AES/[T]DES/SHA). The Device Tree entries are very simple and only
> declare the reg/irq values and the link to DMA.
Herbert,
ping?
Could I have your "Acked-by" for taking these patches through the
arm-soc git tree, or do you want that we split this series so that you
can take the driver part of it?
Best regards,
> Some trivial patches are preceding this move to Device Tree to clean
> things up beforehand.
>
> The series has already been sent but a little bit scattered. So I collect
> everything, this time.
>
> Nicolas Ferre (7):
> ARM: at91/dt/trivial: use macro for AES irq type
> ARM: at91/dt/trivial: before sama5d3, Atmel MPU were using at91 prefix
> ARM: at91/dt/sama5d3: add DMA information to SHA/AES/TDES nodes
> crypto: atmel-aes - add support for Device Tree
> crypto: atmel-tdes - add support for Device Tree
> crypto: atmel-sha - add support for Device Tree
> crypto: atmel-sha - add sha information to the log
>
> .../devicetree/bindings/crypto/atmel-crypto.txt | 68 ++++++++++
> arch/arm/boot/dts/sama5d3.dtsi | 16 ++-
> drivers/crypto/atmel-aes.c | 143 ++++++++++++++-------
> drivers/crypto/atmel-sha.c | 103 +++++++++++----
> drivers/crypto/atmel-tdes.c | 143 ++++++++++++++-------
> 5 files changed, 346 insertions(+), 127 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/crypto/atmel-crypto.txt
>
--
Nicolas Ferre
WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: <linux-arm-kernel@lists.infradead.org>,
<herbert@gondor.hengli.com.au>, <linux-crypto@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <eric@eukrea.com>
Subject: Re: [PATCH RESEND 0/7] crypto: at91/atmel: add Device Tree support
Date: Wed, 20 Nov 2013 11:43:26 +0100 [thread overview]
Message-ID: <528C924E.50206@atmel.com> (raw)
In-Reply-To: <cover.1383922546.git.nicolas.ferre@atmel.com>
On 08/11/2013 16:08, Nicolas Ferre :
> This series adds Device Tree support to the Atmel crypto drivers
> (AES/[T]DES/SHA). The Device Tree entries are very simple and only
> declare the reg/irq values and the link to DMA.
Herbert,
ping?
Could I have your "Acked-by" for taking these patches through the
arm-soc git tree, or do you want that we split this series so that you
can take the driver part of it?
Best regards,
> Some trivial patches are preceding this move to Device Tree to clean
> things up beforehand.
>
> The series has already been sent but a little bit scattered. So I collect
> everything, this time.
>
> Nicolas Ferre (7):
> ARM: at91/dt/trivial: use macro for AES irq type
> ARM: at91/dt/trivial: before sama5d3, Atmel MPU were using at91 prefix
> ARM: at91/dt/sama5d3: add DMA information to SHA/AES/TDES nodes
> crypto: atmel-aes - add support for Device Tree
> crypto: atmel-tdes - add support for Device Tree
> crypto: atmel-sha - add support for Device Tree
> crypto: atmel-sha - add sha information to the log
>
> .../devicetree/bindings/crypto/atmel-crypto.txt | 68 ++++++++++
> arch/arm/boot/dts/sama5d3.dtsi | 16 ++-
> drivers/crypto/atmel-aes.c | 143 ++++++++++++++-------
> drivers/crypto/atmel-sha.c | 103 +++++++++++----
> drivers/crypto/atmel-tdes.c | 143 ++++++++++++++-------
> 5 files changed, 346 insertions(+), 127 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/crypto/atmel-crypto.txt
>
--
Nicolas Ferre
next prev parent reply other threads:[~2013-11-20 10:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 15:08 [PATCH RESEND 0/7] crypto: at91/atmel: add Device Tree support Nicolas Ferre
2013-11-08 15:08 ` Nicolas Ferre
2013-11-08 15:08 ` Nicolas Ferre
2013-11-08 15:08 ` [PATCH RESEND 1/7] ARM: at91/dt/trivial: use macro for AES irq type Nicolas Ferre
2013-11-08 15:08 ` Nicolas Ferre
2013-11-08 15:08 ` Nicolas Ferre
2013-11-08 15:08 ` [PATCH RESEND 2/7] ARM: at91/dt/trivial: before sama5d3, Atmel MPU were using at91 prefix Nicolas Ferre
2013-11-08 15:08 ` Nicolas Ferre
2013-11-08 15:08 ` Nicolas Ferre
2013-11-08 15:08 ` [PATCH RESEND 3/7] ARM: at91/dt/sama5d3: add DMA information to SHA/AES/TDES nodes Nicolas Ferre
2013-11-08 15:08 ` Nicolas Ferre
2013-11-08 15:08 ` Nicolas Ferre
2013-11-08 15:08 ` [PATCH RESEND 4/7] crypto: atmel-aes - add support for Device Tree Nicolas Ferre
2013-11-08 15:08 ` Nicolas Ferre
2013-11-08 15:08 ` Nicolas Ferre
2013-11-08 15:08 ` [PATCH RESEND 5/7] crypto: atmel-tdes " Nicolas Ferre
2013-11-08 15:08 ` Nicolas Ferre
2013-11-08 15:08 ` Nicolas Ferre
2013-11-08 15:08 ` [PATCH RESEND 6/7] crypto: atmel-sha " Nicolas Ferre
2013-11-08 15:08 ` Nicolas Ferre
2013-11-08 15:08 ` Nicolas Ferre
2013-11-08 15:08 ` [PATCH RESEND 7/7] crypto: atmel-sha - add sha information to the log Nicolas Ferre
2013-11-08 15:08 ` Nicolas Ferre
2013-11-08 15:08 ` Nicolas Ferre
2013-11-20 10:43 ` Nicolas Ferre [this message]
2013-11-20 10:43 ` [PATCH RESEND 0/7] crypto: at91/atmel: add Device Tree support Nicolas Ferre
2013-11-20 10:43 ` Nicolas Ferre
2013-11-20 11:18 ` Herbert Xu
2013-11-20 11:18 ` Herbert Xu
2013-11-20 11:18 ` Herbert Xu
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=528C924E.50206@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=eric@eukrea.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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.