summaryrefslogtreecommitdiffstats
path: root/drivers/crypto/s5p-sss.c
diff options
context:
space:
mode:
authorKrzysztof Kozlowski <krzk@kernel.org>2021-02-12 17:35:26 +0100
committerHerbert Xu <herbert@gondor.apana.org.au>2021-03-07 15:13:17 +1100
commit664b0f41ce2e8286c471fd8865d005f594733bdc (patch)
tree7d22d9572a10c8d2532df78d8cd0777f9c2c1452 /drivers/crypto/s5p-sss.c
parent1dbc6a1e25be8575d6c4114d1d2b841a796507f7 (diff)
downloadlinux-stable-664b0f41ce2e8286c471fd8865d005f594733bdc.tar.gz
linux-stable-664b0f41ce2e8286c471fd8865d005f594733bdc.tar.bz2
linux-stable-664b0f41ce2e8286c471fd8865d005f594733bdc.zip
crypto: s5p-sss - initialize APB clock after the AXI bus clock for SlimSSS
The driver for Slim Security Subsystem (SlimSSS) on Exynos5433 takes two clocks - aclk (AXI/AHB clock) and pclk (APB/Advanced Peripheral Bus clock). The "aclk", as main high speed bus clock, is enabled first. Then the "pclk" is enabled. However the driver assigned reversed names for lookup of these clocks from devicetree, so effectively the "pclk" was enabled first. Although it might not matter in reality, the correct order is to enable first main/high speed bus clock - "aclk". Also this was the intention of the actual code. Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'drivers/crypto/s5p-sss.c')
-rw-r--r--drivers/crypto/s5p-sss.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/crypto/s5p-sss.c b/drivers/crypto/s5p-sss.c
index 682c8a450a57..8ed08130196f 100644
--- a/drivers/crypto/s5p-sss.c
+++ b/drivers/crypto/s5p-sss.c
@@ -401,7 +401,7 @@ static const struct samsung_aes_variant exynos_aes_data = {
static const struct samsung_aes_variant exynos5433_slim_aes_data = {
.aes_offset = 0x400,
.hash_offset = 0x800,
- .clk_names = { "pclk", "aclk", },
+ .clk_names = { "aclk", "pclk", },
};
static const struct of_device_id s5p_sss_dt_match[] = {