/openbmc/entity-manager/ |
H A D | README.md | 1 # Entity Manager 3 Entity manager is a design for managing physical system components, and mapping 10 ### Entity subsection 14 likely does contain multiple sub-components, but the component itself as a whole 15 is referred to as an entity. 20 entity encompasses. 24 A particular feature of an Entity. An Entity generally will have multiple 30 A set of rules for detecting a given entity. Said rules generally take the form 31 of a D-Bus interface definition. 35 Entity manager has the following goals (unless you can think of better ones): [all …]
|
/openbmc/entity-manager/schemas/ |
H A D | README.md | 1 # Entity manager configuration file schema 3 Entity manager configuration files are JSON documents and can be validated with 5 of an entity manager configuration file. 7 An entity manager configuration file consists of one or more entity manager 8 configurations. This provides flexibility for system designers - the 14 entity manager configuration file and schema file names must be 17 ## A single entity manager configuration 19 At its core entity manager simply exports objects onto DBus when a specific 20 event occurs. As such, an entity manager configuration provides a syntax for 37 interfaces listed in openbmc-dbus.json will be added on [all …]
|
H A D | global.json | 2 "$schema": "http://json-schema.org/draft-07/schema#", 5 "title": "Entity Manager Configuration", 6 …"description": "The schema for an entity manager configuration. An entity manager configuration de… 28 …"description": "The schema for an entity manager probe statement. Probes can be a single string or… 55 "$ref": "openbmc-dbus.json#/$defs/xyz/openbmc_project/Common/UUID" 58 "$ref": "openbmc-dbus.json#/$defs/xyz/openbmc_project/Inventory/Decorator/Asset" 61 … "$ref": "openbmc-dbus.json#/$defs/xyz/openbmc_project/Inventory/Decorator/AssetTag" 64 "$ref": "openbmc-dbus.json#/$defs/xyz/openbmc_project/Inventory/Decorator/Cable" 67 … "$ref": "openbmc-dbus.json#/$defs/xyz/openbmc_project/Inventory/Decorator/Compatible" 70 … "$ref": "openbmc-dbus.json#/$defs/xyz/openbmc_project/Inventory/Decorator/ManagedHost" [all …]
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Configuration/ |
H A D | README.md | 4 [entity-manager][entity-manager]. Entity-manager currently creates these style 10 It is hoped that in the future entity-manager will be refactored to closer align 13 [entity-manager]: https://github.com/openbmc/entity-manager
|
/openbmc/docs/designs/inventory/ |
H A D | gpio-based-hardware-inventory.md | 11 …om/openbmc/docs/blob/46902afd6ebd20d1148379df99fe2c0c591f56ba/designs/gpio-based-cable-presence.md) 26 and focuses on IPMI use-case. 28 …om/openbmc/docs/blob/879601d92becfa1dbc082f487abfb5e0151a5091/designs/gpio-based-cable-presence.md) 31 phosphor-multi-gpio-presence and phosphor-inventory-manager. 34 by phosphor-inventory-manager. 39 Additional item-specific properties are statically declared in the 40 phosphor-inventory-manager configuration. 44 …277cdb37e8062ae298402e9685882acb/meta-ibm/meta-sbp1/recipes-phosphor/gpio/phosphor-gpio-monitor/ph… 46 …-inventory-manager config](https://github.com/openbmc/openbmc/blob/1d438f68277cdb37e8062ae298402e9… 49 phosphor-multi-gpio-presence configuration: [all …]
|
/openbmc/docs/designs/ |
H A D | entity-manager-hw-id-vpd-discover-via-device-tree.md | 1 # Entity-Manager HW ID: VPD Discovery via Device-Tree Properties 12 data via non-I2C channels and in a proprietary format that is not covered by 13 Entity-Manager's 'fru-device' daemon that most platforms rely on. 16 gathered from device tree file paths for Entity-Manager consumption. 20 Typical platforms provide HW ID data - often referred to as 'vital product data' 21 (VPD) - for the baseboard as a FRU storage blob held in a physical EEPROM. 23 [As described in Entity-Manager documentation](https://github.com/openbmc/entity-manager/blob/maste… 25 copied to D-Bus as properties of the `xyz.openbmc_project.FruDevice` interface 26 by Entity-Manager's fru-device daemon. The current FRU-device daemon is able to 27 decode IPMI-FRU storage formatted blobs, as well as the Tyan data format. [all …]
|
H A D | physical-topology.md | 27 Changes to phosphor-dbus-interfaces documenting new Associations have been 28 [proposed](https://gerrit.openbmc.org/c/openbmc/phosphor-dbus-interfaces/+/46806) 37 - Must represent one-to-many relationships from chassis inventory objects which: 38 - Connect to cables 39 - Contain other chassis and/or are contained by a chassis 40 - Contain storage drives 41 - Are cooled by fans 42 - Are powered by power supplies 43 - Contain processors such as CPUs 44 - Contain memory such as DIMMs [all …]
|
H A D | liquid-leak-detection.md | 19 In this document, a leak is considered to be an entity with digital (present or 20 not-present) value. Currently, openBMC has a framework for sensors, but it is 23 [phosphor-gpio-monitor](https://github.com/openbmc/phosphor-gpio-monitor) is too 28 1. Able to identify leak presence for GPIO-based detectors and generate 32 - For example, the physical location of detectors can be used to determine 38 4. Capable of generating a D-Bus interface that adheres to 46 The DBus Interface for leak detection will consist of following - 49 | :------------------------------------------- | :----------: | :----------------------------: | 54 [patch](https://gerrit.openbmc.org/c/openbmc/phosphor-dbus-interfaces/+/73151) 55 for related D-Bus changes. [all …]
|
H A D | redfish-spdm-attestation.md | 14 [TPM](https://trustedcomputinggroup.org/resource/trusted-platform-module-tpm-summary/) 18 generic implementation for the SPDM D-Bus Daemon. 27 [libspdm](https://github.com/DMTF/libspdm) provides an open-source 30 adds support for doing SPDM-based device attestation over Redfish API. 40 - New D-Bus interfaces for Redfish resources `ComponentIntegrity` and 42 - BMCWeb changes for supporting the above Redfish resources. 43 - Design for SPDM Attestation D-Bus Daemon, demonstrating how to fetch the 44 attestation results over D-Bus. 48 ### Attestation related D-Bus Interfaces 51 D-Bus: [all …]
|
/openbmc/entity-manager/docs/ |
H A D | entity_manager_dbus_api.md | 1 # Entity Manager DBus API 3 The Entity Manager is in charge of inventory management by scanning JSON files 5 the internal structure of the Entity Manager, please refer to the README of the 6 Entity Manager. This file documents a consumers usage of the entity manager, and 13 #### Entities: `/xyz/openbmc_project/Inventory/Item/{Entity Type}/{Entity Name}` 19 #### Devices: `/xyz/openbmc_project/Inventory/Item/{Entity Type}/{Entity Name}/{Configuration}` 21 Configurations are components that are exposed when an entity is added to the 36 [upstream types](https://github.com/openbmc/phosphor-dbus-interfaces/tree/master/yaml/xyz/openbmc_p… 38 - BMC 39 - Board [all …]
|
/openbmc/dbus-sensors/ |
H A D | README.md | 1 # dbus-sensors 3 dbus-sensors is a collection of sensor applications that provide the 5 from hwmon, d-bus, or direct driver access to provide readings. Some advance 6 non-sensor features such as fan presence, pwm control, and automatic cpu 11 - runtime re-configurable from d-bus (entity-manager or the like) 13 - isolated: each sensor type is isolated into its own daemon, so a bug in one 17 - async single-threaded: uses sdbusplus/asio bindings 19 - multiple data inputs: hwmon, d-bus, direct driver access 23 A typical dbus-sensors object support the following dbus interfaces: 38 [phosphor-dbus-interfaces](https://github.com/openbmc/phosphor-dbus-interfaces/tree/master/yaml/xyz… [all …]
|
/openbmc/openbmc/meta-amd/meta-ethanolx/recipes-phosphor/configuration/ |
H A D | entity-manager_%.bbappend | 2 SRC_URI:append = " file://ethanolx-baseboard.json \ 3 file://ethanolx-chassis.json" 6 rm -f ${D}${datadir}/entity-manager/configurations/*.json 7 install -d ${D}${datadir}/entity-manager/configurations 8 … install -m 0444 ${UNPACKDIR}/ethanolx-baseboard.json ${D}${datadir}/entity-manager/configurations 9 install -m 0444 ${UNPACKDIR}/ethanolx-chassis.json ${D}${datadir}/entity-manager/configurations
|
/openbmc/openbmc/meta-amd/meta-daytonax/recipes-phosphor/configuration/ |
H A D | entity-manager_%.bbappend | 2 SRC_URI:append = " file://daytonax-baseboard.json \ 3 file://daytonax-chassis.json \ 7 rm -f ${D}${datadir}/entity-manager/configurations/*.json 8 install -d ${D}${datadir}/entity-manager/configurations 9 … install -m 0444 ${UNPACKDIR}/daytonax-baseboard.json ${D}${datadir}/entity-manager/configurations 10 install -m 0444 ${UNPACKDIR}/daytonax-chassis.json ${D}${datadir}/entity-manager/configurations
|
/openbmc/phosphor-virtual-sensor/ |
H A D | README.md | 1 # phosphor-virtual-sensor 3 phosphor-virtual-sensor reads the configuration file 7 2. `/var/lib/phosphor-virtual-sensor` 8 3. `/usr/share/phosphor-virtual-sensor` 19 ## information to get a virtual sensor configuration from D-Bus 26 "Config": "D-Bus" 35 hardware configuration file in entity-manager. This method of adding a virtual 39 The virtual sensor configuration in entity manager follows a different format to 41 [entity-manager/schemas/VirtualSensor.json](https://github.com/openbmc/entity-manager/blob/master/s…
|
/openbmc/entity-manager/service_files/ |
H A D | xyz.openbmc_project.EntityManager.service | 2 Description=Entity Manager 5 ExecStartPre=/bin/mkdir -p /var/configuration 6 ExecStartPre=/bin/mkdir -p /tmp/overlays 7 ExecStart=/usr/libexec/entity-manager/entity-manager 13 WantedBy=multi-user.target 14 Alias=dbus-xyz.openbmc_project.EntityManager.service
|
/openbmc/phosphor-bmc-code-mgmt/tpm/ |
H A D | README.md | 8 ## Entity Manager Configuration Example 10 The snippet below demonstrates how to configure a TPM device in Entity Manager. 24 ## Entity Manager Interface 26 The D-Bus interface name for TPM configuration will be as follows:
|
/openbmc/openbmc/meta-asrock/conf/machine/include/ |
H A D | asrock.inc | 2 obmc-host-ipmi \ 5 VIRTUAL-RUNTIME_obmc-inventory-manager = "entity-manager" 6 PREFERRED_PROVIDER_virtual/obmc-inventory-data = "entity-manager" 8 VIRTUAL-RUNTIME_obmc-sensors-hwmon ?= "dbus-sensors" 10 VIRTUAL-RUNTIME_obmc-host-state-manager ?= "x86-power-control" 11 VIRTUAL-RUNTIME_obmc-chassis-state-manager ?= "x86-power-control" 13 PREFERRED_PROVIDER_virtual/obmc-chassis-mgmt = "packagegroup-asrock-apps" 14 PREFERRED_PROVIDER_virtual/obmc-fan-mgmt = "packagegroup-asrock-apps" 15 PREFERRED_PROVIDER_virtual/obmc-flash-mgmt = "packagegroup-asrock-apps" 16 PREFERRED_PROVIDER_virtual/obmc-system-mgmt = "packagegroup-asrock-apps" [all …]
|
/openbmc/phosphor-bmc-code-mgmt/eeprom-device/ |
H A D | README.md | 5 ## Entity Manager Configuration Example (Harma) 18 "Name": "rt-cpu0-p1-enable", 22 "Name": "smb-rt-rom-p1-select", 34 ## Entity Manager Interface 36 The EEPROM device configuration can be found at the following D-Bus path, 37 provided that the EEPROMDevice is a expose record in the Harma_MB Entity Manager 44 The D-Bus interface name for EEPROMDevice configuration will be as follows:
|
/openbmc/openbmc/meta-tyan/conf/machine/include/ |
H A D | tyan.inc | 2 obmc-bmc-state-mgmt \ 3 obmc-chassis-state-mgmt \ 4 obmc-host-ipmi \ 5 obmc-host-state-mgmt \ 6 obmc-phosphor-chassis-mgmt \ 7 obmc-phosphor-fan-mgmt \ 8 obmc-phosphor-flash-mgmt \ 11 VIRTUAL-RUNTIME_obmc-inventory-manager = "entity-manager" 12 PREFERRED_PROVIDER_virtual/obmc-inventory-data = "entity-manager" 14 VIRTUAL-RUNTIME_obmc-host-state-manager ?= "x86-power-control" [all …]
|
/openbmc/dbus-sensors/src/ |
H A D | EntityManagerInterface.hpp | 28 /** Get the inventory info from Entity Manager */ 29 auto handleInventoryGet() -> sdbusplus::async::task<>; 32 /** @brief Handle async inventory add from Entity Manager */ 33 auto handleInventoryAdded() -> sdbusplus::async::task<>; 35 /** @brief Handle async inventory remove from Entity Manager */ 36 auto handleInventoryRemoved() -> sdbusplus::async::task<>;
|
/openbmc/openbmc/meta-quanta/meta-s6q/conf/machine/ |
H A D | s6q.conf | 2 KERNEL_DEVICETREE = "aspeed/${KMACHINE}-bmc-quanta-${MACHINE}.dtb" 5 UBOOT_DEVICETREE = "ast2600a1-evb" 8 require conf/machine/include/obmc-bsp-common.inc 13 obmc-bmc-state-mgmt \ 14 obmc-chassis-state-mgmt \ 15 obmc-host-ipmi \ 16 obmc-host-state-mgmt \ 17 obmc-phosphor-chassis-mgmt \ 18 obmc-phosphor-fan-mgmt \ 19 obmc-phosphor-flash-mgmt \ [all …]
|
/openbmc/openbmc/meta-amd/conf/machine/include/ |
H A D | amd.inc | 2 obmc-bmc-state-mgmt \ 3 obmc-phosphor-fan-mgmt \ 4 obmc-phosphor-flash-mgmt \ 7 VIRTUAL-RUNTIME_obmc-sensors-hwmon ?= "dbus-sensors" 8 VIRTUAL-RUNTIME_obmc-inventory-manager = "entity-manager" 10 PREFERRED_PROVIDER_virtual/obmc-inventory-data = "entity-manager" 11 PREFERRED_PROVIDER_virtual/obmc-fan-mgmt = "packagegroup-amd-apps" 12 PREFERRED_PROVIDER_virtual/obmc-flash-mgmt = "packagegroup-amd-apps" 13 PREFERRED_PROVIDER_virtual/obmc-system-mgmt = "packagegroup-amd-apps"
|
/openbmc/pldm/oem/ibm/libpldmresponder/ |
H A D | collect_slot_vpd.cpp | 5 #include <phosphor-logging/lg2.hpp> 47 const pldm_entity entity = getEntityIDfromEffecterID(effecterId); in enableSlot() local 51 if (entity.entity_instance_num == value.entity_instance_num && in enableSlot() 52 entity.entity_type == value.entity_type && in enableSlot() 53 entity.entity_container_id == value.entity_container_id) in enableSlot() 55 this->currentOnGoingSlotEntity.entity_type = value.entity_type; in enableSlot() 56 this->currentOnGoingSlotEntity.entity_instance_num = in enableSlot() 58 this->currentOnGoingSlotEntity.entity_container_id = in enableSlot() 66 const pldm_entity& entity, in processSlotOperations() argument 89 createPresenceMatch(adapterObjPath, entity, stateFieldValue); in processSlotOperations() [all …]
|
/openbmc/phosphor-power/phosphor-power-supply/ |
H A D | chassis_manager.hpp | 8 #include <sdbusplus/server/manager.hpp> 19 // Validation timeout. Allow 30s to detect if new EM interfaces show up in D-Bus 28 * @detail This class interacts with D-Bus to detect chassis power supply, 29 * subscribe to Entity Manager interface changes. 44 * @details Sets up D-Bus interfaces, creates timer for power supply 45 * validation and monitoring, and subscribes to entity-manager interfaces. 47 * @param[in] bus - Reference to the system D-Bus object. 48 * @param[in] e - Reference to event loop. 59 return timer->get_event().loop(); in run() 64 * @brief The D-Bus object [all …]
|
/openbmc/openbmc/meta-bytedance/meta-g220a/conf/machine/ |
H A D | g220a.conf | 2 KERNEL_DEVICETREE = "aspeed/${KMACHINE}-bmc-bytedance-${MACHINE}.dtb" 4 UBOOT_MACHINE = "evb-ast2500_defconfig" 5 UBOOT_DEVICETREE = "ast2500-evb" 10 require conf/machine/include/obmc-bsp-common.inc 11 require conf/distro/include/phosphor-aspeednic-use-mac2.inc 14 obmc-bmc-state-mgmt \ 15 obmc-chassis-state-mgmt \ 16 obmc-host-ipmi \ 17 obmc-host-state-mgmt \ 18 obmc-phosphor-chassis-mgmt \ [all …]
|