Skip to content

RFC Introduce init() and exit() for platform_device

Paulius Zaleckas lkml 1 version In review

Get series with b4
b4 am 20090224155721.28880.31830.stgit@Programuotojas

Versions newest first

  1. v1 RFC Latest3 patches 5 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3platform_device: add init() exit() callbacksDocumentation/driver-model/platform.txt drivers/base/platform.c include/linux/platform_device.h+27 -41 reply
2/3mxc: move serial driver init()/exit() to platform_devicearch/arm/mach-mx1/devices.c arch/arm/mach-mx1/mx1ads.c arch/arm/mach-mx2/mx27ads.c +2 more+170 -2404 replies
3/3imx-uart: remove unused init()/exit() from platform_dataarch/arm/mach-imx/include/mach/imx-uart.h arch/arm/plat-mxc/include/mach/imx-uart.h drivers/serial/imx.c+0 -160 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [RFC PATCH 0/3] Introduce init() and exit() for platform_device

For changes and documentation about this fix please see:
[RFC PATCH 1/3] platform_device: add init() exit() callbacks

Other patches demonstrate how drivers can benefit from this change.

I have two questions:
1. Is init()/exit() OK? Or should I call it activate()/deactivate()? Other suggestions?
2. Now exit() returns nothing. Maybe it is better if it returned int? How to handle such exit failure?