19 Jun, 2019

1 commit

  • Based on 2 normalized pattern(s):

    this program is free software you can redistribute it and or modify
    it under the terms of the gnu general public license version 2 as
    published by the free software foundation

    this program is free software you can redistribute it and or modify
    it under the terms of the gnu general public license version 2 as
    published by the free software foundation #

    extracted by the scancode license scanner the SPDX license identifier

    GPL-2.0-only

    has been chosen to replace the boilerplate/reference in 4122 file(s).

    Signed-off-by: Thomas Gleixner
    Reviewed-by: Enrico Weigelt
    Reviewed-by: Kate Stewart
    Reviewed-by: Allison Randal
    Cc: linux-spdx@vger.kernel.org
    Link: https://lkml.kernel.org/r/20190604081206.933168790@linutronix.de
    Signed-off-by: Greg Kroah-Hartman

    Thomas Gleixner
     

20 Oct, 2014

1 commit


24 Jan, 2014

1 commit

  • The current MAX8907 driver has two issues related to weekday value
    handling:

    1)

    The HW WEEKDAY register has range 0..6 rather than 1..7 as documented.
    Note that I validated the actual HW range by observing the HW register
    roll from 6->0 rather than 6->7->1 as would otherwise be expected.

    This matches Linux's tm_wday range of 0..6.

    When the CMOS RAM content is lost, the date returned from the device is
    2007-01-01 00:00:00, which is a Monday. The WEEKDAY register reads 1 in
    this case. This matches the numbering in Linux's tm_wday field.

    Hence we should write Linux's tm_wday value to the register without
    modifying it. Hence, remove the +1/-1 calculations for WEEKDAY/tm_wday.

    2)

    There's no need to make alarms match on the WEEKDAY register, since the
    other fields together uniquely define the alarm date/time. Ignoring the
    WEEKDAY value in the match isolates the driver from any incorrect value in
    the current time copy of the WEEKDAY register.

    Each change individually, or both together, solves an issue that I
    observed; "hwclock -r" would time out waiting for its alarm to fire if the
    CMOS RAM content had been lost, and hence the WEEKDAY register value
    mismatched what the driver expected it to be. "hwclock -w" would solve
    this by over-writing the HW default WEEKDAY register value with what the
    driver expected.

    Signed-off-by: Stephen Warren
    Cc:
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Stephen Warren
     

04 Jul, 2013

1 commit


30 Apr, 2013

2 commits


22 Feb, 2013

1 commit


04 Jan, 2013

1 commit

  • CONFIG_HOTPLUG is going away as an option. As a result, the __dev*
    markings need to be removed.

    This change removes the use of __devinit, __devexit_p, __devinitdata,
    __devinitconst, and __devexit from these drivers.

    Based on patches originally written by Bill Pemberton, but redone by me
    in order to handle some of the coding style issues better, by hand.

    Cc: Bill Pemberton
    Cc: Alessandro Zummo
    Cc: Srinidhi Kasagar
    Cc: Linus Walleij
    Cc: Mike Frysinger
    Cc: Wan ZongShun
    Cc: Guan Xuetao
    Cc: Mark Brown
    Signed-off-by: Greg Kroah-Hartman

    Greg Kroah-Hartman
     

06 Oct, 2012

1 commit

  • The MAX8907 is an I2C-based power-management IC containing voltage
    regulators, a reset controller, a real-time clock, and a touch-screen
    controller.

    The driver is based on an original by or fixed by:
    * Tom Cherry
    * Prashant Gaikwad
    * Joseph Yoon

    During upstreaming, I (swarren):
    * Converted to regmap.
    * Fixed handling of RTC_HOUR register containing 12.
    * Fixed handling of RTC_WEEKDAY register.
    * General cleanup.

    Signed-off-by: Stephen Warren
    Cc: Tom Cherry
    Cc: Prashant Gaikwad
    Cc: Joseph Yoon
    Cc: Alessandro Zummo
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Stephen Warren