Searched refs:PDR (Results 1 – 14 of 14) sorted by relevance
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/PLDM/ |
H A D | PDR.interface.yaml | 8 An implementation of this interface should maintain the primary PDR 11 A OpenBMC implementation should implement the xyz.openbmc_project.PLDM.PDR 14 More information about PDR can be found at DSP0248 version 1.2.0 section 25. 19 Obtain the state effecter PDR, for the input TID, entity ID and state 22 effecter PDRs are returned. More than one PDR can be returned for the 25 When the PDR for the given input TID, entity id and state set id is 59 Array of State Effecter PDRs, where a PDR is an array[byte]. 70 Obtain the state sensor PDR, for the input TID, entity ID and state 73 PDRs are returned. More than one PDR can be returned for the same 76 When the PDR for the given input TID, entity id and state set id is [all …]
|
/openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/PLDM/ |
H A D | meson.build | 17 subdir('PDR') subdir 20 input: [ '../../../../yaml/xyz/openbmc_project/PLDM/PDR.interface.yaml', ], 21 output: [ 'PDR.md' ], 28 'xyz/openbmc_project/PLDM/PDR',
|
/openbmc/linux/drivers/gpio/ |
H A D | gpio-mb86s7x.c | 30 #define PDR(x) (0x0 + x / 8 * 4) macro 101 val = readl(gchip->base + PDR(gpio)); in mb86s70_gpio_direction_output() 106 writel(val, gchip->base + PDR(gpio)); in mb86s70_gpio_direction_output() 121 return !!(readl(gchip->base + PDR(gpio)) & OFFSET(gpio)); in mb86s70_gpio_get() 132 val = readl(gchip->base + PDR(gpio)); in mb86s70_gpio_set() 137 writel(val, gchip->base + PDR(gpio)); in mb86s70_gpio_set()
|
/openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/PLDM/PDR/ |
H A D | meson.build | 4 input: [ '../../../../../yaml/xyz/openbmc_project/PLDM/PDR.interface.yaml', ], 12 'xyz/openbmc_project/PLDM/PDR',
|
/openbmc/pldm/ |
H A D | README.md | 179 ###### PDR Implementation 183 PDR information is encoded in platform specific JSON files. JSON files must be 184 named based on the PDR type number. For example a state effecter PDR JSON file 186 additional processing (apart from PDR creation) for specific PDR types, for eg 189 The PLDM responder implementation finds and parses PDR JSON files to create the 190 PDR repository. Platform specific PDR modifications would likely just result in 191 JSON updates. New PDR type support would require JSON updates as well as PDR 192 generation code. The PDR generator is a map of PDR Type -> C++ lambda to create 193 PDR entries for that type based on the JSON, and to update the central PDR repo.
|
/openbmc/pldm/tools/visualize-pdr/ |
H A D | README.md | 4 fetches only one PDR at a time. With a lot of sensors/effecters & with a lot of 9 `pldm_visualise_pdrs.py` is a python script that can be used to fetch the PDR's 10 from the BMC and can parse them to display a full view of available PDR's on
|
/openbmc/pldm/libpldmresponder/examples/fru/ |
H A D | FRU_Master.json | 5 // FRU records are created in the FRU table. FRU Record Set PDR and Entity 6 // Association PDR are generated for matching FRU. In this example, PLDM FRU
|
/openbmc/openbmc-test-automation/pldm/ |
H A D | test_pldm_platform.robot | 87 ... Log To Console "Found PDR Type - PLDM_ENTITY_ASSOCIATION_PDR" 99 ... Log To Console "Found PDR Type - PLDM_COMPACT_NUMERIC_SENSOR_PDR' 101 ... ELSE Fail msg="Unknown PDR Type is received"
|
/openbmc/pldm/pldmd/ |
H A D | dbus_impl_pdr.hpp | 19 sdbusplus::xyz::openbmc_project::PLDM::server::PDR>;
|
/openbmc/pldm/libpldmresponder/examples/effecter/ |
H A D | dbus_to_host_effecter.json | 8 // will be fetched from the PDR
|
/openbmc/libpldm/ |
H A D | CHANGELOG.md | 73 10. platform: Add 3 PDR type enum for Redfish Device Enablement per 105 4. pdr: Remove redundant constant for minimum numeric sensor PDR length 210 2. platform: Struct field name in fru_record_set PDR 214 3. platform: Struct field name in numeric sensor value PDR
|
/openbmc/docs/designs/ |
H A D | pldm-stack.md | 83 structures, sensor PDR structures, etc) are implemented by this lib. 380 PLDM entity info extracted from the FRU record set PDR under an
|
/openbmc/ |
H A D | opengrok1.0.log | 11090 …grok/data/xref/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/PLDM/PDR.interface.yaml.gz 11617 …opengrok/data/xref/openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/PLDM/PDR/meson.build.gz 11618 …event delete: /opengrok/data/xref/openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/PLDM/PDR 27588 …grok/data/xref/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/PLDM/PDR.interface.yaml.gz 28115 …opengrok/data/xref/openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/PLDM/PDR/meson.build.gz 28116 …event delete: /opengrok/data/xref/openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/PLDM/PDR
|
H A D | opengrok2.0.log | 11090 …grok/data/xref/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/PLDM/PDR.interface.yaml.gz 11617 …opengrok/data/xref/openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/PLDM/PDR/meson.build.gz 11618 …event delete: /opengrok/data/xref/openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/PLDM/PDR 27580 …grok/data/xref/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/PLDM/PDR.interface.yaml.gz 28107 …opengrok/data/xref/openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/PLDM/PDR/meson.build.gz 28108 …event delete: /opengrok/data/xref/openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/PLDM/PDR
|