Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 20 10月, 2007 1 次提交
  3. 17 10月, 2007 1 次提交
  5. 01 8月, 2007 2 次提交
  7. 22 7月, 2007 2 次提交
  9. 20 7月, 2007 1 次提交
  11. 18 7月, 2007 9 次提交
  13. 10 7月, 2007 1 次提交
  15. 17 5月, 2007 1 次提交
  17. 11 5月, 2007 2 次提交
  19. 10 5月, 2007 1 次提交
  21. 09 5月, 2007 8 次提交
  23. 08 5月, 2007 1 次提交
  25. 05 3月, 2007 1 次提交
    • R
      [ARM] rtc-pcf8583: Final fixes for this RTC on RiscPC · bb71f99f
      由 Russell King 提交于 
      Replace the I2C bus address, as per drivers/acorn/char/pcf8583.c.

Also, since this driver also contains Acorn RiscPC specific code
for obtaining the current year from the SRAM (and updating the
platform specific checksum when writing new data back) this is
NOT a platform independent driver.

Document it as such, and update the dependencies to reflect this
fact.
Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      bb71f99f
  27. 21 2月, 2007 1 次提交
  29. 12 2月, 2007 1 次提交
    • D
      [PATCH] RTC framework driver for CMOS RTCs · 7be2c7c9
      由 David Brownell 提交于 
      This is an "RTC framework" driver for the "CMOS" RTCs which are standard on
PCs and some other platforms.  That's MC146818 compatible silicon.
Advantages of this vs.  drivers/char/rtc.c (use one _or_ the other, only
one will be able to claim the RTC irq) include:

 - This leverages both the new RTC framework and the driver model; both
   PNPACPI and platform device modes are supported.  (A separate patch
   creates a platform device on PCs where PNPACPI isn't configured.)

 - It supports common extensions like longer alarms.  (A separate patch
   exports that information from ACPI through platform_data.)

 - Likewise, system wakeup events use "real driver model support", with
   policy control via sysfs "wakeup" attributes and and using normal rtc
   ioctls to manage wakeup.  (Patch in the works.  The ACPI hooks are
   known; /proc/acpi/alarm can vanish.  Making it work with EFI will
   be a minor challenge to someone with e.g. a MiniMac.)

It's not yet been tested on non-x86 systems, without ACPI, or with HPET.
And the RTC framework will surely have teething pains on "mainstream"
PC-based systems (though must embedded Linux systems use it heavily), not
limited to sorting out the "/dev/rtc0" issue (udev easily tweaked).  Also,
the ALSA rtctimer code doesn't use the new RTC API.

Otherwise, this should be a no-known-regressions replacement for the old
drivers/char/rtc.c driver, and should help the non-embedded distros (and
the new timekeeping code) start to switch to the framework.

Note also that any systems using "rtc-m48t86" are candidates to switch over
to this more functional driver; the platform data is different, and the way
bytes are read is different, but otherwise those chips should be compatible.

[akpm@osdl.org: sparc32 fix]
[akpm@osdl.org: sparc64 fix]
Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
Cc: Woody Suwalski <woodys@xandros.com>
Cc: Alessandro Zummo <alessandro.zummo@towertech.it>
Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      7be2c7c9
  31. 11 12月, 2006 1 次提交
  33. 08 12月, 2006 2 次提交
  35. 01 10月, 2006 1 次提交
  37. 30 9月, 2006 1 次提交
  39. 27 9月, 2006 1 次提交
  41. 15 7月, 2006 1 次提交