| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/Power/ |
| H A D | Throttle.interface.yaml | 11 This property shall contain the cause(s) of the component being
13 being throttled.
29 The cause of the component being throttled is a clock limit.
32 The cause of the component being throttled is a fault detected
36 The cause of the component being throttled is a power limit.
39 The cause of the component being throttled is a thermal limit.
42 The cause of the component being throttled is not known.
|
| /openbmc/qemu/tests/qtest/libqos/ |
| H A D | virtio-9p-client.h | 88 /* 9P client being used (mandatory) */
90 /* user supplied tag number being returned with response (optional) */
94 /* file ID for target directory being walked to (optional) */
101 /* data being received from 9p server as 'Rwalk' response (optional) */
122 /* 9P client being used (mandatory) */
124 /* user supplied tag number being returned with response (optional) */
144 /* 9P client being used (mandatory) */
146 /* user supplied tag number being returned with response (optional) */
150 /* numerical uid of user being introduced to server (optional) */
152 /* data being received from 9p server as 'Rattach' response (optional) */
[all …]
|
| /openbmc/qemu/include/hw/nvram/ |
| H A D | fw_cfg.h | 102 * @s: fw_cfg device being modified
115 * @s: fw_cfg device being modified
127 * @s: fw_cfg device being modified
133 * including its NUL terminator. The data being replaced, assumed to have
141 * @s: fw_cfg device being modified
153 * @s: fw_cfg device being modified
159 * value, converted to little-endian representation. The data being replaced,
167 * @s: fw_cfg device being modified
179 * @s: fw_cfg device being modified
185 * value, converted to little-endian representation. The data being replaced,
[all …]
|
| /openbmc/phosphor-fan-presence/monitor/example/ |
| H A D | config.json | 8 "seconds before being marked nonfunctional in inventory. The first",
14 "target for 5 seconds before being updated to functional again.",
15 "Each sensor has an error logged after 0 seconds being marked",
50 "nonfunctional and only returns to being functional when the counter",
55 "Each sensor has an error logged after 0 seconds being marked",
95 "being marked nonfunctional in inventory. Instead of using the default",
104 "Each sensor has an error logged after 0 seconds being marked",
138 "in the group is cancelled, only to resume being monitored when any",
159 "across all the fans being monitored. The system is immediately hard",
|
| /openbmc/phosphor-power/phosphor-power-sequencer/docs/ |
| H A D | chassis_status.md | 17 is being powered [on](powering_on.md) or [off](powering_off.md).
42 When the system is being powered on, the `state` property of both object paths
46 When the system is being powered off, the `state` property of both object paths
59 When the system is being powered on, the `state` will be changed to 1 for the
75 When the system is being powered off, the `state` will be changed to 0 for the
76 system and for all chassis that are being powered off.
115 - The chassis will **not** be powered on when the system is being powered on.
144 - The chassis will **not** be powered on when the system is being powered on.
167 - The chassis will **not** be powered on when the system is being powered on.
202 - The chassis will **not** be powered on when the system is being powered on.
[all …]
|
| H A D | powering_on.md | 31 that is being powered on. It will set `state` to 0 for each chassis not being
47 In each chassis being powered on, the power sequencer device powers on the
63 When all chassis that were being powered on have finished,
|
| /openbmc/u-boot/doc/device-tree-bindings/serial/ |
| H A D | snps-dw-apb-uart.txt | 28 be reported as active instead of being obtained from the modem status
31 be reported as active instead of being obtained from the modem status
34 be reported as active instead of being obtained from the modem status
37 reported as inactive instead of being obtained from the modem status register.
|
| /openbmc/openbmc/meta-phosphor/recipes-core/systemd/phosphor-systemd-policy/ |
| H A D | service-restart-policy.conf | 18 # failing and a core dump is being generated and collected into a dump,
22 # being restarted indefinitely. Change this to 30s to only allow a service
24 # being put in a permanent fail state.
|
| /openbmc/qemu/tests/qtest/ |
| H A D | libqtest-single.h | 96 * @value: Value being written.
108 * @value: Value being written.
120 * @value: Value being written.
171 * @value: Value being written.
183 * @value: Value being written.
195 * @value: Value being written.
207 * @value: Value being written.
|
| /openbmc/phosphor-fan-presence/docs/monitor/ |
| H A D | method.md | 25 to be calculated out of range of a current target before being marked
29 current target before being marked functional.
39 this method being used.**
64 range before being marked nonfunctional.
|
| /openbmc/openbmc/meta-security/classes/ |
| H A D | aide-db-init.bbclass | 5 # the build cycle allowing for that set being skipped during boot
6 # It has an additional benefit of having not being tamper with
22 # To exclude directories and files from being scanned
|
| /openbmc/phosphor-inventory-manager/ |
| H A D | functor.hpp | 24 * @param[in] action - The action being adapted.
27 * @tparam T - The type of the action being adapted.
39 * @param[in] filter - The filter being adapted.
42 * @tparam T - The type of the filter being adapted.
54 * @param[in] filter - The functor being adapted.
57 * @tparam T - The type of the functor being adapted.
69 * @param[in] method - The functor being adapted.
73 * @tparam U - The type of the functor being adapted.
187 * @tparam T - The type of the property being tested.
302 * @tparam T - The type of the property being tested.
|
| /openbmc/openbmc/meta-security/recipes-security/ecryptfs-utils/files/ |
| H A D | ecryptfs-utils-CVE-2016-6224.patch | 7 being automatically enabled by systemd. This bug affected GPT partitioned
8 NVMe/MMC drives and resulted in the swap partition being used without
33 + being automatically enabled by systemd. This bug affected GPT partitioned
34 + NVMe/MMC drives and resulted in the swap partition being used without
|
| /openbmc/phosphor-dbus-interfaces/yaml/org/freedesktop/UPower/ |
| H A D | Device.interface.yaml | 78 blank if the device is being driven by a user space driver."
135 "Whether power is currently being provided through line power. This
170 "Amount of energy being drained from the source, measured in W. If
171 positive, the source is being discharged, if negative it's being
178 "Voltage in the Cell or being recorded by the meter."
183 "Luminosity being recorded by the meter."
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Software/ |
| H A D | ActivationBlocksTransition.interface.yaml | 8 host while the BIOS is being updated. The managed host, via systemd
12 update is currently being performed and the power-on sequence may safely
|
| /openbmc/openbmc/meta-asrock/meta-x570d4u/recipes-x86/chassis/ |
| H A D | x86-power-control_%.bbappend | 8 # enable button passthrough in x86-power-control, as any pin that's being
9 # passthroughed in hardware can not be used once the SCU is being locked.
|
| /openbmc/u-boot/drivers/led/ |
| H A D | Kconfig | 112 which LED is being acted on. As such, the chosen value must be unique
146 identify which LED is being acted on. As such, the chosen value must
181 identify which LED is being acted on. As such, the chosen value must
216 identify which LED is being acted on. As such, the chosen value must
251 identify which LED is being acted on. As such, the chosen value must
286 identify which LED is being acted on. As such, the chosen value must
|
| /openbmc/phosphor-health-monitor/ |
| H A D | bmc_health_config_json.md | 24 - This indicates the amount of memory being shared between processes within
27 - This indicates the amount of memory being used for caching and temporary
38 - This indicates the number of samples being used for threshold value
|
| /openbmc/gpioplus/src/gpioplus/internal/ |
| H A D | fd.hpp | 20 * @param[in] pathname - The path to the file being opened
30 * @param[in] fd - File descriptor being duplicated
39 * @param[in] fd - File descriptor being duplicated
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | AggregationService.v1_0_3.json | 42 …regates. Access points define the properties needed to access the entity being aggregated and con…
168 "description": "The number of elements in each batch being reset.",
169 …parameter shall contain the number of elements in each batch simultaneously being issued a reset.",
174 "description": "The delay of the batches of elements being reset in seconds.",
175 …tion": "This parameter shall contain the delay of the batches of elements being reset in seconds.",
186 "description": "An array of links to the resources being reset.",
190 … "longDescription": "This parameter shall contain an array of links to the resources being reset.",
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | AggregationService.v1_0_3.json | 42 …regates. Access points define the properties needed to access the entity being aggregated and con…
168 "description": "The number of elements in each batch being reset.",
169 …parameter shall contain the number of elements in each batch simultaneously being issued a reset.",
174 "description": "The delay of the batches of elements being reset in seconds.",
175 …tion": "This parameter shall contain the delay of the batches of elements being reset in seconds.",
186 "description": "An array of links to the resources being reset.",
190 … "longDescription": "This parameter shall contain an array of links to the resources being reset.",
|
| /openbmc/qemu/qapi/ |
| H A D | misc-i386.json | 33 # @launch-update: The guest is currently being launched; plaintext
34 # data and register state is being imported.
36 # @launch-secret: The guest is currently being launched; ciphertext
37 # data is being imported.
41 # @send-update: The guest is currently being migrated out to another
44 # @receive-update: The guest is currently being migrated from another
56 # An enumeration indicating the type of SEV guest being run.
109 # @sev-type: Type of SEV guest being run
|
| /openbmc/openbmc/meta-arm/meta-arm/recipes-bsp/uefi/ |
| H A D | edk2-firmware_%.bbappend | 7 # FIXME - issue with 'RELEASE' firmware, use 'DEBUG'. This is being tracked in
17 # FIXME - issue with 'RELEASE' firmware, use 'DEBUG'. This is being tracked in
|
| /openbmc/openbmc/meta-arm/kas/ |
| H A D | corstone1000-image-configuration.yml | 6 # Intentionally blank to prevent perf from being added to the image in base.yml
26 # prevent the kernel image from being included in the intramfs rootfs
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | gen_valid.py | 165 var_value The value being validated.
212 var_value The value being validated.
285 var_value The value being validated.
327 var_value The value being validated.
363 var_value The value being validated.
397 var_value The value being validated.
420 var_value The value being validated.
437 var_value The value being validated.
454 var_value The value being validated.
482 var_value The value being validated.
[all …]
|