summaryrefslogtreecommitdiffstats
path: root/drivers/rtc/rtc-max77686.c
diff options
context:
space:
mode:
authorBiwen Li <biwen.li@nxp.com>2019-08-29 04:14:18 +0200
committerAlexandre Belloni <alexandre.belloni@bootlin.com>2019-09-01 08:48:28 +0200
commit7ef66122bdb3b839e9f51b76d7e600b6e21ef648 (patch)
treeb45f2b2cd51840d0c4b3fa0504849a9cade156b0 /drivers/rtc/rtc-max77686.c
parentrtc: snvs: switch to rtc_time64_to_tm/rtc_tm_to_time64 (diff)
downloadlinux-7ef66122bdb3b839e9f51b76d7e600b6e21ef648.tar.xz
linux-7ef66122bdb3b839e9f51b76d7e600b6e21ef648.zip
rtc: pcf85363/pcf85263: fix regmap error in set_time
Issue: - # hwclock -w hwclock: RTC_SET_TIME: Invalid argument Why: - Relative commit: 8b9f9d4dc511 ("regmap: verify if register is writeable before writing operations"), this patch will always check for unwritable registers, it will compare reg with max_register in regmap_writeable. - The pcf85363/pcf85263 has the capability of address wrapping which means if you access an address outside the allowed range (0x00-0x2f) hardware actually wraps the access to a lower address. The rtc-pcf85363 driver will use this feature to configure the time and execute 2 actions in the same i2c write operation (stopping the clock and configure the time). However the driver has also configured the `regmap maxregister` protection mechanism that will block accessing addresses outside valid range (0x00-0x2f). How: - Split of writing regs to two parts, first part writes control registers about stop_enable and resets, second part writes RTC time and date registers. Signed-off-by: Biwen Li <biwen.li@nxp.com> Link: https://lore.kernel.org/r/20190829021418.4607-1-biwen.li@nxp.com Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Diffstat (limited to 'drivers/rtc/rtc-max77686.c')
0 files changed, 0 insertions, 0 deletions