diff options
103 files changed, 7778 insertions, 720 deletions
diff --git a/Documentation/arm/OMAP/omap_pm b/Documentation/arm/OMAP/omap_pm new file mode 100644 index 000000000000..5389440aade3 --- /dev/null +++ b/Documentation/arm/OMAP/omap_pm | |||
| @@ -0,0 +1,129 @@ | |||
| 1 | |||
| 2 | The OMAP PM interface | ||
| 3 | ===================== | ||
| 4 | |||
| 5 | This document describes the temporary OMAP PM interface. Driver | ||
| 6 | authors use these functions to communicate minimum latency or | ||
| 7 | throughput constraints to the kernel power management code. | ||
| 8 | Over time, the intention is to merge features from the OMAP PM | ||
| 9 | interface into the Linux PM QoS code. | ||
| 10 | |||
| 11 | Drivers need to express PM parameters which: | ||
| 12 | |||
| 13 | - support the range of power management parameters present in the TI SRF; | ||
| 14 | |||
| 15 | - separate the drivers from the underlying PM parameter | ||
| 16 | implementation, whether it is the TI SRF or Linux PM QoS or Linux | ||
| 17 | latency framework or something else; | ||
| 18 | |||
| 19 | - specify PM parameters in terms of fundamental units, such as | ||
| 20 | latency and throughput, rather than units which are specific to OMAP | ||
| 21 | or to particular OMAP variants; | ||
| 22 | |||
| 23 | - allow drivers which are shared with other architectures (e.g., | ||
| 24 | DaVinci) to add these constraints in a way which won't affect non-OMAP | ||
| 25 | systems, | ||
| 26 | |||
| 27 | - can be implemented immediately with minimal disruption of other | ||
| 28 | architectures. | ||
| 29 | |||
| 30 | |||
| 31 | This document proposes the OMAP PM interface, including the following | ||
| 32 | five power management functions for driver code: | ||
