Am Mittwoch, 11. November 2015, 14:35:55 schrieb Zain Wang: > This commit support three cipher(AES/DES/DES3) and two chainmode(ecb/cbc), > and the more algorithms and new hash drivers will be added later on. I gave this a spin using tcrypt on my rk3288 chromebook and it seems to work nicely for modes 200 (aes), 201 (des3) and 204 (des), so this series Tested-by: Heiko Stuebner <heiko@xxxxxxxxx> > > Changed in v3: > - add OF depended in Kconfig > - rename some variate > - add reset property > - remove crypto_p variate > > Changed in v2: > - remove some part about hash > - add weak key detection > - changed some variate's type > > Changed in v1: > - modify some variate's name > - modify some variate's type > - modify some return value > - remove or modify some print info > - use more dev_xxx in probe > - modify the prio of cipher > - add Kconfig > > Zain Wang (4): > crypto: rockchip/crypto - add DT bindings documentation > clk: rockchip: set an ID for crypto clk > Crypto: rockchip/crypto - add crypto driver for rk3288 > ARM: dts: rockchip: Add Crypto node for rk3288 > > .../devicetree/bindings/crypto/rockchip-crypto.txt | 29 ++ > arch/arm/boot/dts/rk3288.dtsi | 12 + > drivers/clk/rockchip/clk-rk3288.c | 2 +- > drivers/crypto/Kconfig | 11 + > drivers/crypto/Makefile | 1 + > drivers/crypto/rockchip/Makefile | 3 + > drivers/crypto/rockchip/rk3288_crypto.c | 392 +++++++++++++++ > drivers/crypto/rockchip/rk3288_crypto.h | 220 +++++++++ > drivers/crypto/rockchip/rk3288_crypto_ablkcipher.c | 527 +++++++++++++++++++++ > include/dt-bindings/clock/rk3288-cru.h | 1 + > 10 files changed, 1197 insertions(+), 1 deletion(-) > create mode 100644 Documentation/devicetree/bindings/crypto/rockchip-crypto.txt > create mode 100644 drivers/crypto/rockchip/Makefile > create mode 100644 drivers/crypto/rockchip/rk3288_crypto.c > create mode 100644 drivers/crypto/rockchip/rk3288_crypto.h > create mode 100644 drivers/crypto/rockchip/rk3288_crypto_ablkcipher.c > > -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
