UbiquitousOS
/
OpenCloudOS-Kernel
mirror of https://gitee.com/OpenCloudOS/OpenCloudOS-Kernel.git
11
0
Fork 0
Code Issues Projects Releases Wiki Activity

crypto: mv_cesa - explicitly define kirkwood and dove compatible strings 

We are about to add a new driver to support new features like using the
TDMA engine to offload the CPU.
Orion, Dove and Kirkwood platforms are already using the mv_cesa driver,
but Orion SoCs do not embed the TDMA engine, which means we will have to
differentiate them if we want to get TDMA support on Dove and Kirkwood.
In the other hand, the migration from the old driver to the new one is not
something all people are willing to do without first auditing the new
driver.
Hence we have to support the new compatible in the mv_cesa driver so that
new platforms with updated DTs can still attach their crypto engine device
to this driver.

Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
This commit is contained in:
Boris BREZILLON 2015-06-18 15:46:19 +02:00 committed by Herbert Xu
parent 51b44fc811
commit 1fa2e9ae1d
2 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
Documentation/devicetree/bindings/crypto/mv_cesa.txt
View File

@ -1,7 +1,10 @@
Marvell Cryptographic Engines And Security Accelerator Marvell Cryptographic Engines And Security Accelerator
Required properties: Required properties:
- compatible : should be "marvell,orion-crypto" - compatible: should be one of the following string
"marvell,orion-crypto"
"marvell,kirkwood-crypto"
"marvell,dove-crypto"
- reg: base physical address of the engine and length of memory mapped - reg: base physical address of the engine and length of memory mapped
region. Can also contain an entry for the SRAM attached to the CESA, region. Can also contain an entry for the SRAM attached to the CESA,
but this representation is deprecated and marvell,crypto-srams should but this representation is deprecated and marvell,crypto-srams should

4
drivers/crypto/mv_cesa.c
View File

@ -1034,7 +1034,7 @@ static int mv_cesa_get_sram(struct platform_device *pdev,
&sram_size); &sram_size);
cp->sram_size = sram_size; cp->sram_size = sram_size;
cp->sram_pool = of_get_named_gen_pool(&pdev->dev.of_node, cp->sram_pool = of_get_named_gen_pool(pdev->dev.of_node,
"marvell,crypto-srams", 0); "marvell,crypto-srams", 0);
if (cp->sram_pool) { if (cp->sram_pool) {
cp->sram = gen_pool_dma_alloc(cp->sram_pool, sram_size, cp->sram = gen_pool_dma_alloc(cp->sram_pool, sram_size,
@ -1197,6 +1197,8 @@ static int mv_remove(struct platform_device *pdev)
static const struct of_device_id mv_cesa_of_match_table[] = { static const struct of_device_id mv_cesa_of_match_table[] = {
{ .compatible = "marvell,orion-crypto", }, { .compatible = "marvell,orion-crypto", },
{ .compatible = "marvell,kirkwood-crypto", },
{ .compatible = "marvell,dove-crypto", },
{} {}
}; };
MODULE_DEVICE_TABLE(of, mv_cesa_of_match_table); MODULE_DEVICE_TABLE(of, mv_cesa_of_match_table);