Hi Aaro,
Dnia wtorek, 22 marca 2022 20:07:53 CET Aaro Koskinen pisze:
Hi,
On Tue, Mar 22, 2022 at 06:36:48PM +0200, Aaro Koskinen wrote:
On Mon, Mar 21, 2022 at 10:54:16PM +0100, Janusz Krzysztofik wrote:
In preparation for conversion of OMAP1 clocks to common clock framework, identify users of those clocks which don't call clk_prepare/unprepare() and update them to call clk_prepare_enable/clk_disable_unprepare() instead of just clk_enable/disable(), as required by CCF implementation of clock API.
v2: update still a few more OMAP specific drivers missed in v1,
- call clk_prepare/unprepare() just after/before clk_get/put() where it can make more sense than merging prepare/unprepare with enable/disable.
Something is still broken. When doing kexec (using CCF kernel), the kexec'ed kernel now hangs early (on 770):
[...]
[ 0.928863] calling omap1_init_devices+0x0/0x2c @ 1
It hangs in omap_sram_reprogram_clock() (<- omap1_select_table_rate() <- omap1_clk_late_init()).
I've reviewed my changes but haven't found anything suspicious. Could you please provide: - dmesg from both cold start and kexec, both non-CCF and CCF version, - contents of /sys/kernel/debug/clock/summary (non-CCF) after boot/kexec, - contents of /sys/kernel/debug/clk/clk_summary (CCF) after boot?
Thanks, Janusz
A.