> From: Kurt Miller <k...@intricatesoftware.com> > Date: Thu, 26 Sep 2019 12:28:56 -0400
... > rkclock0 at mainbus0 > rkclock_set_parent: 0x000000b4 > rkclock_set_frequency: 0x000000c4 > rkclock_set_frequency: 0x000000c5 > rkclock_set_frequency: 0x000000ca > rkclock_set_frequency: 0x000000c1 > rkclock_set_frequency: 0x000000bf > rkclock_set_frequency: 0x000000c6 > rkclock_set_frequency: 0x000000c8 > rkclock_set_frequency: 0x000000c9 > rkclock_set_frequency: 0x000000c4 > rkclock_set_frequency: 0x000001ac > rkclock_set_frequency: 0x0000013c > rkclock_set_frequency: 0x000000c5 > rkclock_set_frequency: 0x00000198 > rkclock_set_frequency: 0x0000014a > rkclock_set_frequency: 0x000000ca > rkclock_set_frequency: 0x000001a9 > rkclock_set_frequency: 0x000000c1 > rkclock_set_frequency: 0x00000045 > rkclock_set_frequency: 0x000000bf > rkclock_set_frequency: 0x000000c6 > rkclock_set_frequency: 0x000000c8 > rkclock_set_frequency: 0x000000c9 > rkclock_set_frequency: 0x0000003e > rkclock_set_frequency: 0x00000149 > rkclock_set_frequency: 0x000000ce > rkclock_set_frequency: 0x00000140 > rkclock_set_frequency: 0x00000061 So one issue here that U-Boot isn't using the correct clock binding. So the numbers in the device tree don't match what our driver expects. Using a device tree from Linux (i.e. from the dtb package) should help. But I've got no idea whether that actually fixes the issue.
