/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-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-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-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-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-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-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...] |
H A D | aspeed-bmc-ibm-bonnell.dts | 92 fan0-presence { 93 label = "fan0-presence"; 98 fan1-presence { 99 label = "fan1-presence"; 149 /*S0-S7*/ "presence-ps0","presence-ps1","","","power-ffs-sync-history","","","",
|
H A D | aspeed-bmc-facebook-harma.dts | 670 /*Z0-Z7*/ "","","","","","","presence-post-card",""; 689 "presence-scm-cable","power-config-disable-e1s-0", 697 "presence-cpu","smi-control-n", 731 "presence-e1s-0","reset-control-usb-hub", 734 "presence-e1s-1","reset-control-cpu-kbrst", 744 "presence-asic-modules-0","rt-cpu0-p1-force-enable", 745 "presence-asic-modules-1","bios-debug-msg-disable", 747 "presence-cmm","ac-control-n",
|
H A D | aspeed-bmc-ibm-system1.dts | 184 event-nvme0-presence { 185 label = "nvme0-presence"; 190 event-nvme1-presence { 191 label = "nvme1-presence"; 196 event-nvme2-presence { 197 label = "nvme2-presence"; 202 event-nvme3-presence { 203 label = "nvme3-presence"; 712 "presence-ps2", 713 "presence [all...] |
H A D | aspeed-bmc-ampere-mtjefferson.dts | 536 "presence-ocp1","presence-ocp2", 571 /*D0-D7*/ "presence-ps0","presence-ps1","hsc-12vmain-alt2-n","ext-high-temp-n", 584 /*M0-M7*/ "nmi-n","s0-ddr-save","soc-spi-nor-access","presence-cpu0","s0-rtc-lock",
|
/linux/Documentation/ABI/testing/ |
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.
|
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,
|
/linux/drivers/pci/hotplug/ |
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()
|
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() 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 status */ in pnv_php_enable() 554 ret = pnv_php_get_adapter_state(slot, &presence); in pnv_php_enable() 980 u8 presence; pnv_php_interrupt() local [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/devicetree/bindings/mfd/ |
H A D | tps6105x.txt | 15 - regulator: presence of this sub-node puts the chip in regulator mode. 18 - led: presence of this sub-node puts the chip in led mode.
|
/linux/drivers/power/supply/ |
H A D | stc3117_fuel_gauge.c | 129 int presence; member 267 data->presence = 1; in stc3117_init() 347 data->presence = 0; in stc3117_task() 370 /* check battery presence status */ in stc3117_task() 373 data->presence = 0; in stc3117_task() 382 data->presence = 1; in stc3117_task() 496 val->intval = data->presence; in stc3117_get_property()
|
/linux/Documentation/w1/masters/ |
H A D | w1-uart.rst | 24 For instance the timing pattern for a 1-Wire reset and presence detect uses 36 The default baud-rate for reset and presence detection is 9600 and for
|
/linux/drivers/soc/fsl/qbman/ |
H A D | Kconfig | 41 This requires the presence of cpu-affine portals, and performs 55 This requires the presence of cpu-affine portals, and performs
|
/linux/Documentation/admin-guide/laptops/ |
H A D | toshiba_haps.rst | 46 The presence of Solid State Drives (SSD) can make this driver to fail loading, 65 with this device is supported, given the fact that they have the presence of
|
/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
|