linux.git/drivers/rtc, branch v5.16

Merge tag 'rtc-5.16' of git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux

2021-11-12T19:44:31+00:00

Pull RTC updates from Alexandre Belloni:
 "This includes new ioctls to get and set parameters and in particular
  the backup switch mode that is needed for some RTCs to actually enable
  the backup voltage (and have a useful RTC).

  The same interface can also be used to get the actual features
  supported by the RTC so userspace has a better way than trying and
  failing.

  Summary:

  Subsystem:
   - Add new ioctl to get and set extra RTC parameters, this includes
     backup switch mode
   - Expose available features to userspace, in particular, when alarmas
     have a resolution of one minute instead of a second.
   - Let the core handle those alarms with a minute resolution

  New driver:
   - MSTAR MSC313 RTC

  Drivers:
   - Add SPI ID table where necessary
   - Add BSM support for rv3028, rv3032 and pcf8523
   - s3c: set RTC range
   - rx8025: set range, implement .set_offset and .read_offset"

* tag 'rtc-5.16' of git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux: (50 commits)
  rtc: rx8025: use .set_offset/.read_offset
  rtc: rx8025: use rtc_add_group
  rtc: rx8025: clear RTC_FEATURE_ALARM when alarm are not supported
  rtc: rx8025: set range
  rtc: rx8025: let the core handle the alarm resolution
  rtc: rx8025: switch to devm_rtc_allocate_device
  rtc: ab8500: let the core handle the alarm resolution
  rtc: ab-eoz9: support UIE when available
  rtc: ab-eoz9: use RTC_FEATURE_UPDATE_INTERRUPT
  rtc: rv3032: let the core handle the alarm resolution
  rtc: s35390a: let the core handle the alarm resolution
  rtc: handle alarms with a minute resolution
  rtc: pcf85063: silence cppcheck warning
  rtc: rv8803: fix writing back ctrl in flag register
  rtc: s3c: Add time range
  rtc: s3c: Extract read/write IO into separate functions
  rtc: s3c: Remove usage of devm_rtc_device_register()
  rtc: tps80031: Remove driver
  rtc: sun6i: Allow probing without an early clock provider
  rtc: pcf8523: add BSM support
  ...

rtc: rx8025: use .set_offset/.read_offset

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

The driver has its own sysfs file to adjust the clock. Fortunately, it is
already in pbb, however, the sign it expects is the opposite of what the
RTC core does (which actually aligns with the RTC).

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

rtc: rx8025: use rtc_add_group

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

Remove open coded sysfs registration by using rtc_add_group.

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

rtc: rx8025: clear RTC_FEATURE_ALARM when alarm are not supported

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

Clear RTC_FEATURE_ALARM to signal alarms are not supported to the core
instead of checking client->irq.

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

rtc: rx8025: set range

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

Set the RTC range, it is a classic BCD RTC, with 00 being a leap
year. Let the core handle range checking.

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

rtc: rx8025: 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.

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

rtc: rx8025: switch to devm_rtc_allocate_device

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

Switch to devm_rtc_allocate_device/devm_rtc_register_device, this allows
for further improvement of the driver.

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

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: ab-eoz9: support UIE when available

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

The RTC actually supports UIE when an interrupt is available.

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

rtc: ab-eoz9: use RTC_FEATURE_UPDATE_INTERRUPT

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

Switch from uie_unsupported to RTC_FEATURE_UPDATE_INTERRUPT

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