Linux Kernel
3.7.1
|
#include <omap_opp_data.h>
Data Fields | |
char * | hwmod_name |
unsigned long | freq |
unsigned long | u_volt |
bool | default_available |
struct omap_opp_def - OMAP OPP Definition : Name of the hwmod for this domain : Frequency in hertz corresponding to this OPP : Nominal voltage in microvolts corresponding to this OPP : True/false - is this OPP available by default
OMAP SOCs have a standard set of tuples consisting of frequency and voltage pairs that the device will support per voltage domain. This is called Operating Points or OPP. The actual definitions of OMAP Operating Points varies over silicon within the same family of devices. For a specific domain, you can have a set of {frequency, voltage} pairs and this is denoted by an array of omap_opp_def. As the kernel boots and more information is available, a set of these are activated based on the precise nature of device the kernel boots up on. It is interesting to remember that each IP which belongs to a voltage domain may define their own set of OPPs on top of this - but this is handled by the appropriate driver.
Definition at line 50 of file omap_opp_data.h.
bool default_available |
Definition at line 56 of file omap_opp_data.h.
unsigned long freq |
Definition at line 53 of file omap_opp_data.h.
char* hwmod_name |
Definition at line 51 of file omap_opp_data.h.
unsigned long u_volt |
Definition at line 54 of file omap_opp_data.h.