Intel OpenBMC Linux kernel source tree (mirror) https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=v4.18 2018-05-19T08:50:03+00:00 2018-05-19T08:50:03+00:00 Alexandre Belloni alexandre.belloni@bootlin.com 2018-05-19T08:50:03+00:00 urn:sha1:7e83f03fad3e404778fbcfb16f91a09aecf27e04 Use the 64-bit version of rtc_time_to_tm in mxc_rtc_read_alarm Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> 2018-05-19T08:47:46+00:00 Alexandre Belloni alexandre.belloni@bootlin.com 2018-05-19T08:04:46+00:00 urn:sha1:95fbfa14b431d4d7213b8e0e167563f7a11dd5e7 This RTC is a 32-bit second counter. This also solves an issue where mxc_rtc_set_alarm() can return with the lock taken. Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> 2018-05-19T08:47:46+00:00 Alexandre Belloni alexandre.belloni@bootlin.com 2018-05-19T08:01:42+00:00 urn:sha1:5490a1e018a4b447c1fdb49ec274a620e60a4d42 The IRQ is requested before the struct rtc is allocated and registered, but this struct is used in the IRQ handler. This may lead to a NULL pointer dereference. Switch to devm_rtc_allocate_device/rtc_register_device to allocate the rtc before requesting the IRQ. Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> 2018-03-01T09:49:36+00:00 Fabio Estevam fabio.estevam@nxp.com 2018-02-12T02:38:46+00:00 urn:sha1:588519ff16552c5a6f6a189767692db6689cadad Fix the iomem pointer notation in order to fix the following sparse warnings: drivers/rtc/rtc-mxc_v2.c:280:18: warning: incorrect type in argument 1 (different address spaces) drivers/rtc/rtc-mxc_v2.c:280:18: expected void const volatile [noderef] <asn:2>*addr drivers/rtc/rtc-mxc_v2.c:280:18: got void *[noderef] <asn:2>ioaddr drivers/rtc/rtc-mxc_v2.c:329:44: warning: incorrect type in argument 1 (different address spaces) drivers/rtc/rtc-mxc_v2.c:329:44: expected void *[noderef] <asn:2>ioaddr drivers/rtc/rtc-mxc_v2.c:329:44: got void [noderef] <asn:2>* drivers/rtc/rtc-mxc_v2.c:339:44: warning: incorrect type in argument 1 (different address spaces) drivers/rtc/rtc-mxc_v2.c:339:44: expected void *[noderef] <asn:2>ioaddr drivers/rtc/rtc-mxc_v2.c:339:44: got void [noderef] <asn:2>* Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> 2018-01-11T23:20:40+00:00 Arnd Bergmann arnd@arndb.de 2018-01-02T09:43:33+00:00 urn:sha1:db00d38e7b59ae913cfa10f1c40bf656a969fb82 The mxc_rtc_remove is incorrectly annotated as __exit: `mxc_rtc_remove' referenced in section `.data' of drivers/rtc/rtc-mxc_v2.o: defined in discarded section `.exit.text' of drivers/rtc/rtc-mxc_v2.o This should not be done, as devices can be dynamically bound and unbound to a driver. Fixes: 54c47014b474 ("rtc: add mxc driver for i.MX53 SRTC") Signed-off-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com> 2018-01-11T23:20:40+00:00 Fabio Estevam fabio.estevam@nxp.com 2017-12-21T11:43:24+00:00 urn:sha1:a9c705a8bd52d8a5205cc779d6e64af4321a9fa8 devm_ioremap_resource() already checks if the resource is NULL, so remove the unnecessary platform_get_resource() error check. Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com> 2018-01-11T23:20:39+00:00 Patrick Bruenn p.bruenn@beckhoff.com 2017-12-18T11:51:32+00:00 urn:sha1:83c880f79e88cc60593f627e612326f5d43db81e Neither rtc-imxdi, rtc-mxc nor rtc-snvs are compatible with i.MX53. This is driver enables support for the low power domain SRTC features: - 32-bit MSB of non-rollover time counter - 32-bit alarm register Select the new config option RTC_DRV_MXC_V2 to build this driver Based on: http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/tree/drivers/rtc/rtc-mxc_v2.c?h=imx_2.6.35_11.09.01 Signed-off-by: Patrick Bruenn <p.bruenn@beckhoff.com> Acked-by: Philippe Ombredanne <pombredanne@nexb.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>