Home
last modified time | relevance | path

Searched full:either (Results 1 – 25 of 905) sorted by relevance

12345678910>>...37

/Documentation/ABI/testing/
Dsysfs-platform-msi-laptop13 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
Dsysfs-bus-iio-temperature-max318567 Reading returns either '1' or '0'.
21 Reading returns either '1' or '0'.
Dsysfs-bus-iio-frequency-ad952310 Reading returns either '1' or '0'.
18 Reading returns either '1' or '0'. '1' means that the
Dsysfs-driver-altera-cvp6 Contains either 1 or 0 and controls if configuration
Dsysfs-bus-iio-meas-spec5 Reading returns either '1' or '0'. '1' means that the
Dsysfs-kernel-irq53 Description: The type of the interrupt. Either the string 'level' or 'edge'.
59 Description: The wakeup state of the interrupt. Either the string
/Documentation/devicetree/bindings/serial/
Damlogic,meson-uart.yaml15 of SoCs, and can be present either in the "Always-On" power domain or the
49 - description: the bus core clock, either the clk81 clock or the gate clock
50 - description: the source of the baudrate generator, can be either the xtal or the pclk
/Documentation/virt/kvm/
Ds390-diag.txt16 all supported DIAGNOSE calls need to be handled by either KVM or its
43 provides either s390-virtio (subcodes 0-2) or virtio-ccw (subcode 3).
46 the function's return code, which is either a return code or a subcode
59 Handled by either userspace or KVM (ioeventfd case).
/Documentation/scsi/
DLICENSE.FlashPoint8 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
Dscsi_eh.txt43 Once LLDD gets hold of a scmd, either the LLDD will complete the
108 will either be retried (if the number of retries is not exhausted)
128 the host either complete normally, fail and get added to eh_cmd_q, or
131 If all scmds either complete or fail, the number of in-flight scmds
227 either retry or error-finish (notify upper layer of failure) recovered
327 either offline or ready, scsi_eh_finish_cmd() is invoked for
358 If STU succeeds and the sdev is either offline or ready,
410 flushes eh_done_q by either retrying or notifying upper
419 all failed scmds and either ready for new commands or offline. Also,
451 - Either scsi_queue_insert() or scsi_finish_command() is called on
/Documentation/devicetree/
Dchangesets.txt2 in the live tree in such a way that either the full set of changes
24 3. of_changeset_apply() - Apply the changes to the tree. Either the
/Documentation/devicetree/bindings/mips/cavium/
Ductl.txt20 either "crystal" or "external".
31 /* Either "crystal" or "external" */
/Documentation/xtensa/
Dbooting.rst18 - 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/powerpc/fsl/
Dlbc.txt5 - #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/admin-guide/gpio/
Dsysfs.rst75 reads as either "in" or "out". This value may
87 reads as either 0 (low) or 1 (high). If the GPIO
97 poll(2) returns, either lseek(2) to the beginning of the sysfs
102 reads as either "none", "rising", "falling", or
110 reads as either 0 (false) or 1 (true). Write
/Documentation/driver-api/
Ddevice_connection.rst19 They are only descriptions which are not tied to either of the devices directly.
28 either endpoint device in the description. If the connections are defined in
/Documentation/devicetree/bindings/auxdisplay/
Dhit,hd44780.txt5 which can be used in either 4-bit or 8-bit mode.
9 - data-gpios: Must contain an array of either 4 or 8 GPIO specifiers,
/Documentation/devicetree/bindings/pinctrl/
Dnvidia,tegra124-dpaux-padctl.txt5 which can be assigned to either the DPAUX channel or to an I2C
28 - function: Must be either "aux", "i2c" or "off".
Dpinctrl-bindings.txt59 used in an SoC either without a pin controller, or where the
108 driver for the pin controller. This property can be set either
148 (either this or "pins" must be specified)
149 pins - the list of pins to select with this function (either
242 apply to (either this, "group" or "pinmux" has to be
246 individual pins (either this, "pins" or "pinmux" has
249 that properties in the node apply to (either this,
Dpinctrl-vt8500.txt4 either a GPIO in, GPIO out or as an alternate function (I2C, SPI etc).
44 Each of wm,function and wm,pull may contain either a single value which
/Documentation/devicetree/bindings/mtd/
Dnxp-spifi.txt5 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/vm/
Dpage_frags.rst15 memory for use as either an sk_buff->head, or to be used in the "frags"
24 either a per-cpu limitation, or a per-cpu limitation and forcing interrupts
/Documentation/block/
Ddeadline-iosched.rst51 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/power/
Dapm-acpi.rst6 odds are it supports either Advanced Power Management (APM) or
12 The best way to determine which, if either, your system supports is to
/Documentation/devicetree/bindings/clock/
Didt,versaclock5.txt20 5p49v6901: (required) either or both of XTAL or CLKIN
29 5p49v6901: (required) either or both of "xin", "clkin".

12345678910>>...37