If we fail to prepare the ux500-hash clock before enabling it the
platform will fail to boot. Here we insure this happens.

Cc: Herbert Xu <herb...@gondor.apana.org.au>
Cc: David S. Miller <da...@davemloft.net>
Cc: Andreas Westin <andreas.wes...@stericsson.com>
Cc: linux-cry...@vger.kernel.org
Acked-by: Arnd Bergmann <a...@arndb.de>
Acked-by: Ulf Hansson <ulf.hans...@linaro.org>
Signed-off-by: Lee Jones <lee.jo...@linaro.org>
---
 drivers/crypto/ux500/hash/hash_core.c |   12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/drivers/crypto/ux500/hash/hash_core.c 
b/drivers/crypto/ux500/hash/hash_core.c
index cf55089..4b02428 100644
--- a/drivers/crypto/ux500/hash/hash_core.c
+++ b/drivers/crypto/ux500/hash/hash_core.c
@@ -1726,11 +1726,17 @@ static int ux500_hash_probe(struct platform_device 
*pdev)
                goto out_regulator;
        }
 
+       ret = clk_prepare(device_data->clk);
+       if (ret) {
+               dev_err(dev, "[%s] clk_prepare() failed!", __func__);
+               goto out_clk;
+       }
+
        /* Enable device power (and clock) */
        ret = hash_enable_power(device_data, false);
        if (ret) {
                dev_err(dev, "[%s]: hash_enable_power() failed!", __func__);
-               goto out_clk;
+               goto out_clk_unprepare;
        }
 
        ret = hash_check_hw(device_data);
@@ -1762,6 +1768,9 @@ static int ux500_hash_probe(struct platform_device *pdev)
 out_power:
        hash_disable_power(device_data, false);
 
+out_clk_unprepare:
+       clk_unprepare(device_data->clk);
+
 out_clk:
        clk_put(device_data->clk);
 
@@ -1826,6 +1835,7 @@ static int ux500_hash_remove(struct platform_device *pdev)
                dev_err(dev, "[%s]: hash_disable_power() failed",
                        __func__);
 
+       clk_unprepare(device_data->clk);
        clk_put(device_data->clk);
        regulator_put(device_data->regulator);
 
-- 
1.7.10.4

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to