Home
last modified time | relevance | path

Searched refs:Bus (Results 1 – 25 of 332) sorted by relevance

12345678910>>...14

/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/MCTP/
H A DREADME.md3 MCTP D-Bus interfaces are implemented by the MCTP control process daemon alias
7 `xyz.openbmc_project.MCTP.Endpoint` D-Bus interface to discover MCTP endpoints.
12 the removal of the MCTP endpoints and removes the D-Bus objects corresponding to
13 those endpoints. MCTP bridges are not modelled in the D-Bus.
15 ## D-Bus object modelling
17 The root D-Bus object path for the mctpd is `/xyz/openbmc_project/mctp`. There
18 will be a D-Bus object for every endpoint that is discovered by the mctpd. The
19 lifetime of the D-Bus object is the lifetime of the connected MCTP device.
21 The D-Bus object path for MCTP endpoints are named
25 The D-Bus object implements the `xyz.openbmc_project.MCTP.Endpoint` interface.
[all …]
/openbmc/ipmitool/contrib/
H A Doem_ibm_sel_map13 "0xE0","0x00","0x00","Chassis Number","Slot Number","Bus Number","Device ID (MSB)","Device ID (LSB)…
14 "0xE0","0x00","0x01","Chassis Number","Slot Number","Bus Number","Device ID (MSB)","Device ID (LSB)…
15 "0xE0","0x00","0x02","Chassis Number","Slot Number","Bus Number","Device ID (MSB)","Device ID (LSB)…
16 "0xE0","0x00","0x03","Chassis Number","Slot Number","Bus Number","Device ID (MSB)","Device ID (LSB)…
17 "0xE0","0x00","0x04","Chassis Number","Slot Number","Bus Number","Device ID (MSB)","Device ID (LSB)…
18 "0xE0","0x00","0x05","Chassis Number","Slot Number","Bus Number","Device ID (MSB)","Device ID (LSB)…
19 "0xE0","0x00","0x06","Chassis Number","Slot Number","Bus Number","Device ID (MSB)","Device ID (LSB)…
20 "0xE0","0x00","0x07","Chassis Number","Slot Number","Bus Number","Device ID (MSB)","Device ID (LSB)…
21 "0xE0","0x00","0x08","Chassis Number","Slot Number","Bus Number","Device ID (MSB)","Device ID (LSB)…
22 "0xE0","0x00","0x09","Chassis Number","Slot Number","Bus Number","Device ID (MSB)","Device ID (LSB)…
[all …]
/openbmc/qemu/docs/interop/
H A Ddbus-vmstate.rst2 D-Bus VMState
6 on a QEMU D-Bus bus. (refer to the :doc:`dbus` document for
7 some recommendations on D-Bus usage)
10 ``org.qemu.VMState1`` D-Bus name owners and query their ``Id``. It
18 1Mb. The state must be saved quickly (a fraction of a second). (D-Bus
33 Sphinx 4 is required to build D-Bus documentation.
H A Ddbus-display.rst1 D-Bus display
4 QEMU can export the VM display through D-Bus (when started with ``-display
8 Various specialized D-Bus interfaces are available on different object paths
26 Sphinx 4 is required to build D-Bus documentation.
/openbmc/phosphor-power/phosphor-regulators/docs/
H A Dsensor_monitoring.md12 The sensor values are stored on D-Bus on the BMC, making them available to
24 ## How sensors are stored on D-Bus
27 on D-Bus. On subsequent reads, the existing D-Bus sensor object is updated with
30 The D-Bus sensor object implements the following interfaces:
37 An existing D-Bus Sensor object is removed from D-Bus if no corresponding sensor
47 of the D-Bus sensor objects:
59 - The following changes will be made to all D-Bus sensor objects for this rail:
66 following changes will be made to the D-Bus sensor objects:
/openbmc/phosphor-debug-collector/
H A Dmeson.options15 description: 'The D-Bus busname to own',
22 description: 'The dump manager D-Bus root',
29 description: 'The BMC dump manager D-Bus object path',
43 description: 'The BMC dump entry D-Bus object path',
136 description: 'The fault log dump manager D-Bus object path',
143 description: 'The fault log dump entry D-Bus object path',
154 description: 'The system dump manager D-Bus object path',
161 description: 'The system dump entry D-Bus object path',
170 description: 'The resource dump manager D-Bus object path',
177 description: 'The resource dump entry D-Bus object path',
/openbmc/docs/designs/
H A Dredfish-pcie.md33 The proposed implementation will follow the standard D-Bus producer-consumer
35 from hardware. The consumer will retrieve and parse the D-Bus data to provide
38 The proposed D-Bus interface can be found here:
41 The proposed producer will be a new D-Bus daemon that will be responsible for
42 gathering and caching PCIe hardware data and maintaining the D-Bus interfaces
53 update its cache, and make the necessary changes to the D-Bus properties. This
58 PCIe resource data from the D-Bus properties and providing it to the user.
66 Possible performance impact on the hardware-scanning and D-Bus updates. The
69 D-Bus properties.
H A Dboot-progress.md12 phosphor D-Bus properties, IPMI sensors, PLDM sensors, and Redfish properties to
18 [phosphor-state-manager][1] implements D-Bus properties which track the state of
28 phosphor-state-manager implements some other D-Bus properties that represent the
34 These two D-Bus properties are very IPMI-centric. They were defined based on two
74 it also does not preclude them. The `BootProgress` D-Bus property is associated
80 - Enhance the existing [BootProgress][3] D-Bus property to cover all supported
82 - Create a new `BootProgressLastUpdate` D-Bus property that will hold the date
87 `BootProgress` property on D-Bus
89 `BootProgressLastUpdate` property on D-Bus when it sees `BootProgress`
92 appropriate mappings to the `BootProgress` and `BootProgressLastUpdate D-Bus
[all …]
H A Dredfish-spdm-attestation.md18 generic implementation for the SPDM D-Bus Daemon.
40 - New D-Bus interfaces for Redfish resources `ComponentIntegrity` and
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:
81 The proposed Phosphor D-Bus Interfaces is here:
84 ### TrustedComponent related D-Bus Interfaces
101 The proposed Phosphor D-Bus Interfaces for `TrustedComponent` is here:
104 ### SPDM Attestation D-Bus Daemon
[all …]
H A Dmulti-host-postcode.md22 D-Bus objects).
24 Diagram Legend: |Label|Signifies| |-----|---------| |`I:` |D-Bus interface|
25 |`S:` |D-Bus service name (well-known bus name)| |`R:` |Repository name| |`U:`
152 writes value to appropriate D-Bus object hosted by phosphor-host-postd.
155 - phosphor-post-code-manager receives new POST codes via D-Bus signal and stores
167 - Sets `Value` property on appropriate D-Bus `Raw` object hosted by
178 - Display the latest postcode of the selected host read through D-Bus on a
181 ### D-Bus interface
183 The following D-Bus names need to be created for the multi-host post-code.
197 - Create D-Bus service names for single-host and multi-host system accordingly.
[all …]
H A Dtelemetry.md30 relies on the [OpenBMC D-Bus sensors][2].
34 - [OpenBMC D-Bus sensors][2] support. This is also design limitation, since the
35 Telemetry service requires telemetry sources to be implemented as D-Bus
99 URIs for metric report creation. Those sensors are also used to get URI->D-Bus
102 D-Bus sensors and exposing them as D-Bus objects. Telemetry service supports
123 |User| |bmcweb| |Telemetry| | D-Bus |
136 | +--------------------> Invoke AddReport | Register for D-Bus | |
137 | | | method on D-Bus | sensors | |
145 | | code 201 with | Return created | |D-Bus object | |
146 | | Metric Report | Report D-Bus path <-+ | |
[all …]
/openbmc/phosphor-fan-presence/docs/control/
H A Dgroups.md4 to a group of D-Bus objects that all of the same D-Bus path and interface, and
5 are acted upon by actions and triggers in events.json. Only the D-Bus objects
25 An array of the D-Bus object paths that are in the group. Required.
33 If known, the D-Bus service name that provides these D-bus objects. All members
H A Dfans.md22 The D-Bus name of the fan FRU. Required.
34 The D-Bus interface to use for setting the fan target speed/PWM. Either
40 The D-Bus object path used for setting the fan target speed/PWM via
/openbmc/docs/architecture/
H A DLED-architecture.md8 ## D-Bus
41 All applicable Inventory D-Bus objects would have a forward association mapping
42 to LED Group D-Bus object, namely:
48 All applicable LED Group D-Bus objects would have an association mapping to
49 inventory D-Bus object, namely:
58 - Look for an association `identify_led_group` on the Inventory D-Bus object
59 - If found, read the `asserted` property from the D-Bus object that is pointed
65 - Look for an association `identify_led_group` on the Inventory D-Bus object
66 - If found, set the `asserted` property on the D-Bus object that is pointed to
72 used. All applicable Inventory D-Bus objects would have a forward association
[all …]
/openbmc/google-misc/subprojects/acpi-power-state-daemon/
H A Dacpi_power_state.cpp54 sdbusplus::bus_t& Bus; member
57 ACPIPowerStateInherit(bus, path), Bus(bus) in ACPIPowerState()
70 startSystemdUnit(Bus, hostS5Unit); in sysACPIStatus()
74 startSystemdUnit(Bus, hostS0Unit); in sysACPIStatus()
/openbmc/phosphor-certificate-manager/
H A DREADME.md55 ## D-Bus Interface
57 `phosphor-certificate-manager` is an implementation of the D-Bus interface
61 D-Bus service name is constructed by
62 "xyz.openbmc_project.Certs.Manager.{Type}.{Endpoint}" and D-Bus object path is
72 D-Bus service name is "xyz.openbmc_project.Certs.Manager.Server.Https" and D-Bus
80 `phosphor-certificate-manager` via D-Bus.
/openbmc/phosphor-host-ipmid/docs/
H A Dconfiguration.md33 ## IPMI D-Bus Sensor Filtering
38 D-Bus. The D-Bus method is the default mode used by Redfish. Redfish does not
43 specification. Enabling IPMI to use D-Bus may cause the number of sensors
49 sensors via D-Bus. When dynamic sensors are active all of the sensors placed on
50 D-Bus by a service are added to the IPMI sensor list. In the event that too many
51 sensors are exposed on D-Bus, the list can be filtered by adding a list of
/openbmc/phosphor-power/phosphor-regulators/docs/config_file/
H A Dpmbus_read_sensor.md53 ### D-Bus Sensor
56 [D-Bus sensor object](https://github.com/openbmc/docs/blob/master/architecture/sensor-architecture.…
60 D-Bus sensors have an object path with the following format:
66 The D-Bus sensors `<namespace>` is the general category of the sensor. The
67 following table shows how the sensor type is mapped to a D-Bus sensors
70 | Sensor Type | D-Bus `<namespace>` |
82 The D-Bus `<sensor_name>` must be unique across the entire system. It will be
90 the resulting D-Bus `<sensor_name>` will be "vdd0_vout_peak".
96 information, the D-Bus sensor will contain the highest peak/lowest valley value
98 off, the D-Bus peak/valley sensor values are cleared.
/openbmc/openpower-hw-diags/test/
H A Dtest-chnl-timeout.cpp67 "Bus Type": "OMI_BUS", in TEST()
68 "Callout Type": "Bus Callout", in TEST()
135 "Bus Type": "OMI_BUS", in TEST()
136 "Callout Type": "Bus Callout", in TEST()
204 "Bus Type": "OMI_BUS", in TEST()
205 "Callout Type": "Bus Callout", in TEST()
212 "Bus Type": "OMI_BUS", in TEST()
272 "Bus Type": "OMI_BUS", in TEST()
273 "Callout Type": "Bus Callout", in TEST()
280 "Bus Type": "OMI_BUS", in TEST()
/openbmc/phosphor-dbus-interfaces/yaml/com/ibm/ipzvpd/
H A DREADME.md1 # IPZ VPD D-Bus Interfaces
13 Power systems on D-Bus.
15 The D-Bus interfaces defined here describe how IPZ VPD will be made available on
16 D-Bus. Each YAML here represents a record in the IPZ VPD and keywords that
/openbmc/pldm/libpldmresponder/examples/fru/
H A DFRU_Master.json1 // This is the master config file for generating PLDM FRU records from the D-Bus
2 // inventory objects. "service" is the name of D-Bus service hosting the
3 // inventory D-Bus objects, "root_path" is the root path for all the inventory
4 // D-Bus objects and "entities" section specifies the type of FRU's for which
/openbmc/service-config-manager/
H A DREADME.md3 The service config manager provides a D-Bus interface to manage BMC services as
4 described by the [service management D-Bus interfaces][].
18 Implementation details are described in the [D-Bus interface README].
21 units via D-Bus interfaces.
/openbmc/docs/architecture/code-update/
H A Dcode-update-diagrams.md24 │ │Software D-Bus │
33 │ D-Bus Object │
62 …[Software D-Bus Object](https://github.com/openbmc/phosphor-dbus-interfaces/tree/master/yaml/xyz/o…
/openbmc/pldm/docs/
H A Dfw_update_configuration.md5 1. **D-Bus API**: Using the StartUpdate D-Bus interface for firmware updates
12 automatically. When disabled, only D-Bus API-based firmware updates will be
/openbmc/phosphor-bmc-code-mgmt/eeprom-device/
H A DREADME.md13 "Bus": 12,
36 The EEPROM device configuration can be found at the following D-Bus path,
44 The D-Bus interface name for EEPROMDevice configuration will be as follows:

12345678910>>...14