1. 07 Jul, 2017 1 commit
    • Alexandre Belloni's avatar
      rtc: add generic nvmem support · 697e5a47
      Alexandre Belloni authored
      Many RTCs have an on board non volatile storage. It can be battery backed
      RAM or an EEPROM. Use the nvmem subsystem to export it to both userspace
      and in-kernel consumers.
      
      This stays compatible with the previous (non documented) ABI that was using
      /sys/class/rtc/rtcx/device/nvram to export that memory. But will warn about
      the deprecation.
      Signed-off-by: 's avatarAlexandre Belloni <alexandre.belloni@free-electrons.com>
      697e5a47
  2. 31 May, 2017 1 commit
  3. 14 Mar, 2016 1 commit
  4. 25 Mar, 2015 1 commit
  5. 03 Jul, 2013 1 commit
    • Bernie Thompson's avatar
      rtc: add ability to push out an existing wakealarm using sysfs · 1df0a471
      Bernie Thompson authored
      This adds the ability for the rtc sysfs code to handle += characters at
      the beginning of a wakealarm setting string.  This will allow the user
      to attempt to push out an existing wakealarm by a provided amount.
      
      In the case that the += characters are provided but the alarm is not
      active -EINVAL is returned.
      
      his is useful, at least for my purposes in suspend/resume testing.  The
      basic test goes something like:
      
      1. Set a wake alarm from userspace 5 seconds in the future
      
      2. Start the suspend process (echo mem > /sys/power/state)
      
      3. After ~2.5 seconds if userspace is still running (using another
         thread to check this), move the wake alarm 5 more seconds
      
      If the "move" involves an unset of the wakealarm then there's a period
         of time where the system is midway through suspending but has no wake
         alarm.  It will get stuck.
      
      We'd rather not remove the "move" since the idea is to avoid a cancelled
      suspend when the alarm fires _during_ suspend.  It is difficult for the
      test to tell the difference between a suspend that was cancelled because
      the alarm fired too early and a suspend that was
      Signed-off-by: 's avatarBernie Thompson <bhthompson@chromium.org>
      Cc: Alessandro Zummo <a.zummo@towertech.it>
      Cc: Doug Anderson <dianders@chromium.org>
      Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
      Signed-off-by: 's avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: 's avatarLinus Torvalds <torvalds@linux-foundation.org>
      1df0a471
  6. 05 Oct, 2012 1 commit
  7. 09 Mar, 2011 1 commit
  8. 23 Sep, 2009 3 commits
  9. 06 Feb, 2008 2 commits
  10. 15 Nov, 2007 1 commit
  11. 17 Jul, 2007 1 commit
  12. 08 May, 2007 1 commit
    • David Brownell's avatar
      rtc: remove "RTC_ALM_SET mode" bugs · f8245c26
      David Brownell authored
      This fixes a common glitch in how RTC drivers handle two "set alarm" modes,
      by getting rid of the surprising/hidden one that was rarely implemented
      correctly (and which could expose nonportable hardware-specific behavior).
      
      The glitch comes from the /dev/rtcX logic implementing the legacy
      RTC_ALM_SET (limited to 24 hours, needing RTC_AIE_ON) ioctl on top of the
      RTC driver call providing access to the newer RTC_WKALM_SET (without those
      limitations) by initializing the day/month/year fields to be invalid ...
      that second mode.
      
      Now, since few RTC drivers check those fields, and most hardware misbehaves
      when faced with invalid date fields, many RTC drivers will set bogus alarm
      times on those RTC_ALM_SET code paths.  (Several in-tree drivers have that
      issue, and I also noticed it with code reviews on several new RTC drivers.)
      
      This patch ensures that RTC drivers never see such invalid alarm fields, by
      moving some logic out of rtc-omap into the RTC_ALM_SET code and adding an
      explicit check (which will prevent the issue on other code paths).
      Signed-off-by: 's avatarDavid Brownell <dbrownell@users.sourceforge.net>
      Cc: Scott Wood <scottwood@freescale.com>
      Cc: Alessandro Zummo <a.zummo@towertech.it>
      Signed-off-by: 's avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: 's avatarLinus Torvalds <torvalds@linux-foundation.org>
      f8245c26
  13. 11 Feb, 2007 1 commit
  14. 25 Nov, 2006 1 commit
  15. 25 Jun, 2006 1 commit
  16. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4