1. 22 2月, 2020 2 次提交
    • G
      crypto: ccree - simplify Runtime PM handling · 8c7849a3
      Geert Uytterhoeven 提交于
      Currently, a large part of the probe function runs before Runtime PM is
      enabled.  As the driver manages the device's clock manually, this may
      work fine on some systems, but may break on platforms with a more
      complex power hierarchy.
      
      Fix this by moving the initialization of Runtime PM before the first
      register access (in cc_wait_for_reset_completion()), and putting the
      device to sleep only after the last access (in cc_set_ree_fips_status()).
      
      This allows to remove the pm_on flag, which was used to track manually
      if Runtime PM had been enabled or not.
      Remove the cc_pm_{init,go,fini}() wrappers, as they are called only
      once, and obscure operation.
      Signed-off-by: NGeert Uytterhoeven <geert+renesas@glider.be>
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      8c7849a3
    • G
      crypto: ccree - clean up clock handling · 2f272ef3
      Geert Uytterhoeven 提交于
      Use devm_clk_get_optional() instead of devm_clk_get() and explicit
      optional clock handling.
      As clk_prepare_enable() and clk_disable_unprepare() handle optional
      clocks fine, the cc_clk_on() and cc_clk_off() wrappers can be removed.
      
      While at it, use the new "%pe" format specifier to print error codes.
      Signed-off-by: NGeert Uytterhoeven <geert+renesas@glider.be>
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      2f272ef3
  2. 22 1月, 2020 4 次提交
  3. 11 12月, 2019 1 次提交
  4. 26 7月, 2019 1 次提交
  5. 27 6月, 2019 2 次提交
  6. 25 4月, 2019 4 次提交
  7. 08 2月, 2019 1 次提交
    • G
      crypto: ccree - fix resume race condition on init · 1358c13a
      Gilad Ben-Yossef 提交于
      We were enabling autosuspend, which is using data set by the
      hash module, prior to the hash module being inited, casuing
      a crash on resume as part of the startup sequence if the race
      was lost.
      
      This was never a real problem because the PM infra was using low
      res timers so we were always winning the race, until commit 8234f673
      ("PM-runtime: Switch autosuspend over to using hrtimers") changed that :-)
      
      Fix this by seperating the PM setup and enablement and doing the
      latter only at the end of the init sequence.
      Signed-off-by: NGilad Ben-Yossef <gilad@benyossef.com>
      Cc: Vincent Guittot <vincent.guittot@linaro.org>
      Cc: stable@kernel.org # v4.20
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      1358c13a
  8. 15 2月, 2018 2 次提交
  9. 15 1月, 2018 1 次提交
  10. 09 1月, 2018 2 次提交
  11. 08 1月, 2018 2 次提交
  12. 19 12月, 2017 3 次提交
  13. 13 12月, 2017 4 次提交
  14. 27 11月, 2017 5 次提交
  15. 06 11月, 2017 2 次提交
  16. 04 10月, 2017 2 次提交
  17. 17 9月, 2017 1 次提交
  18. 28 7月, 2017 1 次提交