linux-toradex.git/drivers/rtc/rtc-ab8500.c, branch v5.18

rtc: ab8500: let the core handle the alarm resolution

2021-11-09T23:45:57+00:00

Tell the RTC core UIE are not supported because the resolution of the alarm
is a minute.

Note that this is in fact also fixing how the resolution is reported as the
previous test was simply ensuring the alarm was more than a minute in the
future while the register has a minute resolution.
This would be ok if the alarm was a countdown but ab8500_rtc_read_alarm
suggests otherwise and the AB8500 datasheet states that the RTC
documentation is not public.

Finally, the comment is wrong and what makes the UIE emulation work is
uie_unsupported being set.

Signed-off-by: Alexandre Belloni 
Acked-by: Linus Walleij 
Link: https://lore.kernel.org/r/20211107225458.111068-6-alexandre.belloni@bootlin.com

rtc: rework rtc_register_device() resource management

2020-11-19T11:50:12+00:00

rtc_register_device() is a managed interface but it doesn't use devres
by itself - instead it marks an rtc_device as "registered" and the devres
callback for devm_rtc_allocate_device() takes care of resource release.

This doesn't correspond with the design behind devres where managed
structures should not be aware of being managed. The correct solution
here is to register a separate devres callback for unregistering the
device.

While at it: rename rtc_register_device() to devm_rtc_register_device()
and add it to the list of managed interfaces in devres.rst. This way we
can avoid any potential confusion of driver developers who may expect
there to exist a corresponding unregister function.

Signed-off-by: Bartosz Golaszewski 
Signed-off-by: Alexandre Belloni 
Link: https://lore.kernel.org/r/20201109163409.24301-8-brgl@bgdev.pl

rtc: ab8500: switch to rtc_time64_to_tm/rtc_tm_to_time64

2020-03-16T10:12:11+00:00

Call the 64bit versions of rtc_tm time conversion.

Acked-by: Linus Walleij 
Link: https://lore.kernel.org/r/20200306010101.39517-1-alexandre.belloni@bootlin.com
Signed-off-by: Alexandre Belloni

treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 194

2019-05-30T18:29:22+00:00

Based on 1 normalized pattern(s):

  license terms gnu general public license gpl version 2

extracted by the scancode license scanner the SPDX license identifier

  GPL-2.0-only

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

Signed-off-by: Thomas Gleixner 
Reviewed-by: Allison Randal 
Reviewed-by: Alexios Zavras 
Reviewed-by: Steve Winslow 
Reviewed-by: Richard Fontana 
Cc: linux-spdx@vger.kernel.org
Link: https://lkml.kernel.org/r/20190528170027.447718015@linutronix.de
Signed-off-by: Greg Kroah-Hartman

rtc: ab8500: remove useless check

2018-09-28T12:36:49+00:00

rtc_time_to_tm always rturns a valid tm, there is no need to validate it.

Signed-off-by: Alexandre Belloni 
Acked-by: Linus Walleij 
Signed-off-by: Alexandre Belloni

rtc: ab8500: let the core handle range

2018-09-28T12:36:47+00:00

Let the core handle offsetting and windowing the RTC range.
The RTC has a 24 bit counter for minutes plus a seconds counter.
Keep the epoch at the beginning of 2000.

Signed-off-by: Alexandre Belloni 
Acked-by: Linus Walleij 
Signed-off-by: Alexandre Belloni

rtc: ab8500: use rtc_add_group

2018-09-28T12:36:44+00:00

Use rtc_add_group to add the sysfs group in a race free manner.

Signed-off-by: Alexandre Belloni 
Reviewed-by: Linus Walleij 
Signed-off-by: Alexandre Belloni

rtc: ab8500: Drop AB8540 support

2018-03-27T08:45:05+00:00

The AB8540 was an evolved version of the AB8500, but it was never
mass produced or put into products, only reference designs exist.
The upstream support was never completed and it is unlikely that
this will happen so drop the support for now to simplify
maintenance of the AB8500.

Cc: Loic Pallardy 
Signed-off-by: Linus Walleij 
Signed-off-by: Alexandre Belloni

rtc: stop validating rtc_time after rtc_time_to_tm

2018-03-01T09:49:41+00:00

rtc_time_to_tm never generates an invalid tm. It is not necessary to
validate it.

Signed-off-by: Alexandre Belloni

rtc: ab8500: remove misuse of IRQF_NO_SUSPEND flag

2015-11-08T13:12:25+00:00

The IRQF_NO_SUSPEND flag is used to identify the interrupts that should
be left enabled so as to allow them to work as expected during the
suspend-resume cycle, but doesn't guarantee that it will wake the system
from a suspended state, enable_irq_wake is recommended to be used for
the wakeup.

This patch removes the use of IRQF_NO_SUSPEND flags and uses newly
introduce PM wakeup APIs dev_pm_{set,clear}_wake_irq.

Cc: Linus Walleij 
Cc: Alessandro Zummo 
Cc: Alexandre Belloni 
Cc: rtc-linux@googlegroups.com
Signed-off-by: Sudeep Holla 
Acked-by: Linus Walleij 
Signed-off-by: Alexandre Belloni