On Dec 4, 2007 11:41 AM, Alessandro Zummo <[email protected]> wrote: > it should be EINVAL. at least it is wat rtc-cmos does when the value > is invalid. in the example rtc test code (Documentation/rtc.txt), would it be useful to handle EINVAL ? if the freq isnt supported, just say "hardware does not support frequency %i" and continue on to try the next freq ? the current code just does: perror("RTC_IRQP_SET ioctl"); exit(errno); -mike -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- [PATCH 0/7] Blackfin On-Chip RTC driver updates
- From: Bryan Wu <[email protected]>
- [PATCH 1/7] Blackfin RTC driver: the frequency function is in units of Hz, not units of seconds, so lock our driver down to 1 Hz
- From: Bryan Wu <[email protected]>
- Re: [PATCH 1/7] Blackfin RTC driver: the frequency function is in units of Hz, not units of seconds, so lock our driver down to 1 Hz
- From: Alessandro Zummo <[email protected]>
- Re: [rtc-linux] Re: [PATCH 1/7] Blackfin RTC driver: the frequency function is in units of Hz, not units of seconds, so lock our driver down to 1 Hz
- From: "Mike Frysinger" <[email protected]>
- Re: [rtc-linux] Re: [PATCH 1/7] Blackfin RTC driver: the frequency function is in units of Hz, not units of seconds, so lock our driver down to 1 Hz
- From: Alessandro Zummo <[email protected]>
- [PATCH 0/7] Blackfin On-Chip RTC driver updates
- Prev by Date: dmapool patch series, version 2
- Next by Date: Re: [PATCH] ipwireless_cs driver for 4G PC Card
- Previous by thread: Re: [rtc-linux] Re: [PATCH 1/7] Blackfin RTC driver: the frequency function is in units of Hz, not units of seconds, so lock our driver down to 1 Hz
- Next by thread: [PATCH 5/7] Blackfin RTC driver: read_alarm() checks the enabled field, not the pending field.
- Index(es):
 |