SSS module on Exynos4210, Exynos5250 and Exynos5420 SoCs has added
features to the one on S5PV210. However with minor changes the s5p-sss.c
driver can be reused to support SSS modules on Exynos4 and 5 SoCs.
This patch set
1. Adds device tree support to the s5p-sss.c driver and Documentation
2. Adds code to support SSS module on Exynos4 and 5 SoCs
3. Adds device tree node to Exynos5250 and Exynos5420
4. Adds variant struct to handle the differences in SSS modules
5. Adds clk_prepare/clk_unprepare clocks to the s5p-sss.c driver
Note: Compatible "exynos4210-secss" should work for Exynos4412 and
Exynos5260 (Exynos5260, for which ARCH code is under review)
I couldn't test on Exynos4412 and Exynos4210 boards, Should be able to
test with addition of DT node and clocks support.
Naveen Krishna Ch (7): [crypto-2.6.git]
crypto:s5p-sss: Use platform_get_irq() instead of _byname()
crypto:s5p-sss: Kconfig: Let Exynos SoCs select SSS driver
crypto:s5p-sss: Look for the next request in the queue
crypto:s5p-sss: Add device tree support
crypto:s5p-sss: Add support for SSS module on Exynos
crypto:s5p-sss: validate iv before memcpy
crypto:s5p-sss: Use clk_prepare/clk_unprepare
Naveen Krishna Chatradhi (1): [samsung-clk.git]
clk: samsung exynos5250/5420: Add gate clock for SSS module
Naveen Krishna Chatradhi (1): [linuxsamsung.git]
ARM: dts: exynos5250/5420: add dt node for sss module
.../devicetree/bindings/clock/exynos5250-clock.txt | 1 +
.../devicetree/bindings/crypto/samsung-sss.txt | 35 +++++
arch/arm/boot/dts/exynos5250.dtsi | 8 ++
arch/arm/boot/dts/exynos5420.dtsi | 9 ++
drivers/clk/samsung/clk-exynos5250.c | 1 +
drivers/clk/samsung/clk-exynos5420.c | 4 +
drivers/crypto/Kconfig | 6 +-
drivers/crypto/s5p-sss.c | 145 +++++++++++++++-----
include/dt-bindings/clock/exynos5250.h | 1 +
9 files changed, 174 insertions(+), 36 deletions(-)
create mode 100644 Documentation/devicetree/bindings/crypto/samsung-sss.txt
--
1.7.9.5
--
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
