Searched refs:effecters (Results 1 – 6 of 6) sorted by relevance
38 auto effecters = e.value("effecters", emptyList); in generateStateEffecterPDR() local39 for (const auto& effecter : effecters) in generateStateEffecterPDR()110 pdr->composite_effecter_count = effecters.size(); in generateStateEffecterPDR()116 for (const auto& effecter : effecters) in generateStateEffecterPDR()
237 for (auto effecters = 0x00; effecters < compositeEffecterCount; in getEntityIDfromEffecterID() local238 effecters++) in getEntityIDfromEffecterID()
50 for (auto effecters = 0x00; effecters < compositeEffecterCount; in findStateEffecterPDR() local51 effecters++) in findStateEffecterPDR()484 for (auto effecters = 0x00; effecters < compositeEffecterCount; in findStateEffecterId() local485 effecters++) in findStateEffecterId()
93 auto effecters = entry.value("effecters", emptyList); in parseEffecterJson() local97 for (const auto& effecter : effecters) in parseEffecterJson()144 for (const auto& effecter : effecters) in parseEffecterJson()
4 fetches only one PDR at a time. With a lot of sensors/effecters & with a lot of
57 - PLDM introduces the concept of effecters - a control mechanism. Both sensors58 and effecters are associated to entities (similar to IPMI, entities can be60 effecters are a mechanism for control. Effecters can be numeric or state438 Because the `$TerminusName` will be included in the Terminus' sensors, effecters441 support sensors, effecters or status. When the EM EID configuration is not477 - The `pldmd` then creates the Terminus inventory, sensors, effecters D-Bus