| /openbmc/openbmc-test-automation/redfish/systems/eventlog/ |
| H A D | test_event_association.robot | 55 Create Test Error Callout And Verify Associations
56 [Documentation] Create test error callout and verify Associations.
60 # "Associations": [
71 List Should Contain Value ${resp.json()["data"]["Associations"][0]} callout
72 List Should Contain Value ${resp.json()["data"]["Associations"][0]} fault
74 ... ${resp.json()["data"]["Associations"][0]}
94 # "Associations": [
131 # "Associations": [
155 # "Associations": [
203 Should Contain ${resp.json()["data"]["Associations"][0]} callout
[all …]
|
| H A D | test_esel.robot | 67 # "Associations": [
|
| /openbmc/docs/designs/ |
| H A D | physical-topology.md | 21 specifies using Associations for all relationships (Proposal II) rather than
27 Changes to phosphor-dbus-interfaces documenting new Associations have been
73 Associations, so no changes are needed here.
126 choose to include the same Associations that phosphor-inventory-manager and
169 Associations are the only approach that fits all use cases, so we should start
174 dedicated tool to query for Associations of a specific type and present a
|
| H A D | guard-on-bmc.md | 113 - Associations:
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Association/ |
| H A D | Definitions.interface.yaml | 6 - name: Associations
|
| /openbmc/pldm/oem/ibm/libpldmresponder/ |
| H A D | utils.cpp | 209 const EntityAssociations& Associations, const EntityMaps entityMaps) in setCoreCount() argument
213 for (const auto& entries : Associations) in setCoreCount()
|
| /openbmc/docs/architecture/ |
| H A D | object-mapper.md | 10 - [Associations](#associations) - Associates two different objects with each
335 ## Associations section in The ObjectMapper
337 Associations are special D-Bus objects created by the mapper to associate two
340 association is desired, the `Associations` property on that interface needs to
343 This `Associations` property is an array of tuples of the form:
384 `org.openbmc.Associations`. While the mapper still supports this interface as
|
| /openbmc/phosphor-psu-code-mgmt/ |
| H A D | README.md | 81 "Associations": [
96 "Associations": [
116 "Associations": [
|
| /openbmc/entity-manager/docs/ |
| H A D | associations.md | 1 # Associations chapter
|
| H A D | my_first_sensors.md | 243 org.openbmc.Associations interface - - -
|
| /openbmc/openbmc-tools/expectedJsonChecker/ |
| H A D | README.md | 287 "Associations": [
299 "Associations": [
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | logging_utils.robot | 135 # "Associations": []
209 # "Associations": []
|
| /openbmc/docs/architecture/code-update/ |
| H A D | host-code-update.md | 130 ### Associations, MANIFEST File, Deleting an Image, Software Field Mode, and Software Factory Reset
|
| H A D | code-update.md | 178 ### Associations subsection in # ls -l /tmp/images/
|
| /openbmc/phosphor-dbus-interfaces/ |
| H A D | requirements.md | 51 ## Associations section in Requirements and Expectations for dbus interfaces
|
| /openbmc/phosphor-pid-control/dbus/ |
| H A D | dbusconfiguration.cpp | 55 using Associations = std::vector<Association>; typedef
170 std::unordered_map<std::string, std::variant<Associations, bool>>> in eventHandler()
|
| /openbmc/phosphor-inventory-manager/ |
| H A D | README.md | 133 ## Creating Associations
|
| /openbmc/entity-manager/ |
| H A D | README.md | 88 ### Associations subsection
|
| /openbmc/phosphor-webui/app/common/services/ |
| H A D | api-utils.js | 866 content.data[key].Associations.forEach(function(
1522 delete content.data[key].Associations;
|
| /openbmc/docs/ |
| H A D | host-management.md | 132 - `Associations`: A URI to the failing inventory part.
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/intel/ |
| H A D | ixgbe.rst | 524 Associations with "ip xfrm ..." the 'offload' tag option can be used to
|