linux-toradex.git/drivers/rtc/rtc-pcf8563.c, branch v5.16

rtc: pcf8563: Fix the datasheet URL

2021-06-20T21:48:35+00:00

The current datasheet URL is no longer valid.

Replace with a valid one.

Signed-off-by: Fabio Estevam 
Signed-off-by: Alexandre Belloni 
Link: https://lore.kernel.org/r/20210603143447.2223353-3-festevam@gmail.com

rtc: pcf8563: Add NXP PCA8565 compatible

2021-02-13T20:51:05+00:00

The NXP PCA8565 is software compatible with the NXP PCF8563,
add DT and ACPI compatible entries.

Signed-off-by: Marek Vasut 
Cc: Alessandro Zummo 
Cc: Alexandre Belloni 
To: linux-rtc@vger.kernel.org
Signed-off-by: Alexandre Belloni 
Link: https://lore.kernel.org/r/20210210220623.23233-1-marex@denx.de

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: pcf8563: Use BIT

2019-12-23T10:23:53+00:00

Replace (1 << ...) with BIT().

CC: Alessandro Zummo 
CC: Alexandre Belloni 
Signed-off-by: Nobuhiro Iwamatsu 
Link: https://lore.kernel.org/r/20191218082553.3309554-1-iwamatsu@nigauri.org
Signed-off-by: Alexandre Belloni

rtc: pcf8563: return meaningful value for RTC_VL_READ

2019-12-18T09:37:32+00:00

PCF8563_SC_LV means the voltage dropped too low and data has been lost.

Link: https://lore.kernel.org/r/20191214220259.621996-10-alexandre.belloni@bootlin.com
Signed-off-by: Alexandre Belloni

rtc: pcf8563: stop caching voltage_low

2019-12-18T09:37:30+00:00

voltage_low is only updated when reading the time, this means that using
RTC_VL_READ will miss the VL flag if the time has not been read before
using the ioctl. Always read the status from the hardware.

Link: https://lore.kernel.org/r/20191214220259.621996-9-alexandre.belloni@bootlin.com
Signed-off-by: Alexandre Belloni

rtc: pcf8563: remove conditional compilation

2019-12-18T09:37:28+00:00

Always compile pcf8563_rtc_ioctl as we are sure that CONFIG_RTC_INTF_DEV is
selected on actual kernel configurations.

Link: https://lore.kernel.org/r/20191214220259.621996-8-alexandre.belloni@bootlin.com
Signed-off-by: Alexandre Belloni

rtc: pcf8563: remove RTC_VL_CLR handling

2019-12-18T09:37:27+00:00

Remove RTC_VL_CLR handling because it is a disservice to userspace as it
removes the important information that the RTC data is invalid. This may
lead userspace to set an invalid system time later on.

Link: https://lore.kernel.org/r/20191214220259.621996-7-alexandre.belloni@bootlin.com
Signed-off-by: Alexandre Belloni

rtc: pcf8563: Constify clkout_rates

2019-11-15T10:58:16+00:00

The lates of clockout should be marked const. Make that so.

Signed-off-by: Nobuhiro Iwamatsu 
Link: https://lore.kernel.org/r/20191108002449.15097-1-iwamatsu@nigauri.org
Signed-off-by: Alexandre Belloni

rtc: pcf8563: let the core handle range offsetting

2019-09-01T08:57:47+00:00

Set the RTC range properly and use the core windowing and offsetting to
(unfortunately) map back to a 1970-2069 range.

Link: https://lore.kernel.org/r/20190829212547.19185-5-alexandre.belloni@bootlin.com
Signed-off-by: Alexandre Belloni