set_rtc_time() cleanup / normalization
dan at embeddededge.com
Thu May 15 02:28:29 EST 2003
Gabriel Paubert wrote:
> Ask on the ntp lists first, I bet you'll upset a lot of people
> if you suggest it.
I'll bet no one is using it on a system that has an unpredictable
latency, interrupt generating, i2c RTC, either. :-)
The solution is to do like other architectures and allow (as Tom
suggested) a selectable rtc update function. Although I may use
a particular RTC driver, I may not want the update function that
comes along with it. All we need is an indirect function pointer
to the get/set functions that is initialized by the board set
up functions. By default they should be null functions, if you
want something else, put a pointer there.
The fact is the current rtc update functions are not suitable for
embedded boards that have to meet latency guarantees. They simply
add overhead, often in a bad way, even if implemented correctly.
Installing any kind of real-time enhancement (like RTLinux or RTAI)
will cause a failure of the rtc update model because the update thread of
control can be easily preempted.
The solution is easy, you can find examples in other architectures,
and we don't have to argue about it.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
More information about the Linuxppc-dev