linux-toradex.git/drivers/rtc, branch v6.0-rc1

rtc: spear: set range max

2022-08-08T22:56:41+00:00

In the commit f395e1d3b28d7c2c67b73bd467c4fb79523e1c65
("rtc: spear: set range"), the value of
RTC_TIMESTAMP_END_9999 was incorrectly set to range_min.
390	config->rtc->range_min = RTC_TIMESTAMP_BEGIN_0000;
391	config->rtc->range_max = RTC_TIMESTAMP_END_9999;

Fixes: f395e1d3b28d ("rtc: spear: set range")
Signed-off-by: Zeng Jingxiang 
Acked-by: Viresh Kumar 
Signed-off-by: Alexandre Belloni 
Link: https://lore.kernel.org/r/20220728100101.1906801-1-zengjx95@gmail.com

rtc: rtc-cmos: Do not check ACPI_FADT_LOW_POWER_S0

2022-08-08T18:36:01+00:00

The ACPI_FADT_LOW_POWER_S0 flag merely means that it is better to
use low-power S0 idle on the given platform than S3 (provided that
the latter is supported) and it doesn't preclude using either of
them (which of them will be used depends on the choices made by user
space).

For this reason, there is no benefit from checking that flag in
use_acpi_alarm_quirks().

First off, it cannot be a bug to do S3 with use_acpi_alarm set,
because S3 can be used on systems with ACPI_FADT_LOW_POWER_S0 and it
must work if really supported, so the ACPI_FADT_LOW_POWER_S0 check is
not needed to protect the S3-capable systems from failing.

Second, suspend-to-idle can be carried out on a system with
ACPI_FADT_LOW_POWER_S0 unset and it is expected to work, so if setting
use_acpi_alarm is needed to handle that case correctly, it should be
set regardless of the ACPI_FADT_LOW_POWER_S0 value.

Accordingly, drop the ACPI_FADT_LOW_POWER_S0 check from
use_acpi_alarm_quirks().

Signed-off-by: Rafael J. Wysocki 
Reviewed-by: Mario Limonciello 
Signed-off-by: Alexandre Belloni 
Link: https://lore.kernel.org/r/12054246.O9o76ZdvQC@kreacher

rtc: zynqmp: initialize fract_tick

2022-08-08T18:35:41+00:00

fract_tick is used uninitialized when fract_offset is 0

Reported-by: kernel test robot 
Signed-off-by: Alexandre Belloni 
Reviewed-by: Nathan Chancellor 
Reviewed-by: Michal Simek 
Link: https://lore.kernel.org/r/20220727100018.3301470-1-alexandre.belloni@bootlin.com

rtc: Add NCT3018Y real time clock driver

2022-07-26T15:07:04+00:00

Add real time clock support for NCT3018Y.

Signed-off-by: Mia Lin 
Signed-off-by: Alexandre Belloni 
Link: https://lore.kernel.org/r/20220713090647.8028-4-mimi05633@gmail.com

rtc: rx8025: fix 12/24 hour mode detection on RX-8035

2022-07-26T14:49:45+00:00

The 12/24hr flag in the RX-8035 can be found in the hour register,
instead of the CTRL1 on the RX-8025. This was overlooked when
support for the RX-8035 was added, and was causing read errors when
the hour register 'overflowed'.

To deal with the relevant register not always being visible in
the relevant functions, determine the 12/24 mode at startup and
store it in the driver state.

Signed-off-by: Mathew McBride 
Fixes: f120e2e33ac8 ("rtc: rx8025: implement RX-8035 support")
Cc: stable@vger.kernel.org
Signed-off-by: Alexandre Belloni 
Link: https://lore.kernel.org/r/20220706074236.24011-1-matt@traverse.com.au

rtc: cros-ec: Only warn once in .remove() about notifier_chain problems

2022-07-26T14:43:46+00:00

When a remove platform device callback returns an error code, the driver
core emits an error message ("remove callback returned a non-zero value.
This will be ignored.\n") and still removes the device. As the driver
already emits a more specific error message, return 0 to suppress the
core's error message.

This is a preparation for making platform remove callbacks return void.

Signed-off-by: Uwe Kleine-König 
Acked-by: Tzung-Bi Shih 
Signed-off-by: Alexandre Belloni 
Link: https://lore.kernel.org/r/20220707153156.214841-1-u.kleine-koenig@pengutronix.de

rtc: vr41xx: remove driver

2022-07-26T14:34:12+00:00

Commit d3164e2f3b0a ("MIPS: Remove VR41xx support") removed support
for MIPS VR41xx platform, so remove exclusive drivers for this
platform, too.

Signed-off-by: Thomas Bogendoerfer 
Signed-off-by: Alexandre Belloni 
Link: https://lore.kernel.org/r/20220715135330.134684-1-tsbogend@alpha.franken.de

rtc: mpfs: remove 'pending' variable from mpfs_rtc_wakeup_irq_handler()

2022-07-26T14:31:15+00:00

cppcheck reports
[drivers/rtc/rtc-mpfs.c:219]: (style) Variable 'pending' is assigned a value that is never used.

The fetched CONTROL_REG stored in pending is unused and partially
duplicates the functionality of the later call to mpfs_rtc_clear().  This looks
like leftover development code, so remove pending.

Fixes: 0b31d703598d ("rtc: Add driver for Microchip PolarFire SoC")
Signed-off-by: Tom Rix 
Reviewed-by: Conor Dooley 
Signed-off-by: Alexandre Belloni 
Link: https://lore.kernel.org/r/20220627205943.2075043-1-trix@redhat.com

rtc: rv8803: fix missing unlock on error in rv8803_set_time()

2022-07-26T09:29:05+00:00

Add the missing unlock before return from function rv8803_set_time()
in the error handling case.

Fixes: f8176e0bb83f ("rtc: rv8803: initialize registers on post-probe voltage loss")
Reported-by: Hulk Robot 
Signed-off-by: Yang Yingliang 
Reviewed-by: Sascha Hauer 
Signed-off-by: Alexandre Belloni 
Link: https://lore.kernel.org/r/20220627080822.3881072-1-yangyingliang@huawei.com

rtc: zynqmp: Add calibration set and get support

2022-07-26T09:21:50+00:00

Zynqmp RTC controller has a calibration feature to compensate
time deviation due to input clock inaccuracy.
Set and get calibration API's are used for setting and getting
calibration value from the controller calibration register.

Signed-off-by: Srinivas Neeli 
Signed-off-by: Alexandre Belloni 
Link: https://lore.kernel.org/r/20220626070817.3780977-3-srinivas.neeli@xilinx.com