diff options
author | Paweł Chmiel <pawel.mikolaj.chmiel@gmail.com> | 2020-10-24 17:43:46 +0200 |
---|---|---|
committer | Sylwester Nawrocki <s.nawrocki@samsung.com> | 2021-04-07 11:37:17 +0200 |
commit | 34138a59b92c1a30649a18ec442d2e61f3bc34dd (patch) | |
tree | 7b19818e2bd446505c6b7d7a5e256378c9dabb23 /drivers/rtc/rtc-fm3130.c | |
parent | a38fd8748464831584a19438cbb3082b5a2dab15 (diff) | |
download | linux-34138a59b92c1a30649a18ec442d2e61f3bc34dd.tar.gz linux-34138a59b92c1a30649a18ec442d2e61f3bc34dd.tar.bz2 linux-34138a59b92c1a30649a18ec442d2e61f3bc34dd.zip |
clk: exynos7: Mark aclk_fsys1_200 as critical
This clock must be always enabled to allow access to any registers in
fsys1 CMU. Until proper solution based on runtime PM is applied
(similar to what was done for Exynos5433), mark that clock as critical
so it won't be disabled.
It was observed on Samsung Galaxy S6 device (based on Exynos7420), where
UFS module is probed before pmic used to power that device.
In this case defer probe was happening and that clock was disabled by
UFS driver, causing whole boot to hang on next CMU access.
Fixes: 753195a749a6 ("clk: samsung: exynos7: Correct CMU_FSYS1 clocks names")
Signed-off-by: Paweł Chmiel <pawel.mikolaj.chmiel@gmail.com>
Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
Link: https://lore.kernel.org/linux-clk/20201024154346.9589-1-pawel.mikolaj.chmiel@gmail.com
[s.nawrocki: Added comment in the code]
Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
Diffstat (limited to 'drivers/rtc/rtc-fm3130.c')
0 files changed, 0 insertions, 0 deletions