/openbmc/pldm/pldmd/ |
H A D | dbus_impl_requester.hpp | 5 #include "xyz/openbmc_project/PLDM/Requester/server.hpp" 18 sdbusplus::xyz::openbmc_project::PLDM::server::Requester>; 20 /** @class Requester 21 * @brief OpenBMC PLDM.Requester implementation. 23 * xyz.openbmc_project.PLDM.Requester DBus APIs. 25 class Requester : public RequesterIntf class 28 Requester() = delete; 29 Requester(const Requester&) = delete; 30 Requester& operator=(const Requester&) = delete; 31 Requester(Requester&&) = delete; [all …]
|
H A D | oem_ibm.hpp | 14 #include "requester/request.hpp" 66 pldm::requester::Handler<pldm::requester::Request>* reqHandler) : in OemIBM() 194 /** @brief pointer to the requester class*/ 195 requester::Handler<requester::Request>* reqHandler;
|
H A D | pldmd.cpp | 10 #include "requester/handler.hpp" 11 #include "requester/mctp_endpoint_discovery.hpp" 12 #include "requester/request.hpp" 105 requester::Handler<requester::Request>& handler, in processRxMsg() 193 // Setup PLDM requester transport in main() 207 dbus_api::Requester dbusImplReq(bus, "/xyz/openbmc_project/pldm", in main() 213 requester::Handler<requester::Request> reqHandler(&pldmTransport, event, in main()
|
/openbmc/pldm/oem/ibm/requester/ |
H A D | dbus_to_file_handler.hpp | 4 #include "requester/handler.hpp" 14 namespace requester namespace 23 * as a pldm requester in oem-ibm path. 44 pldm::requester::Handler<pldm::requester::Request>* handler); 93 pldm::requester::Handler<pldm::requester::Request>* handler; 97 } // namespace requester
|
/openbmc/pldm/host-bmc/ |
H A D | dbus_to_event_handler.hpp | 5 #include "requester/handler.hpp" 42 * @param[in] requester - reference to Requester object 47 pldm::requester::Handler<pldm::requester::Request>* handler); 100 pldm::requester::Handler<pldm::requester::Request>* handler;
|
/openbmc/docs/designs/ |
H A D | pldm-stack.md | 93 - The BMC should be able to act as a PLDM responder as well as a PLDM requester. 94 As a PLDM requester, the BMC can monitor/control other devices. As a PLDM 98 - As a PLDM requester, the BMC must be able to discover other PLDM enabled 101 - As a PLDM requester, the BMC must be able to send simultaneous messages to 104 - As a PLDM requester, the BMC must be able to handle out of order responses. 122 The design aims at having a single PLDM daemon serve both the requester and 126 The design enables concurrency aspects of the requester and responder functions, 186 #### Requester subsubsection 188 Designing the BMC as a PLDM requester is interesting. We haven't had this with 189 IPMI, because the BMC was typically an IPMI server. PLDM requester functions [all …]
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/PLDM/ |
H A D | Requester.interface.yaml | 3 API would be used by PLDM requester apps on the BMC. 6 xyz.openbmc_project.PLDM.Requester on /xyz/openbmc_project/pldm. 16 messages when a PLDM requester sends out multiple request messages, 19 https://github.com/openbmc/docs/blob/master/designs/pldm-stack.md#Requester. 22 EID that a PLDM requester is communicating with. An implementation of
|
/openbmc/pldm/oem/ibm/host-bmc/ |
H A D | host_lamp_test.hpp | 5 #include "requester/handler.hpp" 57 pldm::requester::Handler<pldm::requester::Request>* handler) : in HostLampTest() 107 pldm::requester::Handler<pldm::requester::Request>* handler;
|
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
H A D | ComponentIntegrity.v1_3_0.json | 156 …egrityType` contains `SPDM`, a value of `false` shall prohibit the SPDM Requester from using SPDM … 213 … "description": "Integrity information about the SPDM Responder as reported by an SPDM Requester.", 214 … identified by the `TargetComponentURI` property as reported by an SPDM Requester. This property … 372 …Requester shall issue one or more SPDM 'GET_MEASUREMENTS' requests for each of the requested measu… 384 …SPDM Requester shall generate the nonce. The value should be unique and generated using a random … 390 …provided by the client, the value shall be assumed to be `0`. The SPDM Requester shall send this … 448 …roperty shall contain the hashing algorithm negotiated between the SPDM Requester and the SPDM Res… 459 …idate the signature. This property shall only be present when the SPDM Requester was pre-provisio… 465 …Requester and the SPDM Responder. If SPDM version is 1.0 or 1.1, this value shall be a concatenat… 471 …ll contain the asymmetric signing algorithm negotiated between the SPDM Requester and the SPDM Res… [all …]
|
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
H A D | ComponentIntegrity.v1_3_0.json | 156 …egrityType` contains `SPDM`, a value of `false` shall prohibit the SPDM Requester from using SPDM … 213 … "description": "Integrity information about the SPDM Responder as reported by an SPDM Requester.", 214 … identified by the `TargetComponentURI` property as reported by an SPDM Requester. This property … 372 …Requester shall issue one or more SPDM 'GET_MEASUREMENTS' requests for each of the requested measu… 384 …SPDM Requester shall generate the nonce. The value should be unique and generated using a random … 390 …provided by the client, the value shall be assumed to be `0`. The SPDM Requester shall send this … 448 …roperty shall contain the hashing algorithm negotiated between the SPDM Requester and the SPDM Res… 459 …idate the signature. This property shall only be present when the SPDM Requester was pre-provisio… 465 …Requester and the SPDM Responder. If SPDM version is 1.0 or 1.1, this value shall be a concatenat… 471 …ll contain the asymmetric signing algorithm negotiated between the SPDM Requester and the SPDM Res… [all …]
|
/openbmc/pldm/fw-update/ |
H A D | inventory_manager.hpp | 5 #include "requester/handler.hpp" 41 pldm::requester::Handler<pldm::requester::Request>& handler, in InventoryManager() 91 pldm::requester::Handler<pldm::requester::Request>& handler;
|
H A D | update_manager.hpp | 8 #include "requester/handler.hpp" 46 pldm::requester::Handler<pldm::requester::Request>& handler, in UpdateManager() 94 pldm::requester::Handler<pldm::requester::Request>& handler;
|
H A D | manager.hpp | 8 #include "requester/handler.hpp" 9 #include "requester/mctp_endpoint_discovery.hpp" 41 requester::Handler<requester::Request>& handler, in Manager()
|
/openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/PLDM/ |
H A D | meson.build | 5 subdir('Requester') subdir 56 '../../../../yaml/xyz/openbmc_project/PLDM/Requester.interface.yaml', 58 output: ['Requester.md'], 70 'xyz/openbmc_project/PLDM/Requester',
|
/openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
H A D | ComponentIntegrity_v1.xml | 65 …Requester shall issue one or more SPDM 'GET_MEASUREMENTS' requests for each of the requested measu… 69 …SPDM Requester shall generate the nonce. The value should be unique and generated using a random … 74 …provided by the client, the value shall be assumed to be `0`. The SPDM Requester shall send this … 144 …egrityType` contains `SPDM`, a value of `false` shall prohibit the SPDM Requester from using SPDM … 163 …iption" String="Integrity information about the SPDM Responder as reported by an SPDM Requester."/> 164 … identified by the `TargetComponentURI` property as reported by an SPDM Requester. This property … 239 …ription" String="Integrity information about an SPDM Responder as reported by an SPDM Requester."/> 240 …ct shall contain integrity information about an SPDM Responder as reported by an SPDM Requester."/> 241 <NavigationProperty Name="Requester" Type="Resource.Item" Nullable="false"> 252 …Description" String="Identity authentication information about the SPDM Requester and SPDM Respond… [all …]
|
/openbmc/bmcweb/redfish-core/schema/dmtf/installed/ |
H A D | ComponentIntegrity_v1.xml | 65 …Requester shall issue one or more SPDM 'GET_MEASUREMENTS' requests for each of the requested measu… 69 …SPDM Requester shall generate the nonce. The value should be unique and generated using a random … 74 …provided by the client, the value shall be assumed to be `0`. The SPDM Requester shall send this … 144 …egrityType` contains `SPDM`, a value of `false` shall prohibit the SPDM Requester from using SPDM … 163 …iption" String="Integrity information about the SPDM Responder as reported by an SPDM Requester."/> 164 … identified by the `TargetComponentURI` property as reported by an SPDM Requester. This property … 239 …ription" String="Integrity information about an SPDM Responder as reported by an SPDM Requester."/> 240 …ct shall contain integrity information about an SPDM Responder as reported by an SPDM Requester."/> 241 <NavigationProperty Name="Requester" Type="Resource.Item" Nullable="false"> 252 …Description" String="Identity authentication information about the SPDM Requester and SPDM Respond… [all …]
|
/openbmc/pldm/requester/test/ |
H A D | mock_request.hpp | 4 #include "requester/request.hpp" 14 namespace requester namespace 30 } // namespace requester
|
/openbmc/pldm/oem/ampere/ |
H A D | oem_ampere.hpp | 10 #include "../../requester/request.hpp" 59 pldm::requester::Handler<pldm::requester::Request>* reqHandler) : in OemAMPERE() 162 /** @brief pointer to the requester class*/ 163 requester::Handler<requester::Request>* reqHandler = nullptr;
|
/openbmc/pldm/oem/ibm/libpldmresponder/ |
H A D | platform_oem_ibm.hpp | 4 #include "requester/handler.hpp" 30 pldm::requester::Handler<pldm::requester::Request>* handler);
|
H A D | file_io.hpp | 4 #include "oem/ibm/requester/dbus_to_file_handler.hpp" 7 #include "requester/handler.hpp" 171 pldm::requester::Handler<pldm::requester::Request>* handler) : in Handler() 269 std::make_unique<pldm::requester::oem_ibm:: in Handler() 307 pldm::requester::oem_ibm:: in Handler() 423 std::unique_ptr<pldm::requester::oem_ibm::DbusToFileHandler> 432 std::vector<std::unique_ptr<pldm::requester::oem_ibm::DbusToFileHandler>>
|
/openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/PLDM/Requester/ |
H A D | meson.build | 3 sdbusplus_current_path = 'xyz/openbmc_project/PLDM/Requester' 8 '../../../../../yaml/xyz/openbmc_project/PLDM/Requester.interface.yaml', 28 'xyz/openbmc_project/PLDM/Requester',
|
/openbmc/linux/Documentation/devicetree/bindings/pci/ |
H A D | pci-iommu.txt | 4 Each PCI(e) device under a root complex is uniquely identified by its Requester 5 ID (AKA RID). A Requester ID is a triplet of a Bus number, Device number, and 17 Requester ID. While a given PCI device can only master through one IOMMU, a 35 - iommu-map: Maps a Requester ID to an IOMMU and associated IOMMU specifier 44 - iommu-map-mask: A mask to be applied to each Requester ID prior to being
|
H A D | pci-msi.txt | 4 Each PCI device under a root complex is uniquely identified by its Requester ID 5 (AKA RID). A Requester ID is a triplet of a Bus number, Device number, and 18 Requester ID. A mechanism is required to associate a device with both the MSI 32 - msi-map: Maps a Requester ID to an MSI controller and associated 49 - msi-map-mask: A mask to be applied to each Requester ID prior to being mapped
|
/openbmc/pldm/requester/ |
H A D | README.md | 3 PLDM requester infrastructure enables the requester code in PLDM daemon to meet 20 The requester code needs to use the `registerRequest` API to register the PLDM
|
/openbmc/ipmbbridge/ |
H A D | ipmbdefines.hpp | 40 uint8_t rqSA; /// @brief requester's target address, LS bit=0 41 uint8_t rqSeqLUN; /// @brief requester's sequence number and logical 51 uint8_t rqNetFnLUN; /// @brief requester's net function and logical
|