31 May, 2019

1 commit

  • Based on 1 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 as published by
    the free software foundation either version 2 of the license or at
    your option any later version

    extracted by the scancode license scanner the SPDX license identifier

    GPL-2.0-or-later

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

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

    Thomas Gleixner
     

18 May, 2018

3 commits

  • While the year is encoded on 32 bits in SYS_TOYWRITE1i/SYS_TOYREAD1. The
    Loongson 1c datasheet states that the range is from 0 to 99.

    The current code exceeds this range and seems to be working, I deduce that
    the leap year algorithm will fail in 2100.

    Anyway, alarm registers only encode the year on 14 bits so with alarm
    support, the range will always be limited to 0 to 16383.

    Signed-off-by: Alexandre Belloni

    Alexandre Belloni
     
  • The error handling in ls1x_rtc_probe used to release resources but since
    it is using devm functions, it only returns a value. Make the code clearer
    by returning directly instead of using goto.

    Signed-off-by: Alexandre Belloni

    Alexandre Belloni
     
  • This allows for future improvement of the driver.

    Signed-off-by: Alexandre Belloni

    Alexandre Belloni
     

04 May, 2018

1 commit

  • The loongson1 platform is 32-bit, so storing a time value in 32 bits
    suffers from limited range. In this case it is likely to be correct
    until 2106, but it's better to avoid the limitation and just use
    the time64_t based mktime64() and rtc_time64_to_tm() interfaces.

    The hardware uses a 32-bit year number, and time64_t can cover that
    entire range.

    Signed-off-by: Arnd Bergmann
    Signed-off-by: Alexandre Belloni

    Arnd Bergmann
     

01 Mar, 2018

1 commit


12 Jan, 2017

1 commit

  • Declare rtc_class_ops structures as const as they are only passed
    as an argument to the function devm_rtc_device_register. This argument
    is of type const struct rtc_class_ops *, so rtc_class_ops structures
    having this property can be declared const.
    Done using Coccinelle:

    @r1 disable optional_qualifier @
    identifier i;
    position p;
    @@
    static struct rtc_class_ops i@p = {...};

    @ok1@
    identifier r1.i;
    position p;
    @@
    devm_rtc_device_register(...,&i@p,...)

    @bad@
    position p!={r1.p,ok1.p};
    identifier r1.i;
    @@
    i@p

    @depends on !bad disable optional_qualifier@
    identifier r1.i;
    @@
    +const
    struct rtc_class_ops i;

    Signed-off-by: Bhumika Goyal
    Signed-off-by: Alexandre Belloni

    Bhumika Goyal
     

22 Jun, 2015

1 commit

  • Currently, code of Loongson-2/3 is under loongson directory and code of
    Loongson-1 is under loongson1 directory. Besides, there are Kconfig
    options such as MACH_LOONGSON and MACH_LOONGSON1. This naming style is
    very ugly and confusing. Since Loongson-2/3 are both 64-bit general-
    purpose CPU while Loongson-1 is 32-bit SoC, we rename both file names
    and Kconfig symbols from loongson/loongson1 to loongson64/loongson32.

    [ralf@linux-mips.org: Resolve a number of simple conflicts.]

    Signed-off-by: Huacai Chen
    Cc: Steven J. Hill
    Cc: linux-mips@linux-mips.org
    Cc: Fuxin Zhang
    Cc: Zhangjin Wu
    Cc: Kelvin Cheung
    Patchwork: https://patchwork.linux-mips.org/patch/9790/
    Signed-off-by: Ralf Baechle

    Huacai Chen
     

20 Oct, 2014

1 commit


04 Jul, 2013

2 commits

  • After the switch to devm_ functions and the removal of
    rtc_device_unregister(), the 'remove' function does not do anything.
    Delete it.

    Signed-off-by: Sachin Kamat
    Cc: zhao zhang
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Sachin Kamat
     
  • The driver core clears the driver data to NULL after device_release or
    on probe failure, since commit 0998d063100 ("device-core: Ensure drvdata
    = NULL when no driver is bound"). Thus, it is not needed to manually
    clear the device driver data to NULL.

    Signed-off-by: Jingoo Han
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Jingoo Han
     

30 Apr, 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
     

24 Mar, 2012

1 commit