platform-specific PM customization


One Line Summary

Currently, platform-specific code has a need to customize common PM methods, typically on the platform_bus. This track is to discuss the various approaches to solving this problem.


The platform_bus currently has a weak-symbol method for overriding various methods of its struct dev_pm_ops. This is used by platforms that want to customize/extend the default PM methods and add platform-specific behavior.

Doing this has led to several discussions on the “right” way to approach this. Various topics below have been discussed on mailing lists and would be good to discuss further:

- customizing existing bus (platform_bus)
- creating a new platform-specific bus
- how to extend platform_device (pdev_archdata, devres, device parents, etc.)

Currently the need for this has been demonstrated on SH, sh-mobile, OMAP and msm. Would be great to have folks from each camp there.


PM, platform_bus, devres, bus type


  • Biography

    Kevin has been a Linux user since 1994, and a kernel hacker since 1999 when he started writing drivers and working on kernel ports to new embedded platforms. He has been a driver/kernel developer for Equator Technologies, Texas Instruments, MontaVista and now runs a small consulting company offering services in upstream kernel development, and specializing in power management.

    He is also the maintainer of the kernel for the TI DaVinci SoCs and is active developer in the TI OMAP kernel community where he is a maintainer of the OMAP PM core code.

Leave a private comment to organizers about this proposal