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. 11 8月, 2010 22 次提交
  3. 06 8月, 2010 1 次提交
  4. 05 8月, 2010 6 次提交
  5. 28 7月, 2010 1 次提交
  6. 27 7月, 2010 1 次提交
    • R
      ARM: Fix section build warnings for AMBA drivers · 2c39c9e1
      Russell King 提交于
      Found in the Versatile build:
      
      WARNING: drivers/built-in.o(.data+0x14c): Section mismatch in reference from the variable pl061_gpio_driver to the (unknown reference) .init.data:(unknown)
      The variable pl061_gpio_driver references
      the (unknown reference) __initdata (unknown)
      
      WARNING: drivers/built-in.o(.data+0x40f8): Section mismatch in reference from the variable pl011_driver to the (unknown reference) .init.data:(unknown)
      The variable pl011_driver references
      the (unknown reference) __initdata (unknown)
      
      WARNING: drivers/built-in.o(.data+0x5ab4): Section mismatch in reference from the variable pl031_driver to the (unknown reference) .init.data:(unknown)
      The variable pl031_driver references
      the (unknown reference) __initdata (unknown)
      
      Basically, amba_id structures must not be __initdata.  Also fix:
      
      WARNING: drivers/built-in.o(.data+0x138): Section mismatch in reference from the variable pl061_gpio_driver to the function .init.text:pl061_probe()
      The variable pl061_gpio_driver references
      the function __init pl061_probe()
      
      which is an incorrectly annotated probe function.  Fix it to reflect
      the other AMBA bus probe functions by removing the __init attributation.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      2c39c9e1
  7. 19 7月, 2010 1 次提交
  8. 30 6月, 2010 1 次提交
  9. 28 6月, 2010 1 次提交
  10. 17 6月, 2010 1 次提交
  11. 05 6月, 2010 2 次提交
  12. 03 6月, 2010 2 次提交