Messages in this thread | | | Date | Tue, 22 Feb 2011 21:05:22 +0000 | From | Mark Brown <> | Subject | Re: [rtc-linux] [PATCH 04/10] RTC: Cleanup rtc_class_ops->read_alarm() |
| |
On Tue, Feb 22, 2011 at 12:22:54PM -0800, john stultz wrote:
> In some ways it does complicate things, but in others it greatly > simplifies it. You don't have to have 80 drivers each implementing their > own code to set a mode that isn't used. Everyone is using the common > kernel code, so bugs are shared and thus found and fixed faster. > Features can be more easily added, as the limitations of specific > hardware have to be more formally expressed, rather then having to > change 80 drivers that opaquely work around their specific hardware > issues. Also, applications are easier to port, since there are less > platform specific differences.
I agree that it's a win for things like UIE - the reason it worries me for alarms (and the RTC time itself) is that full emulation requires us to do things over reboots, including the support for having multiple alarms scheduled which isn't available on most hardware at all.
| |