[lkml]   [2001]   [Oct]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[RFC] RTC policy questions

I am currently working on porting the linux kernel to
the Shark, a StrongARM based computer (DNARD from digital)
that contains many parts known from PCs.

On the Shark I have to use the (PC-like) RealTimeClock as a
heartbeat source. This has two consequences:

1) No user may be allowed to alter the frequency of
the RTC interrupt or even turn it off.
AFAIK the alarm cannot be used, because it uses
the same irq.
2) I would like to use the set_rtc_irq_bit and
get_rtc_time functions from drivers/char/rtc.c in
include/asm-arm/arch-shark/time.h to setup the
rtc at bootup. That means that they cannot be
static in rtc.c.

a) I could avoid 2) by duplicating the functions in time.h
(it seems arch-ebsa285/time.h implements its own setup),
but I hate duplicating code.
b) I solved 1) by patching rtc.c to exclude the offending
code if CONFIG_ARCH_SHARK is defined. The only other way
I can think of would be to have a complete rtc driver
for the shark but that again would mean duplicating code.

What do you think? Is it ok to patch the rtc.c or would it be
better to duplicate the code? Are there more possible solutions
that I cannot think of?

I am using 2.4.12-ac6-rmk2 at the moment but the problem is
mostly version independent.

Thanks for all comments
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:11    [W:0.034 / U:3.012 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site