1. 11 12月, 2010 1 次提交
    • J
      RTC: Rework RTC code to use timerqueue for events · 6610e089
      John Stultz 提交于
      This patch reworks a large portion of the generic RTC code
      to in-effect virtualize the rtc interrupt code.
      
      The current RTC interface is very much a raw hardware interface.
      Via the proc, /dev/, or sysfs interfaces, applciations can set
      the hardware to trigger interrupts in one of three modes:
      
      AIE: Alarm interrupt
      UIE: Update interrupt (ie: once per second)
      PIE: Periodic interrupt (sub-second irqs)
      
      The problem with this interface is that it limits the RTC hardware
      so it can only be used by one application at a time.
      
      The purpose of this patch is to extend the RTC code so that we can
      multiplex multiple applications event needs onto a single RTC device.
      This is done by utilizing the timerqueue infrastructure to manage
      a list of events, which cause the RTC hardware to be programmed
      to fire an interrupt for the next event in the list.
      
      In order to preserve the functionality of the exsting proc,/dev/ and
      sysfs interfaces, we emulate the different interrupt modes as follows:
      
      AIE: We create a rtc_timer dedicated to AIE mode interrupts. There is
      only one per device, so we don't change existing interface semantics.
      
      UIE: Again, a dedicated rtc_timer, set for periodic mode, is used
      to emulate UIE interrupts. Again, only one per device.
      
      PIE: Since PIE mode interrupts fire faster then the RTC's clock read
      granularity, we emulate PIE mode interrupts using a hrtimer. Again,
      one per device.
      
      With this patch, the rtctest.c application in Documentation/rtc.txt
      passes fine on x86 hardware. However, there may very well still be
      bugs, so greatly I'd appreciate any feedback or testing!
      Signed-off-by: NJohn Stultz <john.stultz@linaro.org>
      LKML Reference: <1290136329-18291-4-git-send-email-john.stultz@linaro.org>
      Acked-by: NAlessandro Zummo <a.zummo@towertech.it>
      Reviewed-by: NThomas Gleixner <tglx@linutronix.de>
      CC: Alessandro Zummo <a.zummo@towertech.it>
      CC: Thomas Gleixner <tglx@linutronix.de>
      CC: Richard Cochran <richardcochran@gmail.com>
      6610e089
  2. 12 10月, 2009 1 次提交
  3. 20 6月, 2009 1 次提交
  4. 07 1月, 2009 3 次提交
  5. 05 1月, 2009 1 次提交
  6. 07 11月, 2008 1 次提交
  7. 31 7月, 2008 1 次提交
  8. 22 7月, 2008 1 次提交
  9. 05 7月, 2008 1 次提交
    • D
      rtc: rtc_read_alarm() handles wraparound · a01cc657
      David Brownell 提交于
      While 0e36a9a4 ("rtc: fix readback from
      /sys/class/rtc/rtc?/wakealarm") made sure that active alarms were never
      returned with invalid "wildcard" fields (negative), it can still report
      (wrongly) that the alarm triggers in the past.
      
      Example, if it's now 10am, an alarm firing at 5am will be triggered
      TOMORROW not today.  (Which may also be next month or next year...)
      
      This updates that alarm handling in three ways:
      
        * Handle alarm rollover in the common cases of RTCs that don't
          support matching on all date fields.
      
        * Skip the invalid-field logic when it's not needed.
      
        * Minor bugfix ... tm_isdst should be ignored, it's one of the
          fields Linux doesn't maintain.
      
      A warning is emitted for some of the unhandled rollover cases, but the
      possible combinations are a bit too numerous to handle every bit of
      potential hardware and firmware braindamage.
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Cc: Mark Lord <lkml@rtr.ca>
      Acked-by: NAlessandro Zummo <a.zummo@towertech.it>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      a01cc657
  10. 25 1月, 2008 1 次提交
  11. 06 12月, 2007 1 次提交
  12. 30 11月, 2007 1 次提交
  13. 17 10月, 2007 3 次提交
  14. 09 5月, 2007 3 次提交
  15. 02 3月, 2007 1 次提交
  16. 26 11月, 2006 2 次提交
  17. 26 6月, 2006 1 次提交
  18. 28 3月, 2006 1 次提交