rtc: rework rtc_register_device() resource management
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 <bgolaszewski@baylibre.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Link: https://lore.kernel.org/r/20201109163409.24301-8-brgl@bgdev.pl
This commit is contained in:
committed by
Alexandre Belloni
parent
6746bc095b
commit
fdcfd85433
@ -694,7 +694,7 @@ static int ds1305_probe(struct spi_device *spi)
|
||||
ds1305->rtc->range_max = RTC_TIMESTAMP_END_2099;
|
||||
|
||||
ds1305_nvmem_cfg.priv = ds1305;
|
||||
status = rtc_register_device(ds1305->rtc);
|
||||
status = devm_rtc_register_device(ds1305->rtc);
|
||||
if (status)
|
||||
return status;
|
||||
|
||||
|
Reference in New Issue
Block a user