diff options
author | Stefan Agner <stefan.agner@toradex.com> | 2018-01-04 11:07:59 +0100 |
---|---|---|
committer | Max Krummenacher <max.krummenacher@toradex.com> | 2018-03-08 14:52:16 +0100 |
commit | b407d00f8f4fc613223c30931bfa263a3db91bcb (patch) | |
tree | b6e4adc332fb53c9793352fc5634d3b05e564c6a /arch/arm/boot | |
parent | d38c0bfd4d79012b4dfbf1342a4fa7c9fb07964f (diff) |
ARM: imx7d: clk: make sure OCOTP clock is always on
Some device make use of the OCOTP via syscon. While the OCOTP node
specifies a clock, in newer kernels the access via syscon does not
enable the clock! During the main boot phase this is not usually a
problem since the clock is initially on. However, after unused
clocks get disabled, any access leads to a freeze. This has been
observed when the i.MX Thermal driver probe has been deferred: The
driver tried to read the calibration data from OCOTP via syscon
and caused a system freeze.
In upstream Linux this has recently been resolved using the NVMEM
framework, see:
Commit ae6215576d6b ("thermal: imx: Add support for reading OCOTP
through nvmem")
Commit a6c856e9a8cd ("ARM: dts: imx6sx: Use nvmem-cells for tempmon")
Use a simpler work around by just adding the clock to the list of
clocks which should kept on.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Acked-by: Max Krummenacher <max.krummenacher@toradex.com>
Diffstat (limited to 'arch/arm/boot')
0 files changed, 0 insertions, 0 deletions