Eric Lee / smarc-fsl-linux-kernel

15 Mar, 2016

1 commit

25 Mar, 2015

1 commit

  • 4a5fd8150   Documentation, split up rtc.txt into documentation and test file ... Browse Code »

    This patch splits rtc.txt into two separate files, one for the
    documentation itself, and the other for the rtctest.c file. The rtctest
    file is moved into the kernel tools/testing/selftests/timers directory.
    This will make automated testing easier. Note that the only difference in
    the rtc.txt file is that the location of the rtctest.c file has changed.

    Signed-off-by: Prarit Bhargava
    Acked-by: Jonathan Corbet
    Acked-by: John Stultz
    Cc: corbet@lwn.net
    Cc: rtc-linux@googlegroups.com
    Cc: linux-doc@vger.kernel.org
    Cc: a.zummo@towertech.it
    Cc: prarit@redhat.com
    Cc: john.stultz@linaro.org
    Cc: shuahkh@osg.samsung.com
    Signed-off-by: Shuah Khan

    Prarit Bhargava
     

04 Jul, 2013

1 commit

  • 1df0a4711   rtc: add ability to push out an existing wakealarm using sysfs ... Browse Code »

    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: Bernie Thompson
    Cc: Alessandro Zummo
    Cc: Doug Anderson
    Cc: "Rafael J. Wysocki"
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Bernie Thompson
     

06 Oct, 2012

1 commit

  • 92589c986   rtc-proc: permit the /proc/driver/rtc device to use other devices ... Browse Code »

    To get time information via /proc/driver/rtc, only the first device (rtc0)
    is used. If the rtcN (eg. rtc1 or rtc2) is used for the system clock,
    there is no way to get information of rtcN via /proc/driver/rtc. With
    this patch, the time data can be retrieved from the system clock RTC.

    If the RTC_HCTOSYS_DEVICE is not defined, then rtc0 is used by default.

    Signed-off-by: Milo(Woogyom) Kim
    Cc: Alessandro Zummo
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Kim, Milo
     

10 Mar, 2011

1 commit

23 Sep, 2009

3 commits

  • d8c1acb16   rtc: add boot_timesource sysfs attribute ... Browse Code »

    CONFIG_RTC_HCTOSYS allows the kernel to read the system time from the RTC
    at boot and resume, avoiding the need for userspace to do so.
    Unfortunately userspace currently has no way to know whether this
    configuration option is enabled and thus cannot sensibly choose whether to
    run hwclock itself or not. Add a hctosys sysfs attribute which indicates
    whether a given RTC set the system clock.

    Signed-off-by: Matthew Garrett
    Acked-by: Alessandro Zummo
    Cc: Mark Brown
    Cc: David Brownell
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Matthew Garrett
     
  • ea3d1606f   rtc: document the sysfs interface ... Browse Code »

    The sysfs interface to the RTC class drivers is currently undocumented.
    Add some basic documentation defining the semantics of the fields.

    Signed-off-by: Matthew Garrett
    Cc: Mark Brown
    Acked-by: Alessandro Zummo
    Cc: David Brownell
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Matthew Garrett
     
  • ad91fd854   rtc: update documentation wrt RTC_PIE/irq_set_state ... Browse Code »

    Signed-off-by: Mike Frysinger
    Cc: David Brownell
    Signed-off-by: Alessandro Zummo
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Mike Frysinger
     

07 Feb, 2008

2 commits

15 Nov, 2007

1 commit

  • 108b4c363   rtc: tweak driver documentation for rtc periodic ... Browse Code »

    The max_user_freq member is not really meant for RTC drivers to modify, so
    update the rtc documentation so drivers writers know what is expected of
    them when handling periodic events.

    Signed-off-by: Mike Frysinger
    Acked-by: Alessandro Zummo
    Cc: David Brownell
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Mike Frysinger
     

18 Jul, 2007

1 commit

09 May, 2007

1 commit

  • f8245c268   rtc: remove "RTC_ALM_SET mode" bugs ... Browse Code »

    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: David Brownell
    Cc: Scott Wood
    Cc: Alessandro Zummo
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    David Brownell
     

12 Feb, 2007

1 commit

  • 2b1cd4c43   [PATCH] some rtc documentation updates ... Browse Code »

    Fix typo when describing RTC_WKALM. Add some helpful pointers to people
    developing their own RTC driver. Change a bunch of the error messages in the
    test program to be a bit more helpful.

    Signed-off-by: Mike Frysinger
    Cc: Alessandro Zummo
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Mike Frysinger
     

26 Nov, 2006

1 commit

  • 7531d8faa   [PATCH] Documentation/rtc.txt updates (for rtc class) ... Browse Code »

    This updates the RTC documentation to summarize the two APIs now available:
    the old PC/AT one, and the new RTC class drivers. It also updates the
    included "rtctest.c" file to better meet Linux style guidelines, and to work
    with the new RTC drivers.

    Signed-off-by: David Brownell
    Acked-by: Alessandro Zummo
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    David Brownell
     

26 Jun, 2006

1 commit

17 Apr, 2005

1 commit

  • 1da177e4c   Linux-2.6.12-rc2 ... Browse Code »

    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!

    Linus Torvalds