diff options
author | 2020-11-09 17:34:08 +0100 | |
---|---|---|
committer | 2020-11-19 12:50:12 +0100 | |
commit | fdcfd854333be5b30377dc5daa9cd0fa1643a979 (patch) | |
tree | 89b755560a425f0eb332a86037e2b6d429b7fb5a /arch/alpha | |
parent | rtc: nvmem: emit an error message when nvmem registration fails (diff) | |
download | linux-fdcfd854333be5b30377dc5daa9cd0fa1643a979.tar.gz linux-fdcfd854333be5b30377dc5daa9cd0fa1643a979.tar.bz2 linux-fdcfd854333be5b30377dc5daa9cd0fa1643a979.zip |
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
Diffstat (limited to 'arch/alpha')
-rw-r--r-- | arch/alpha/kernel/rtc.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/alpha/kernel/rtc.c b/arch/alpha/kernel/rtc.c index 1b1d5963ac55..ce3077946e1d 100644 --- a/arch/alpha/kernel/rtc.c +++ b/arch/alpha/kernel/rtc.c @@ -216,6 +216,6 @@ alpha_rtc_init(void) rtc->ops = &remote_rtc_ops; #endif - return rtc_register_device(rtc); + return devm_rtc_register_device(rtc); } device_initcall(alpha_rtc_init); |