| /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-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-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-opp-tacoma.dts | 53 event-ps0-presence { 54 label = "ps0-presence"; 59 event-ps1-presence { 60 label = "ps1-presence"; 70 event-fan0-presence { 71 label = "fan0-presence"; 76 event-fan1-presence { 77 label = "fan1-presence"; 82 event-fan2-presence { 83 label = "fan2-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-ibm-balcones.dts | 31 event-fan0-presence { 33 label = "fan0-presence"; 37 event-fan1-presence { 39 label = "fan1-presence"; 154 /*S0-S7*/ "presence-ps0","presence-ps1","","","power-ffs-sync-history","","",
|
| 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-ps3", [all …]
|
| H A D | aspeed-bmc-inventec-transformers.dts | 272 /*B0-B7*/ "presence-ps0","power-chassis-good","","","","","presence-ps1","",
|
| /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-st | 11 appear in sysfs as its presence is conditional upon debug
|
| /linux/drivers/pci/hotplug/ |
| H A D | pciehp_pci.c | 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 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() 545 uint8_t presence = OPAL_PCI_SLOT_EMPTY; in pnv_php_enable() local 554 ret = pnv_php_get_adapter_state(slot, &presence); in pnv_php_enable() 564 if (presence == OPAL_PCI_SLOT_EMPTY) { in pnv_php_enable() 609 if (presence == OPAL_PCI_SLOT_PRESENT) { in pnv_php_enable() 980 u8 presence; in 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 dependency for managed [all …]
|
| H A D | slimbus.rst | 56 device with a 1-byte logical address after the devices report presence on the 73 Since SLIMbus devices have mechanisms for reporting their presence, the 75 presence on the bus.
|
| /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/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
|
| H A D | ds2490.rst | 47 short, alarming presence on reset, and no presence on reset, but the
|
| /linux/arch/riscv/ |
| H A D | Kconfig.vendor | 27 not be detected at boot and their presence not reported to userspace. 53 not be detected at boot and their presence not reported to userspace.
|
| /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/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/staging/ |
| H A D | speculation.rst | 16 observe its impact on microarchitectural state, such as the presence or 20 For example, in the presence of branch prediction, it is possible for bounds
|
| /linux/Documentation/ABI/stable/ |
| H A D | sysfs-bus-w1 | 6 control systems are attached/generate presence for as short as
|
| /linux/Documentation/devicetree/bindings/display/ |
| H A D | multi-inno,mi0283qt.txt | 10 - dc-gpios: D/C pin. The presence/absence of this GPIO determines
|
| /linux/Documentation/arch/riscv/ |
| H A D | uabi.rst | 56 In both lines, the presence of an extension guarantees only that the hardware 59 Similarly, for S-mode extensions, presence in one of these lines does not
|