[RFC] Option to disable mapping genrtc calls to ppc_md calls

Tom Rini trini at kernel.crashing.org
Wed Jan 19 05:33:37 EST 2005

On Tue, Jan 18, 2005 at 11:39:46AM -0600, Tolunay Orkun wrote:
> Dan Malek wrote:
> >
> >On Jan 18, 2005, at 11:15 AM, Tom Rini wrote:
> >
> >>On Mon, Jan 17, 2005 at 02:10:00PM -0700, Mark A. Greer wrote:
> >
> >
> >>>There are 2 reasons to not use the ppc_md.get_rtc_time() et. al. 
> >>>interfaces:
> >>>1) They are called before the i2c driver is initialized and even loaded
> >>>if its a module.
> >
> >
> >There are three reasons.  You don't want to use an I2c rtc clock at
> >all in these functions because they get can get called from the
> >clock interrupt to update the time in the rtc.  If it does happen to work,
> >it creates long latencies in the timer interrupt.  If the i2c requires an
> >interrupt, they system will crash or hang.
> >
> >A system using an I2C RTC should find some way to access the
> >clock from application space as a standard I2C device and manage
> >time/clock from the application, not from the kernel.
> This is exactly what I've done for our PPC405GP based Linux port 
> (2.4.25). I've written a clone of hwclock utility using /dev/i2c0 to 
> access Dallas RTC chip with I2C interface. I setthe system clock from 
> RTC within /etc/rcS (Busybox). It is less than perfect as early logs 
> have the date wrong but it was the direction of least resistance.
> Still, I think there should be a better standardized RTC interface to 
> help deal with I2C/SMBus based RTC chips.

There kind of is now, arch/arm/common/rtctime.c (thought of for I2C RTCs
and has alarm support).

Tom Rini

More information about the Linuxppc-dev mailing list