From: Marek Vasut <marex@denx.de>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Fabio Estevam <fabio.estevam@freescale.com>,
linux-crypto@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH V2 3/5] ARM: mxs: crypto: Add Freescale MXS DCP driver
Date: Tue, 10 Dec 2013 20:19:22 +0100 [thread overview]
Message-ID: <201312102019.22473.marex@denx.de> (raw)
In-Reply-To: <20131203110958.GF13726@S2101-09.ap.freescale.net>
On Tuesday, December 03, 2013 at 12:10:02 PM, Shawn Guo wrote:
> On Sun, Dec 01, 2013 at 10:20:21PM +0100, Marek Vasut wrote:
> > Add support for the MXS DCP block. The driver currently supports
> > SHA-1/SHA-256 hashing and AES-128 CBC/ECB modes. The non-standard
> > CRC32 is not yet supported.
> >
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > Cc: Herbert Xu <herbert@gondor.apana.org.au>
> > Cc: David S. Miller <davem@davemloft.net>
> > Cc: Fabio Estevam <fabio.estevam@freescale.com>
> > Cc: Shawn Guo <shawn.guo@linaro.org>
> > Cc: linux-crypto@vger.kernel.org
> > ---
> >
> > .../devicetree/bindings/crypto/fsl-dcp.txt | 18 +
> > drivers/crypto/Kconfig | 17 +
> > drivers/crypto/Makefile | 1 +
> > drivers/crypto/mxs-dcp.c | 1100
> > ++++++++++++++++++++ 4 files changed, 1136 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/crypto/fsl-dcp.txt
>
> Since it creates new device tree bindings, please copy
> devicetree@vger.kernel.org, so that DT experts can have a chance to
> review the bindings.
OK, makes sense.
> Shawn
>
> > create mode 100644 drivers/crypto/mxs-dcp.c
> >
> > V2: Use dma_{un,}map_single instead of large coherent chunk
> >
> > Use the DMA mapping function on DCP buffers instead of the large
> > coherent chunk. This reduces the amount of cache
> > flushes/invalidations and write buffer drains as we do not need to
> > do this every time we operate with the coherent memory chunk, but
> > only when really needed.
> >
> > Make sure rctx is always inited
> >
> > The crypto request context is not zeroed out by the crypto API.
> > While this is not documented anywhere, it will produce arcane and
> > hard to debug problems. Fix the DCP code so that the request
> > context is always properly initialized.
> >
> > Minor code and coding-style fixes.
> >
> > diff --git a/Documentation/devicetree/bindings/crypto/fsl-dcp.txt
> > b/Documentation/devicetree/bindings/crypto/fsl-dcp.txt new file mode
> > 100644
> > index 0000000..ee8fbf9
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/crypto/fsl-dcp.txt
> > @@ -0,0 +1,18 @@
> > +Freescale DCP (Data Co-Processor) found on i.MX23/i.MX28 .
> > +
> > +Required properties:
> > +- compatible : Should be "fsl,<soc>-dcp"
> > +- reg : Should contain MXS DCP registers location and length
> > +- interrupts : Should contain MXS DCP interrupt numbers, VMI IRQ and DCP
> > IRQ + must be supplied, optionally Secure IRQ can be
> > present, but + is currently not implemented and not used.
> > +
> > +Example:
> > +
> > +dcp@80028000 {
> > + compatible = "fsl,imx28-dcp", "fsl,imx23-dcp";
> > + reg = <0x80028000 0x2000>;
> > + interrupts = <52 53>;
> > + status = "okay";
> > +};
[...]
WARNING: multiple messages have this Message-ID (diff)
From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 3/5] ARM: mxs: crypto: Add Freescale MXS DCP driver
Date: Tue, 10 Dec 2013 20:19:22 +0100 [thread overview]
Message-ID: <201312102019.22473.marex@denx.de> (raw)
In-Reply-To: <20131203110958.GF13726@S2101-09.ap.freescale.net>
On Tuesday, December 03, 2013 at 12:10:02 PM, Shawn Guo wrote:
> On Sun, Dec 01, 2013 at 10:20:21PM +0100, Marek Vasut wrote:
> > Add support for the MXS DCP block. The driver currently supports
> > SHA-1/SHA-256 hashing and AES-128 CBC/ECB modes. The non-standard
> > CRC32 is not yet supported.
> >
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > Cc: Herbert Xu <herbert@gondor.apana.org.au>
> > Cc: David S. Miller <davem@davemloft.net>
> > Cc: Fabio Estevam <fabio.estevam@freescale.com>
> > Cc: Shawn Guo <shawn.guo@linaro.org>
> > Cc: linux-crypto at vger.kernel.org
> > ---
> >
> > .../devicetree/bindings/crypto/fsl-dcp.txt | 18 +
> > drivers/crypto/Kconfig | 17 +
> > drivers/crypto/Makefile | 1 +
> > drivers/crypto/mxs-dcp.c | 1100
> > ++++++++++++++++++++ 4 files changed, 1136 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/crypto/fsl-dcp.txt
>
> Since it creates new device tree bindings, please copy
> devicetree at vger.kernel.org, so that DT experts can have a chance to
> review the bindings.
OK, makes sense.
> Shawn
>
> > create mode 100644 drivers/crypto/mxs-dcp.c
> >
> > V2: Use dma_{un,}map_single instead of large coherent chunk
> >
> > Use the DMA mapping function on DCP buffers instead of the large
> > coherent chunk. This reduces the amount of cache
> > flushes/invalidations and write buffer drains as we do not need to
> > do this every time we operate with the coherent memory chunk, but
> > only when really needed.
> >
> > Make sure rctx is always inited
> >
> > The crypto request context is not zeroed out by the crypto API.
> > While this is not documented anywhere, it will produce arcane and
> > hard to debug problems. Fix the DCP code so that the request
> > context is always properly initialized.
> >
> > Minor code and coding-style fixes.
> >
> > diff --git a/Documentation/devicetree/bindings/crypto/fsl-dcp.txt
> > b/Documentation/devicetree/bindings/crypto/fsl-dcp.txt new file mode
> > 100644
> > index 0000000..ee8fbf9
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/crypto/fsl-dcp.txt
> > @@ -0,0 +1,18 @@
> > +Freescale DCP (Data Co-Processor) found on i.MX23/i.MX28 .
> > +
> > +Required properties:
> > +- compatible : Should be "fsl,<soc>-dcp"
> > +- reg : Should contain MXS DCP registers location and length
> > +- interrupts : Should contain MXS DCP interrupt numbers, VMI IRQ and DCP
> > IRQ + must be supplied, optionally Secure IRQ can be
> > present, but + is currently not implemented and not used.
> > +
> > +Example:
> > +
> > +dcp at 80028000 {
> > + compatible = "fsl,imx28-dcp", "fsl,imx23-dcp";
> > + reg = <0x80028000 0x2000>;
> > + interrupts = <52 53>;
> > + status = "okay";
> > +};
[...]
next prev parent reply other threads:[~2013-12-10 19:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-01 21:20 [PATCH 1/5] crypto: Fully restore ahash request before completing Marek Vasut
2013-12-01 21:20 ` Marek Vasut
2013-12-01 21:20 ` [PATCH 2/5] ARM: mxs: crypto: Remove the old DCP driver Marek Vasut
2013-12-01 21:20 ` Marek Vasut
2013-12-03 11:07 ` Shawn Guo
2013-12-03 11:07 ` Shawn Guo
2013-12-03 12:28 ` Marek Vasut
2013-12-03 12:28 ` Marek Vasut
2013-12-01 21:20 ` [PATCH V2 3/5] ARM: mxs: crypto: Add Freescale MXS " Marek Vasut
2013-12-01 21:20 ` Marek Vasut
2013-12-03 11:10 ` Shawn Guo
2013-12-03 11:10 ` Shawn Guo
2013-12-03 11:10 ` Shawn Guo
2013-12-10 19:19 ` Marek Vasut [this message]
2013-12-10 19:19 ` Marek Vasut
2013-12-01 21:20 ` [PATCH 4/5] ARM: mxs: dts: Enable DCP for MXS Marek Vasut
2013-12-01 21:20 ` Marek Vasut
2013-12-01 21:20 ` [PATCH 5/5] crypto: Sort drivers/crypto/Makefile Marek Vasut
2013-12-01 21:20 ` Marek Vasut
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=201312102019.22473.marex@denx.de \
--to=marex@denx.de \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@freescale.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=shawn.guo@linaro.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.