Dear Maintainer,

I am using fake-hwclock to ensure the system clock is properly initialized during a boot on a Radxa Rock 3C single board computer.
The board does have a real time clock, but no buffer battery.
The solution is working great when the board is properly shutdown or rebooted, but when the board faces a power loss, the system clock will not be properly setup.

I do see in the journal logs that fake-hwclock is run, but it only sets the system clock and not the hardware clock as well. After the run the system clock
seems to be synchronized again with the hardware clock. Because fake-hwclock only sets the system clock, this values will be overwritten again.

My question now, why does fake-hwclock only sets the system clock and not also sets the hardware clock as well? That would solve such issues or race conditions during boot.
Maybe this feature can be handled like the FORCE configuration option with a flag.