Re: [RFC/PATCH 00/13] OMAP2+: PM: isolate PM code in modules

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* jean.pihet@xxxxxxxxxxxxxx <jean.pihet@xxxxxxxxxxxxxx> [110518 10:28]:
> From: Jean Pihet <j-pihet@xxxxxx>
> 
> First attempt at isolation of the OMAP2+ PM code
> 
> RFC quality code but successfully tested on board as a proof
> of concept
> 
> 1) provide PM functionality as modules
> 
> To allow for the PM functionality to be built and used as modules a
> clean-up and isolation task first has been performed ('spaghetti
> unwinding') because there are a lot of cross calls between various parts
> of the PM code (core, platform specific, cpuidle ...).

Glad to see this happening! :)
 
> 2) Addition of EXPORT_SYMBOL for functions and variables used by
> the code in PM modules. Lots of (too many?) symbols need to exported
> to the PM modules.

Ideally these would all be Linux generic of course..

Anyways, please also consider what all modules could be moved to
live under drivers/pm or similar. I'd assume a lot of this can
be done in a generic way.

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux