The configuration object shall be loaded prior to calling any EEMI API, except the following APIs:
- Get API version
- Set configuration
- Get Chip ID
Until the first configuration object is loaded the PM controller is configured to initially expect the EEMI API calls from the APU or RPU master, via IPI_APU or IPI_RPU_0 IPI channels, respectively. In other words, the first configuration object has to be loaded by APU or RPU.
After the first configuration object is loaded, the next loading of the configuration object can be triggered by a privileged master. Privileged masters are defined in the configuration object that was loaded the last.
Following are the steps at boot level:
- FSBL sends the configuration object to PMU with the Set Configuration API
- PMU parses the configuration object and configures
- PMU powers off all the nodes which are unused after all the masters have completed the initialization
All other requests prior to the first Set Configuration API call will be rejected by PMU firmware.