| /linux/arch/arm/boot/dts/aspeed/ |
| H A D | aspeed-bmc-ufispace-ncplite.dts | 80 psu0-presence-l {
81 label = "psu0-presence-l";
86 psu1-presence-l {
87 label = "psu1-presence-l";
111 fan0-presence {
112 label = "fan0-presence";
117 fan1-presence {
118 label = "fan1-presence";
123 fan2-presence {
124 label = "fan2-presence";
[all...] |
| H A D | aspeed-bmc-inspur-fp5280g2.dts | 82 event-ps0-presence {
83 label = "ps0-presence";
88 event-ps1-presence {
89 label = "ps1-presence";
100 event-fan0-presence {
101 label = "fan0-presence";
106 event-fan1-presence {
107 label = "fan1-presence";
112 event-fan2-presence {
113 label = "fan2-presence";
[all...] |
| H A D | aspeed-bmc-bytedance-g220a.dts | 114 event-rear-riser1-presence {
115 label = "rear-riser1-presence";
126 event-rear-riser0-presence {
127 label = "rear-riser0-presence";
168 event-fan0-presence {
169 label = "fan0-presence";
174 event-fan1-presence {
175 label = "fan1-presence";
180 event-fan2-presence {
181 label = "fan2-presence";
[all...] |
| H A D | aspeed-bmc-opp-mowgli.dts | 61 event-ps0-presence {
62 label = "ps0-presence";
67 event-ps1-presence {
68 label = "ps1-presence";
84 event-fan0-presence {
85 label = "fan0-presence";
90 event-fan1-presence {
91 label = "fan1-presence";
96 event-fan2-presence {
97 label = "fan2-presence";
[all...] |
| H A D | aspeed-bmc-opp-witherspoon.dts | 66 event-ps0-presence {
67 label = "ps0-presence";
72 event-ps1-presence {
73 label = "ps1-presence";
88 event-fan0-presence {
89 label = "fan0-presence";
94 event-fan1-presence {
95 label = "fan1-presence";
100 event-fan2-presence {
101 label = "fan2-presence";
[all...] |
| H A D | aspeed-bmc-facebook-greatlakes.dts | 247 /*B0-B7*/ "power-bmc-nic","presence-ocp-debug",
250 /*C0-C7*/ "presence-ocp-nic","","","reset-cause-nic-primary",
256 "","","","presence-emmc",
259 "presence-mb-slot1","presence-mb-slot2",
260 "presence-mb-slot3","presence-mb-slot4",
273 /*S0-S7*/ "","","power-p5v-usb","presence-bmc-tpm","","","","",
|
| H A D | aspeed-bmc-ibm-fuji.dts | 216 event-fan0-presence {
218 label = "fan0-presence";
222 event-fan1-presence {
224 label = "fan1-presence";
228 event-fan2-presence {
230 label = "fan2-presence";
234 event-fan3-presence {
236 label = "fan3-presence";
342 "presence-ps0",
343 "presence
[all...] |
| H A D | aspeed-bmc-ibm-everest.dts | 216 event-fan0-presence {
217 label = "fan0-presence";
222 event-fan1-presence {
223 label = "fan1-presence";
228 event-fan2-presence {
229 label = "fan2-presence";
234 event-fan3-presence {
235 label = "fan3-presence";
340 "presence-ps0",
341 "presence
[all...] |
| H A D | aspeed-bmc-ibm-blueridge.dts | 139 event-fan0-presence {
141 label = "fan0-presence";
145 event-fan1-presence {
147 label = "fan1-presence";
151 event-fan2-presence {
153 label = "fan2-presence";
157 event-fan3-presence {
159 label = "fan3-presence";
163 event-fan4-presence {
165 label = "fan4-presence";
[all...] |
| H A D | aspeed-bmc-ibm-rainier.dts | 136 event-fan0-presence {
137 label = "fan0-presence";
142 event-fan1-presence {
143 label = "fan1-presence";
148 event-fan2-presence {
149 label = "fan2-presence";
154 event-fan3-presence {
155 label = "fan3-presence";
160 event-fan4-presence {
161 label = "fan4-presence";
[all...] |
| /linux/Documentation/driver-api/ |
| H A D | device_link.rst | 17 Secondly, the driver core by default does not enforce any driver presence
22 another one both with regards to driver presence *and* with regards to
30 presence on the supplier. The consumer devices are not probed before the
34 When driver presence on the supplier is irrelevant and only correct
37 enforcing driver presence on the supplier is optional.
60 represents a driver presence dependency, yet is added from the consumer's
64 presence of the supplier after adding the link, and defer probing on
65 non-presence. [Note that it is valid to create a link from the consumer's
82 driver presence dependency is needed (but only correct suspend/resume and
109 Driver authors should be aware that a driver presence dependenc
[all...] |
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-platform-ts5500 | 6 Indicates the presence of an A/D Converter. If it is present,
14 Indicates the presence of an external reset. If it is present,
45 Indicates the presence of the RS485 option. If it is present,
53 Indicates the presence of the SRAM option. If it is present,
|
| H A D | sysfs-driver-amd-sfh | 5 Human presence detection (HPD) enable/disable.
7 presence of a human and will send an interrupt that can be
10 the presence of a human.
|
| /linux/Documentation/devicetree/bindings/phy/ |
| H A D | nvidia,tegra194-xusb-padctl.yaml | 240 description: A boolean property whose presence determines
247 A boolean property whole presence indicates that the port
278 description: A boolean property whose presence determines
285 A boolean property whole presence indicates that the port
316 description: A boolean property whose presence determines
323 A boolean property whole presence indicates that the port
354 description: A boolean property whose presence determines
361 A boolean property whole presence indicates that the port
392 description: A boolean property whose presence determines
425 description: A boolean property whose presence determine
[all...] |
| H A D | nvidia,tegra186-xusb-padctl.yaml | 249 description: A boolean property whose presence determines
256 A boolean property whole presence indicates that the port
287 description: A boolean property whose presence determines
294 A boolean property whole presence indicates that the port
325 description: A boolean property whose presence determines
332 A boolean property whole presence indicates that the port
355 description: A boolean property whose presence determines
376 description: A boolean property whose presence determines
397 description: A boolean property whose presence determines
|
| H A D | nvidia,tegra210-xusb-padctl.yaml | 368 description: A boolean property whose presence determines
375 A boolean property whole presence indicates that the port
406 description: A boolean property whose presence determines
413 A boolean property whole presence indicates that the port
444 description: A boolean property whose presence determines
451 A boolean property whole presence indicates that the port
482 description: A boolean property whose presence determines
489 A boolean property whole presence indicates that the port
524 description: A boolean property whose presence determines
545 description: A boolean property whose presence determine
[all...] |
| H A D | nvidia,tegra124-xusb-padctl.yaml | 346 description: A boolean property whose presence determines
353 A boolean property whole presence indicates that the port
381 description: A boolean property whose presence determines
388 A boolean property whole presence indicates that the port
416 description: A boolean property whose presence determines
423 A boolean property whole presence indicates that the port
439 description: A boolean property whose presence determines
469 description: A boolean property whose presence determines
490 description: A boolean property whose presence determines
|
| /linux/drivers/pci/hotplug/ |
| H A D | pnv_php.c | 413 uint8_t presence = OPAL_PCI_SLOT_EMPTY; in pnv_php_get_adapter_state() local
417 * Retrieve presence status from firmware. If we can't in pnv_php_get_adapter_state()
420 ret = pnv_pci_get_presence_state(php_slot->id, &presence); in pnv_php_get_adapter_state()
423 presence == OPAL_PCI_SLOT_EMPTY) { in pnv_php_get_adapter_state()
427 * that don't properly assert Presence Detect State, as in pnv_php_get_adapter_state()
432 presence = OPAL_PCI_SLOT_PRESENT; in pnv_php_get_adapter_state()
435 *state = presence; in pnv_php_get_adapter_state()
438 SLOT_WARN(php_slot, "Error %d getting presence\n", ret); in pnv_php_get_adapter_state()
545 uint8_t presence = OPAL_PCI_SLOT_EMPTY; in pnv_php_enable() local
553 /* Retrieve slot presence statu in pnv_php_enable()
980 u8 presence; pnv_php_interrupt() local
[all...] |
| H A D | pciehp_pci.c | 87 * @presence: whether the card is still present in the slot;
95 void pciehp_unconfigure_device(struct controller *ctrl, bool presence) in pciehp_unconfigure_device() argument
104 if (!presence) in pciehp_unconfigure_device()
131 if (presence) { in pciehp_unconfigure_device()
|
| /linux/tools/testing/selftests/alsa/conf.d/ |
| H A D | Lenovo_ThinkPad_P1_Gen2.conf | 68 # use default tests, check for the presence
76 # # check for the presence
81 # # check for the presence
|
| /linux/include/linux/ |
| H A D | amd-pmf-io.h | 19 * @MT_HPD: Message ID to know the Human presence info from MP2 FW
30 * enum sfh_hpd_info - Query the Human presence information
44 * @user_present: Populates the user presence information
|
| /linux/Documentation/dev-tools/ |
| H A D | testing-devices.rst | 25 * **Coverage**: Error (or more critical) log messages presence coming from any
31 * **Coverage**: Presence and probe status of USB or PCI devices that have been
39 * **Coverage**: Presence of all devices
|
| /linux/Documentation/devicetree/bindings/timer/ |
| H A D | arm,arch_timer.yaml | 73 description: Indicates the presence of an erratum found in Allwinner SoCs,
79 description: Indicates the presence of QorIQ erratum A-008585, which says
86 description: Indicates the presence of Hisilicon erratum 161010101, which
|
| /linux/Documentation/arch/powerpc/ |
| H A D | elf_hwcaps.rst | 16 presence of these features to userspace through a set of flags called HWCAPs,
36 HWCAP is the preferred method to test for the presence of a feature rather
49 registers, interrupts, etc. The presence or absence of a facility indicates
61 context, e.g., the presence of the BOOKE feature implies that the server
|
| /linux/Documentation/arch/arm64/ |
| H A D | sme.rst | 24 * The presence of SME is reported to userspace via HWCAP2_SME in the aux vector
25 AT_HWCAP2 entry. Presence of this flag implies the presence of the SME
29 * The presence of SME2 is reported to userspace via HWCAP2_SME2 in the
30 aux vector AT_HWCAP2 entry. Presence of this flag implies the presence of
38 It does not guarantee the presence of the system interfaces described in the
42 * There are a number of optional SME features, presence of these is reported
|