From: Krzysztof Kozlowski <krzk@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Stefan Agner <stefan@agner.ch>,
Fabio Estevam <fabio.estevam@nxp.com>,
NXP Linux Team <linux-imx@nxp.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org
Subject: [PATCH 0/6] crypto: vf-crc - Add new driver (and required clk, DTS...)
Date: Thu, 30 Aug 2018 19:15:33 +0200 [thread overview]
Message-ID: <20180830171539.20008-1-krzk@kernel.org> (raw)
Hi,
Add new driver for Freescale/NXP Vybrid CRC HW accelerator along with
prerequisities:
1. Clock,
2. Bindings,
3. CRC16 test tables for testing.
Patch 3/6 (ARM: dts: vfxxx: Add node for CRC hardware block) depends on patch
2/6 (clk) so it should go in following cycle (after clk change hits mainline).
Best regards,
Krzysztof
Krzysztof Kozlowski (6):
dt-bindings: crypto: Add Freescale Vybrid CRC
clk: imx: vf610: Add CRC clock
ARM: dts: vfxxx: Add node for CRC hardware block
crypto: testmgr - Add CRC16 test tables
crypto - Group Freescale/NXP ARM architecture Kconfig entires together
crypto: vf-crc - Add new driver for Freescale Vybrid CRC
.../devicetree/bindings/crypto/fsl-vf610-crc.txt | 16 +
MAINTAINERS | 7 +
arch/arm/boot/dts/vfxxx.dtsi | 7 +
crypto/testmgr.c | 6 +
crypto/testmgr.h | 386 ++++++++++++++++++++
drivers/clk/imx/clk-vf610.c | 1 +
drivers/crypto/Kconfig | 42 ++-
drivers/crypto/Makefile | 1 +
drivers/crypto/vf-crc.c | 387 +++++++++++++++++++++
include/dt-bindings/clock/vf610-clock.h | 3 +-
include/linux/crc32poly.h | 7 +
11 files changed, 846 insertions(+), 17 deletions(-)
create mode 100644 Documentation/devicetree/bindings/crypto/fsl-vf610-crc.txt
create mode 100644 drivers/crypto/vf-crc.c
--
2.14.1
next reply other threads:[~2018-08-30 17:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 17:15 Krzysztof Kozlowski [this message]
2018-08-30 17:15 ` [PATCH 1/6] dt-bindings: crypto: Add Freescale Vybrid CRC Krzysztof Kozlowski
2018-08-30 17:15 ` [PATCH 2/6] clk: imx: vf610: Add CRC clock Krzysztof Kozlowski
2018-08-30 21:42 ` Stephen Boyd
2018-08-30 17:15 ` [PATCH 3/6] ARM: dts: vfxxx: Add node for CRC hardware block Krzysztof Kozlowski
2018-08-30 17:15 ` [PATCH 4/6] crypto: testmgr - Add CRC16 test tables Krzysztof Kozlowski
2018-08-30 17:15 ` [PATCH 5/6] crypto - Group Freescale/NXP ARM architecture Kconfig entires together Krzysztof Kozlowski
2018-08-30 17:15 ` [PATCH 6/6] crypto: vf-crc - Add new driver for Freescale Vybrid CRC Krzysztof Kozlowski
2018-08-31 7:39 ` Sascha Hauer
2018-08-31 11:07 ` Krzysztof Kozlowski
2018-08-31 13:36 ` Sascha Hauer
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=20180830171539.20008-1-krzk@kernel.org \
--to=krzk@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=herbert@gondor.apana.org.au \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--cc=stefan@agner.ch \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).