| John Wang | af0bc6e | 2018-11-29 11:22:01 +0800 | [diff] [blame^] | 1 | ## System states |
| 2 | ## state can change to next state in 2 ways: |
| 3 | ## - a process emits a GotoSystemState signal with state name to goto |
| 4 | ## - objects specified in EXIT_STATE_DEPEND have started |
| 5 | SYSTEM_STATES = [ |
| 6 | 'BASE_APPS', |
| 7 | 'BMC_STARTING', |
| 8 | 'BMC_READY', |
| 9 | 'HOST_POWERING_ON', |
| 10 | 'HOST_POWERED_ON', |
| 11 | 'HOST_BOOTING', |
| 12 | 'HOST_BOOTED', |
| 13 | 'HOST_POWERED_OFF', |
| 14 | ] |
| 15 | |
| 16 | EXIT_STATE_DEPEND = { |
| 17 | 'BASE_APPS' : { |
| 18 | '/xyz/openbmc_poroject/sensors': 0, |
| 19 | }, |
| 20 | 'BMC_STARTING' : { |
| 21 | '/xyz/openbmc_project/control/chassis0': 0, |
| 22 | }, |
| 23 | } |
| 24 | |
| 25 | FRU_INSTANCES = {} |
| 26 | |
| 27 | # I believe these numbers need to match the yaml file used to create the c++ ipmi map. |
| 28 | # the devices have types, but I don't believe that factors in here, I think these are |
| 29 | # just unique IDs. |
| 30 | ID_LOOKUP = { |
| 31 | 'FRU' : {}, |
| 32 | # The number at the end needs to match the FRU ID. |
| 33 | # https://github.com/openbmc/skeleton/blob/master/pysystemmgr/system_manager.py#L143 |
| 34 | # The parameter for it is of type 'y' (unsigned 8-bit integer) presumably decimal? |
| 35 | 'FRU_STR' : {}, |
| 36 | 'SENSOR' : {}, |
| 37 | 'GPIO_PRESENT' : {} |
| 38 | } |
| 39 | |
| 40 | GPIO_CONFIG = {} |
| 41 | HWMON_CONFIG = {} |
| 42 | GPIO_CONFIGS = {} |
| 43 | |
| 44 | # Miscellaneous non-poll sensor with system specific properties. |
| 45 | # The sensor id is the same as those defined in ID_LOOKUP['SENSOR']. |
| 46 | MISC_SENSORS = {} |
| 47 | |
| 48 | # vim: tabstop=8 expandtab shiftwidth=4 softtabstop=4 |