Searched full:being (Results 1 – 25 of 3475) sorted by relevance
12345678910>>...139
| /openbmc/linux/tools/perf/pmu-events/arch/x86/ivytown/ |
| D | uncore-io.json | |
| D | uncore-cache.json | |
| D | memory.json | |
| /openbmc/linux/tools/perf/pmu-events/arch/x86/broadwellde/ |
| D | uncore-io.json | |
| D | frontend.json | |
| D | memory.json | |
| /openbmc/linux/tools/perf/pmu-events/arch/x86/broadwellx/ |
| D | uncore-io.json | |
| D | frontend.json | |
| /openbmc/linux/tools/perf/pmu-events/arch/x86/haswellx/ |
| D | uncore-io.json | |
| /openbmc/linux/tools/perf/pmu-events/arch/x86/ivybridge/ |
| D | memory.json | |
| /openbmc/linux/tools/perf/pmu-events/arch/x86/jaketown/ |
| D | uncore-io.json | |
| D | uncore-cache.json | |
| D | uncore-memory.json | |
| /openbmc/linux/tools/perf/pmu-events/arch/arm64/arm/cortex-a510/ |
| D | branch.json | |
| /openbmc/linux/tools/perf/pmu-events/arch/arm64/arm/cortex-a55/ |
| D | branch.json | |
| D | pipeline.json | |
| /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/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/linux/drivers/iio/dummy/ |
| D | iio_simple_dummy_events.c | |
| /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/linux/tools/perf/pmu-events/arch/x86/broadwell/ |
| D | frontend.json | |
| /openbmc/linux/certs/ |
| D | system_keyring.c | |
| /openbmc/linux/include/linux/ |
| D | wait_bit.h | |
| /openbmc/linux/Documentation/ABI/testing/ |
| D | configfs-most | |
| /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",
|
12345678910>>...139