From: Andy W. <an...@si...> - 2013-10-14 20:34:58
|
Hi: For a few weeks I've been developing a driver that, as a side function, initializes and uses GPTimers 10 & 11. Today, for the first time, I consistently started getting this error with kernel 3.5: Jan 01 00:05:58 overo kernel: omap_timer omap_timer.10: omap2_dm_timer_set_src: clk_set_parent() to sys_ck FAILED Jan 01 00:05:58 overo kernel: foo: foo_clock_clk_out_init: unable to set OMAP dual-mode timer 10 functional clock source to source 0. Jan 01 00:05:58 overo kernel: foo: foo_clock_initialize: unable to init OMAP dual-mode timer to drive foo chip foo_clock input. Jan 01 00:05:58 overo kernel: foo: foo_driver_init: foo_clock init failed, err: -22. FWIW, err: -22 is -EINVAL. Subsequent attempts of unloading and reloading the module yield the same, but with err: -12, aka -ENOMEM. Looking at the current Functional clocks: root@overo:~# grep 'gpt1[10]_fck' /sys/kernel/debug/clock/summary gpt11_fck omap_32k_fck 32768 0 gpt10_fck omap_32k_fck 32768 0 But I really need: gpt11_fck sys_fck 13000000 0 gpt10_fck sys_fck 13000000 0 Again, my driver was able to set this, until I edited some unrelated driver code today and recompiled the module. Anyone have any insights into what might make clk_set_parent() unhappy? Regards, Andy |