metaonly module ti.bios.power.OMAP2530GPP

GPP configuration module for the OMAP2530 device

Configuration parameters for the Local Power Manager running on the GPP core of an OMAP2530 device.
XDCspec summary sourced in ti/bios/power/OMAP2530GPP.xdc
metaonly module OMAP2530GPP {  ...
XDCscript usage meta-domain
XDCspec declarations sourced in ti/bios/power/OMAP2530GPP.xdc
 
enum OMAP2530GPP.OpersysCfg

Runtime Operating System

XDCscript usage meta-domain
values of type OMAP2530GPP.OpersysCfg
    const OMAP2530GPP.Opersys_PrOS_DaVinci;
    // PrOS on DaVinci platform
    const OMAP2530GPP.Opersys_Linux;
    // Linux (HLOS)
    const OMAP2530GPP.Opersys_DSPBIOS;
    // DSP/BIOS
 
 
enum OMAP2530GPP.TransportCfg

Transport Layer used between GPP and DSP

XDCscript usage meta-domain
values of type OMAP2530GPP.TransportCfg
    const OMAP2530GPP.Transport_Link_PrOS_DaVinci;
    // DSP/BIOS Link for PrOS on DaVinci
    const OMAP2530GPP.Transport_Link_Linux;
    // DSP/BIOS Link for Linux
 
 
config OMAP2530GPP.CPU_NAME  // module-wide

cpu name, useful for adding validation checks

XDCscript usage meta-domain
const OMAP2530GPP.CPU_NAME = String "GPP";
 
 
config OMAP2530GPP.opersys  // module-wide

Define which operating system is running on the CPU (required)

XDCscript usage meta-domain
OMAP2530GPP.opersys = ITMS320CDM644x.OpersysCfg undefined;
 
 
config OMAP2530GPP.proxyFor  // module-wide

Proxy device used for new devices

XDCscript usage meta-domain
OMAP2530GPP.proxyFor = String undefined;
 
DETAILS
To support new devices which behave the same as existing devices, set this configuration parameter to a known device which can be used as a proxy for the new device.
 
config OMAP2530GPP.transport  // module-wide

Define which transport layer is used (required)

XDCscript usage meta-domain
OMAP2530GPP.transport = ITMS320CDM644x.TransportCfg undefined;
 
generated on Mon, 20 Sep 2010 23:50:09 GMT