All of lore.kernel.org
 help / color / mirror / Atom feed
From: leroy christophe <christophe.leroy@c-s.fr>
To: Kim Phillips <kim.phillips@freescale.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-crypto@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 00/17] crypto: talitos - Add support for SEC1
Date: Fri, 17 Apr 2015 16:29:48 +0200	[thread overview]
Message-ID: <553118DC.6000508@c-s.fr> (raw)
In-Reply-To: <20150417142353.76D561A242C@localhost.localdomain>

Oops, this is the first time I use directly the output of git 
format-patch into sendmail, and
it looks like the mails are dated with the commit date, not today's date.

I will resend now with today's date. Sorry for the noise.

Christophe

Le 17/04/2015 15:47, Christophe Leroy a écrit :
> The purpose of this set of patchs is to add to talitos crypto driver
> the support for the SEC1 version of the security engine, which is
> found in mpc885 and mpc8272 processors.
>
> v3 is a complete rework of the patchset. Since a kernel can be built
> with support for both MPC82xx and MPC83xx at the same time, talitos
> driver shall support both SEC1 and SEC2+ at the same time.
>
> Based on cryptodev-2.6 tree
>
> Christophe Leroy (17):
>    crypto: talitos - Use zero entry to init descriptors ptrs to zero
>    crypto: talitos - Refactor the sg in/out chain allocation
>    crypto: talitos - talitos_ptr renamed ptr for more lisibility
>    crypto: talitos - Add a helper function to clear j_extent field
>    crypto: talitos - remove param 'extent' in map_single_talitos_ptr()
>    crypto: talitos - helper function for ptr len
>    crypto: talitos - enhanced talitos_desc struct for SEC1
>    crypto: talitos - add sub-choice in talitos CONFIG for SEC1
>    crypto: talitos - Add a feature to tag SEC1
>    crypto: talitos - fill in talitos descriptor iaw SEC1 or SEC2+
>    crypto: talitos - adaptation of talitos_submit() for SEC1
>    crypto: talitos - base address for Execution Units
>    crypto: talitos - adapt interrupts and reset functions to SEC1
>    crypto: talitos - implement scatter/gather copy for SEC1
>    crypto: talitos - SEC1 bugs on 0 data hash
>    crypto: talitos - Add fsl,sec1.0 compatible
>    crypto: talitos - Update DT bindings with SEC1
>
>   .../devicetree/bindings/crypto/fsl-sec2.txt        |   6 +-
>   drivers/crypto/Kconfig                             |  18 +
>   drivers/crypto/talitos.c                           | 727 +++++++++++++++------
>   drivers/crypto/talitos.h                           | 153 +++--
>   4 files changed, 644 insertions(+), 260 deletions(-)
>

WARNING: multiple messages have this Message-ID (diff)
From: leroy christophe <christophe.leroy@c-s.fr>
To: Kim Phillips <kim.phillips@freescale.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>
Cc: devicetree@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: [PATCH v3 00/17] crypto: talitos - Add support for SEC1
Date: Fri, 17 Apr 2015 16:29:48 +0200	[thread overview]
Message-ID: <553118DC.6000508@c-s.fr> (raw)
In-Reply-To: <20150417142353.76D561A242C@localhost.localdomain>

Oops, this is the first time I use directly the output of git 
format-patch into sendmail, and
it looks like the mails are dated with the commit date, not today's date.

I will resend now with today's date. Sorry for the noise.

Christophe

Le 17/04/2015 15:47, Christophe Leroy a écrit :
> The purpose of this set of patchs is to add to talitos crypto driver
> the support for the SEC1 version of the security engine, which is
> found in mpc885 and mpc8272 processors.
>
> v3 is a complete rework of the patchset. Since a kernel can be built
> with support for both MPC82xx and MPC83xx at the same time, talitos
> driver shall support both SEC1 and SEC2+ at the same time.
>
> Based on cryptodev-2.6 tree
>
> Christophe Leroy (17):
>    crypto: talitos - Use zero entry to init descriptors ptrs to zero
>    crypto: talitos - Refactor the sg in/out chain allocation
>    crypto: talitos - talitos_ptr renamed ptr for more lisibility
>    crypto: talitos - Add a helper function to clear j_extent field
>    crypto: talitos - remove param 'extent' in map_single_talitos_ptr()
>    crypto: talitos - helper function for ptr len
>    crypto: talitos - enhanced talitos_desc struct for SEC1
>    crypto: talitos - add sub-choice in talitos CONFIG for SEC1
>    crypto: talitos - Add a feature to tag SEC1
>    crypto: talitos - fill in talitos descriptor iaw SEC1 or SEC2+
>    crypto: talitos - adaptation of talitos_submit() for SEC1
>    crypto: talitos - base address for Execution Units
>    crypto: talitos - adapt interrupts and reset functions to SEC1
>    crypto: talitos - implement scatter/gather copy for SEC1
>    crypto: talitos - SEC1 bugs on 0 data hash
>    crypto: talitos - Add fsl,sec1.0 compatible
>    crypto: talitos - Update DT bindings with SEC1
>
>   .../devicetree/bindings/crypto/fsl-sec2.txt        |   6 +-
>   drivers/crypto/Kconfig                             |  18 +
>   drivers/crypto/talitos.c                           | 727 +++++++++++++++------
>   drivers/crypto/talitos.h                           | 153 +++--
>   4 files changed, 644 insertions(+), 260 deletions(-)
>

  reply	other threads:[~2015-04-17 14:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17 13:47 [PATCH v3 00/17] crypto: talitos - Add support for SEC1 Christophe Leroy
2015-04-17 13:47 ` Christophe Leroy
2015-04-17 14:29 ` leroy christophe [this message]
2015-04-17 14:29   ` leroy christophe
  -- strict thread matches above, loose matches on Subject: below --
2015-04-17 14:31 Christophe Leroy
2015-04-17 14:31 ` Christophe Leroy
2015-04-17 15:26 ` Olaf Hering
2015-04-17 15:26   ` Olaf Hering
2015-04-19  5:48 ` Herbert Xu
2015-04-19  5:48   ` 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=553118DC.6000508@c-s.fr \
    --to=christophe.leroy@c-s.fr \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=kim.phillips@freescale.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@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.