2
0
mirror of https://github.com/edk2-porting/linux-next.git synced 2024-12-27 22:53:55 +08:00
linux-next/Documentation/driver-api/driver-model
Bartosz Golaszewski fdcfd85433 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
2020-11-19 12:50:12 +01:00
..
binding.rst
bus.rst
class.rst
design-patterns.rst
device.rst docs: filesystems: fix renamed references 2020-04-20 15:45:22 -06:00
devres.rst rtc: rework rtc_register_device() resource management 2020-11-19 12:50:12 +01:00
driver.rst docs: driver-model: remove a duplicated markup at driver.rst 2020-06-26 10:01:24 -06:00
index.rst
overview.rst docs: filesystems: fix renamed references 2020-04-20 15:45:22 -06:00
platform.rst Documentation/driver-api: driver-model/platform: drop doubled word 2020-07-10 14:35:37 +02:00
porting.rst