Searched full:either (Results 1 – 25 of 1164) sorted by relevance
12345678910>>...47
| /Documentation/ABI/testing/ |
| D | sysfs-platform-msi-laptop | 13 Enable automatic brightness control: contains either 0 or 1. If
22 WLAN subsystem enabled: contains either 0 or 1.
29 Bluetooth subsystem enabled: contains either 0 or 1. Please
38 Contains either 0 or 1 and indicates if touchpad is turned on.
46 Contains either 0 or 1 and indicates if turbo mode is turned
59 Contains either 0 or 1 and indicates if ECO mode is turned on.
80 Contains either 0 or 1 and indicates if fan speed is controlled
|
| D | sysfs-bus-iio-frequency-ad9523 | 10 Reading returns either '1' or '0'.
20 Reading returns either '1' or '0'. '1' means that the
|
| /Documentation/devicetree/bindings/iio/frequency/ |
| D | adi,adrf6780.yaml | 55 Intermediate Frequency Mode Enable. Either IF Mode or I/Q Mode
61 I/Q Mode Enable. Either IF Mode or I/Q Mode can be enabled at a
68 Oscillator Input Frequency. Either LOx1 or LOx2 can be enabled
75 output frequency (LO x1). Either LOx1 or LOx2 can be enabled
|
| /Documentation/scsi/ |
| D | LICENSE.FlashPoint | 8 the terms of either:
11 Foundation; either version 2, or (at your option) any later version,
19 or FITNESS FOR A PARTICULAR PURPOSE. See either the GNU General Public
|
| D | scsi_eh.rst | 48 Once LLDD gets hold of a scmd, either the LLDD will complete the
121 will either be retried (if the number of retries is not exhausted)
143 the host either complete normally, fail and get added to eh_cmd_q, or
146 If all scmds either complete or fail, the number of in-flight scmds
247 either retry or error-finish (notify upper layer of failure) recovered
361 either offline or ready, scsi_eh_finish_cmd() is invoked for
392 If STU succeeds and the sdev is either offline or ready,
444 flushes eh_done_q by either retrying or notifying upper
454 all failed scmds and either ready for new commands or offline. Also,
488 - Either scsi_queue_insert() or scsi_finish_command() is called on
|
| /Documentation/virt/kvm/arm/ |
| D | pkvm.rst | 30 in either protected or non-protected state, although the hypervisor is still
31 responsible for managing most of the VM metadata in either case.
47 guest pages. It also requires that the VMM has either ``CAP_IPC_LOCK`` or
84 either by the ``KVM_SET_ONE_REG`` interface or by a call to PSCI ``CPU_ON``.
|
| /Documentation/devicetree/bindings/timer/ |
| D | nvidia,tegra-timer.yaml | 21 # Either a single combined interrupt or up to 14 individual interrupts
43 # Either a single combined interrupt or up to 6 individual interrupts
57 # Either a single combined interrupt or up to 4 individual interrupts
69 timestamp counter. The TMRs run at either a fixed 1 MHz clock rate derived
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-class-multicolor.yaml | 14 either integrated multi-color LED elements (like RGB, RGBW, RGBWA-UV
28 For multicolor LED support this property should be defined as either
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | lbc.txt | 5 - #address-cells : Should be either two or three. The first cell is the
8 - #size-cells : Either one or two, depending on how large each chipselect
|
| /Documentation/devicetree/bindings/mips/cavium/ |
| D | uctl.txt | 20 either "crystal" or "external".
31 /* Either "crystal" or "external" */
|
| /Documentation/arch/xtensa/ |
| D | booting.rst | 18 - For configurations with MMUv3 and CONFIG_MMU=y the address may be either a
19 virtual or physical address. In either case it must be within the default
|
| /Documentation/devicetree/bindings/serial/ |
| D | amlogic,meson-uart.yaml | 15 of SoCs, and can be present either in the "Always-On" power domain or the
71 - description: the bus core clock, either the clk81 clock or the gate clock
72 - description: the source of the baudrate generator, can be either the xtal or the pclk
|
| /Documentation/userspace-api/gpio/ |
| D | sysfs.rst | 78 reads as either "in" or "out". This value may
90 reads as either 0 (inactive) or 1 (active). If the GPIO
101 zero. Alternatively, either lseek(2) to the beginning of the
106 reads as either "none", "rising", "falling", or
114 reads as either 0 (false) or 1 (true). Write
|
| /Documentation/devicetree/ |
| D | changesets.rst | 8 in the live tree in such a way that either the full set of changes
30 3. of_changeset_apply() - Apply the changes to the tree. Either the
|
| /Documentation/virt/kvm/s390/ |
| D | s390-diag.rst | 19 all supported DIAGNOSE calls need to be handled by either KVM or its
46 provides either s390-virtio (subcodes 0-2) or virtio-ccw (subcode 3).
49 the function's return code, which is either a return code or a subcode
62 Handled by either userspace or KVM (ioeventfd case).
|
| /Documentation/admin-guide/gpio/ |
| D | gpio-aggregator.rst | 15 system permissions, on an all-or-nothing basis: either a GPIO controller is
80 Binding a device to the GPIO Aggregator is performed either by modifying the
94 it can be bound to the GPIO Aggregator by either:
|
| /Documentation/hwmon/ |
| D | gsc-hwmon.rst | 21 The voltage inputs are scaled either internally or by the driver depending
33 either internally or by the driver depending on the GSC version and firmware.
|
| /Documentation/devicetree/bindings/display/bridge/ |
| D | synopsys,dw-hdmi.yaml | 36 - description: The bus clock for either AHB and APB
52 The HDMI DDC bus can be connected to either a system I2C master or the
|
| /Documentation/devicetree/bindings/arm/ |
| D | microchip,sparx5.yaml | 36 either spi-nand or eMMC storage (mount option).
43 either spi-nand or eMMC storage (mount option).
|
| /Documentation/mm/ |
| D | page_frags.rst | 13 memory for use as either an sk_buff->head, or to be used in the "frags"
22 either a per-cpu limitation, or a per-cpu limitation and forcing interrupts
|
| /Documentation/devicetree/bindings/mtd/ |
| D | nxp-spifi.txt | 5 mode 0 or 3. The controller operates in either command or memory
25 - spi-cpol : Controller only supports mode 0 and 3 so either
|
| /Documentation/block/ |
| D | deadline-iosched.rst | 51 don't want to starve writes indefinitely either. So writes_starved controls
61 with a request that is already on the queue. Either it fits in the back of that
62 request, or it fits at the front. That is called either a back merge candidate
|
| /Documentation/trace/ |
| D | ring-buffer-map.rst | 39 either resize it (either by increasing the entire size of the ring-buffer or
43 Concurrent readers (either another application mapping that ring-buffer or the
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | ti,k3-r5f-rproc.yaml | 15 either in a LockStep mode providing safety/fault tolerance features or in a
72 It should be either a value of 1 (LockStep mode) or 0 (Split mode) on
76 It should be either a value of 0 (Split mode) or 2 (Single-CPU mode) and
103 either of them can be configured to appear at that R5F's address 0x0.
181 either a value of 1 (enabled) or 0 (disabled), default is disabled
190 either a value of 1 (enabled) or 0 (disabled), default is enabled if
198 address 0 (from core's view). Should be either a value of 1 (ATCM
|
| /Documentation/power/ |
| D | apm-acpi.rst | 6 odds are it supports either Advanced Power Management (APM) or
12 The best way to determine which, if either, your system supports is to
|
12345678910>>...47