Lines Matching +full:in +full:- +full:functions
6 authors use these functions to communicate minimum latency or
13 - support the range of power management parameters present in the TI SRF;
15 - separate the drivers from the underlying PM parameter
19 - specify PM parameters in terms of fundamental units, such as
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
27 - can be implemented immediately with minimal disruption of other
32 five power management functions for driver code:
36 (*pdata->set_max_mpu_wakeup_lat)(struct device *dev, unsigned long t)
40 (*pdata->set_max_dev_wakeup_lat)(struct device *dev, unsigned long t)
44 (*pdata->set_max_sdma_lat)(struct device *dev, long t)
48 (*pdata->set_min_bus_tput)(struct device *dev, u8 agent_id, unsigned long r)
52 (*pdata->get_dev_context_loss_count)(struct device *dev)
55 Further documentation for all OMAP PM interface functions can be
56 found in arch/arm/plat-omap/include/mach/omap-pm.h.
60 ---------------------------------------------
63 the range of power management features present in OMAP3. As this
68 Driver usage of the OMAP PM functions
69 -------------------------------------
71 As the 'pdata' in the above examples indicates, these functions are
72 exposed to drivers through function pointers in driver .platform_data
73 structures. The function pointers are initialized by the `board-*.c`
74 files to point to the corresponding OMAP PM functions:
76 - set_max_dev_wakeup_lat will point to
78 not support these functions should leave these function pointers set
81 if (pdata->set_max_dev_wakeup_lat)
82 (*pdata->set_max_dev_wakeup_lat)(dev, t);
84 The most common usage of these functions will probably be to specify
93 if (pdata->set_max_mpu_wakeup_lat)
94 (*pdata->set_max_mpu_wakeup_lat)(dev, tc);
97 if (pdata->set_max_dev_wakeup_lat)
98 (*pdata->set_max_dev_wakeup_lat)(dev, td);
100 /* total wakeup latency in this example: (tc + td) */
104 function with a t argument of -1 (except in the case of
113 Other specialized interface functions
114 -------------------------------------
116 The five functions listed above are intended to be usable by any
118 DSPBridge expresses target DSP performance levels in terms of OPP IDs.
119 CPUFreq expresses target MPU performance levels in terms of MPU
120 frequency. The OMAP PM interface contains functions for these
125 6. `(*pdata->dsp_get_opp_table)(void)`
127 7. `(*pdata->dsp_set_min_opp)(u8 opp_id)`
129 8. `(*pdata->dsp_get_opp)(void)`
131 9. `(*pdata->cpu_get_freq_table)(void)`
133 10. `(*pdata->cpu_set_freq)(unsigned long f)`
135 11. `(*pdata->cpu_get_freq)(void)`
141 However, in special cases, the default OPP table may need to be
148 in these cases, the board file needs to do additional steps as follows:
150 arch/arm/mach-omapx/board-xyz.c::