/openbmc/entity-manager/configurations/meta/santabarbara/ |
H A D | santabarbara_cable.json | 3 "Exposes": [], array 22 "Exposes": [], array 41 "Exposes": [], array 60 "Exposes": [], array 79 "Exposes": [], array 98 "Exposes": [], array 117 "Exposes": [], array 136 "Exposes": [], array 155 "Exposes": [], array 174 "Exposes": [], array [all …]
|
/openbmc/entity-manager/schemas/ |
H A D | README.md | 45 ## Exposes section in Entity manager configuration file schema 47 The exposes property describes the configuration data at its most specific 48 level. The exposes property is an array of heterogeneous configuration data. 49 Each exposes element has its own schema which is outlined by the subschemas in 57 `<remaining properties defined by exposes subschema>` 59 ## Adding new exposes property subschema 61 New subschema for the exposes property must be added to the schema directory, 62 and then referenced from global.json at /definitions/EMExposesElement. Exposes
|
H A D | global.json | 13 "Exposes": { object 14 …"The schema for the exposes property. The exposes property must be an array where elements are of … 28 …value. When the match condition occurs, the information described by the Exposes property is expor… 112 "required": ["Exposes", "Name", "Probe", "Type"]
|
/openbmc/entity-manager/configurations/meta/ventura/ |
H A D | ventura_cable.json | 3 "Exposes": [], array 26 "Exposes": [], array 45 "Exposes": [], array 64 "Exposes": [], array 86 "Exposes": [], array 109 "Exposes": [], array 132 "Exposes": [], array 153 "Exposes": [], array 174 "Exposes": [], array 201 "Exposes" array 222 "Exposes": [], global() array 245 "Exposes": [], global() array 266 "Exposes": [], global() array 287 "Exposes": [], global() array 310 "Exposes": [], global() array 329 "Exposes": [], global() array [all...] |
H A D | ventura_valve.json | 3 "Exposes": [ array 31 "Exposes": [ array
|
/openbmc/entity-manager/configurations/meta/minerva/ |
H A D | minerva_cmm_misc_boards.json | 3 "Exposes": [], array 18 "Exposes": [], array 33 "Exposes": [], array 48 "Exposes": [], array 63 "Exposes": [], array
|
H A D | minerva_tahan_smb.json | 3 "Exposes": [ array 38 "Exposes": [ array
|
H A D | minerva_janga_smb.json | 3 "Exposes": [ array 38 "Exposes": [ array
|
/openbmc/entity-manager/configurations/ibm/ |
H A D | system1_psu.json | 3 "Exposes": [ array 36 "Exposes": [ array 69 "Exposes": [ array 102 "Exposes": [ array
|
H A D | genesis3_psu.json | 3 "Exposes": [ array 68 "Exposes": [ array 133 "Exposes": [ array 198 "Exposes": [ array
|
H A D | sbp1_rssd.json | 3 "Exposes": [ array 131 "Exposes": [ array 259 "Exposes": [ array 387 "Exposes": [ array 515 "Exposes": [ array 643 "Exposes": [ array 771 "Exposes": [ array 899 "Exposes": [ array 1027 "Exposes": [ array 1155 "Exposes": [ array [all …]
|
/openbmc/entity-manager/src/gpio-presence/ |
H A D | README.md | 13 Exposes: 59 Exposes: 80 This is what the gpio-presence daemon exposes on dbus when the hardware is
|
/openbmc/docs/designs/inventory/ |
H A D | gpio-based-hardware-inventory.md | 106 exposes record in the json configuration 176 - EM exposes configuration for 'gpio-presence-sensor' 183 - EM exposes the new configuration for the detected hardware 194 - EM exposes configuration for 'gpio-presence-sensor' 234 exposes configuration on dbus. 237 'gpio-presence-sensor' then exposes 266 Exposes record. It needs to then create the 312 Exposes: 358 Exposes: 401 means EM would lose any semantic knowledge of the entities it exposes and
|
/openbmc/entity-manager/scripts/ |
H A D | autojson.py | 112 item["Exposes"] = sorted(item["Exposes"], key=lambda k: k["Type"]) 114 j["Exposes"] = sorted(j["Exposes"], key=lambda k: k["Type"])
|
/openbmc/entity-manager/ |
H A D | README.md | 22 ### Exposes subsection 25 Exposes records for the various features that component supports. Some examples 71 Exposes records that specify the specific features that this Entity supports. 72 Once a component is detected, entity manager will publish these Exposes 78 applications that input the Exposes records for sensor devices, then connect
|
/openbmc/entity-manager/configurations/ |
H A D | f2u8x25_hsbp.json |
|
H A D | a2ul16riser.json |
|
H A D | ahw1um2riser.json |
|
H A D | 2ux8_riser.json |
|
H A D | 1ux16_riser.json |
|
H A D | sas_module.json |
|
/openbmc/entity-manager/configurations/meta/bletchley/ |
H A D | bletchley_frontpanel.json | 3 "Exposes": [ array 49 "Exposes": [ array
|
/openbmc/entity-manager/configurations/meta/clemente/ |
H A D | clemente_hdd_nvme.json | 3 "Exposes": [ array 65 "Exposes": [ array 127 "Exposes": [ array
|
/openbmc/docs/designs/ |
H A D | physical-topology.md | 77 For entity-manager, we add new `Exposes` stanzas for the upstream and downstream 83 New code in entity-manager matches these properties and exposes associations on 94 "Exposes": [ 110 "Exposes": [
|
/openbmc/phosphor-snmp/docs/ |
H A D | snmp-configuration.md | 27 The phosphor-snmp repository exposes the following lib and the D-Bus service 29 libsnmp: Exposes the API to send the SNMP trap phosphor-network-snmpconf: Used
|