On Thu, Apr 30, 2015 at 10:44:07PM +0200, Sebastian Hesselbarth wrote:[...]
What I noticed about your clk2 that you always measure as 0 Hz is
that none of your clocks is prepared/enabled.
Currently, the si5351 driver only ensures the output is enabled
when si5351_clkout_prepare() is called.
As long as you do not have a clk consumer that properly prepare/enables
the clock output, it may remain disabled.
We should probably have additional DT properties and corresponding
pdata to force clkoutN always on.
Does the silabs,disable-state of 3 (SI5351_DISABLE_NEVER) take care
Otherwise is there a simple registration that will do this?
It should be noted that if I program the device's register map in the
bootloader the device keeps the correct frequency outputs.
"keeps"? You mean "generates", don't you?
Yes the clocks are generated and do not get effected by the driver.