Searched full:does (Results 1 – 25 of 1348) sorted by relevance
12345678910>>...54
| /Documentation/ABI/testing/ |
| D | sysfs-block-device | 34 - If the device does not support the unload heads feature,
44 does support the unload feature, then you can tell the kernel
60 turned off. If the device does not support the SATA NCQ
73 This file does not exist if the HBA driver does not implement
95 This file does not exist if the HBA driver does not implement
|
| D | sysfs-fs-fuse | 6 supported, does not exist otherwise
13 passthrough with Android modifications is supported, does not
|
| /Documentation/kbuild/ |
| D | Kconfig.select-break | 10 # Kconfig currently does not check the list of symbols listed on a symbol's
16 # However, when A is set, C can be set as well because Kconfig does not
18 # Kconfig does not visit the dependencies, it breaks the dependencies of B
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-modulator.rst | 52 this is a write-only ioctl, it does not return the actual audio
136 channels, a down-mix of channel 1 and 2. This flag does not
144 left and right channel. This flag does not combine with
146 driver does not support stereo audio it shall fall back to mono.
152 or secondary language only. This flag does not combine with
154 ``V4L2_TUNER_SUB_SAP``. If the hardware does not support the
155 respective audio matrix, or the current video standard does not
176 hardware does not support the respective audio matrix, or the
177 current video standard does not permit SAP the
|
| D | vidioc-g-std.rst | 55 does not return the actual new standard as :ref:`VIDIOC_G_STD <VIDIOC_G_STD>` does. When
56 no flags are given or the current input does not support the requested
59 standards. If the current input or output does not support standard
61 does not set the ``V4L2_IN_CAP_STD`` flag), then ``ENODATA`` error code is
|
| D | func-poll.rst | 67 driver does not capture yet, the :c:func:`poll()` function starts
74 driver does not stream yet, the :c:func:`poll()` function starts
81 streaming if the driver does not stream yet. This makes it possible to
102 The driver does not support multiple read or write streams and the
|
| D | vidioc-encoder-cmd.rst | 104 this command does nothing. No flags are defined for this command.
116 encoder is already stopped, this command does nothing.
127 already paused, this command does nothing. No flags are defined
133 the encoder is already running, this command does nothing. No
150 Does not apply to :ref:`encoder`.
|
| D | selection-api-intro.rst | 26 the device does supports neither cropping nor composing. Their size and
27 position will be fixed in such a case. If the device does not support
|
| /Documentation/driver-api/md/ |
| D | raid5-ppl.rst | 13 this, md by default does not allow starting a dirty degraded array.
29 stripe. It does not require a dedicated journaling drive. Write performance is
31 and the journaling drive does not become a bottleneck or a single point of
35 not a true journal. It does not protect from losing in-flight data, only from
|
| /Documentation/devicetree/bindings/serial/ |
| D | snps-dw-apb-uart.yaml | 96 parameter. Define this if your UART does not implement the busy functionality.
110 status register. Define this if your serial port does not use this
117 status register. Define this if your serial port does not use this
124 status register. Define this if your serial port does not use this
131 register. Define this if your serial port does not use this pin.
|
| /Documentation/litmus-tests/atomic/ |
| D | cmpxchg-fail-unordered-2.litmus | 6 * Demonstrate that a failing cmpxchg() operation does not act as either
8 * does act as both an acquire and a release operation.)
|
| D | cmpxchg-fail-unordered-1.litmus | 6 * Demonstrate that a failing cmpxchg() operation does not act as a
7 * full barrier. (In contrast, a successful cmpxchg() does act as a
|
| /Documentation/devicetree/bindings/timer/ |
| D | arm,arch_timer_mmio.yaml | 39 only where necessary to work around broken firmware which does not configure
50 description: Firmware does not initialize any of the generic timer CPU
57 description: The main counter does not tick when the system is in
58 low-power system suspend on some SoCs. This behavior does not match the
|
| D | arm,arch_timer.yaml | 62 only where necessary to work around broken firmware which does not configure
93 description: Firmware does not initialize any of the generic timer CPU
100 description: The main counter does not tick when the system is in
101 low-power system suspend on some SoCs. This behavior does not match the
|
| /Documentation/filesystems/ |
| D | hfs.rst | 42 Select partition number n from the devices. Does only makes
44 For disk devices the generic partition parsing code does this
54 HFS is not a UNIX filesystem, thus it does not have the usual features you'd
61 HFS does on the other have the concepts of multiple forks per file. These
|
| /Documentation/virt/kvm/x86/ |
| D | errata.rst | 54 KVM does not virtualize guest MTRR memory types. KVM emulates accesses to MTRR
55 MSRs, i.e. {RD,WR}MSR in the guest will behave as expected, but KVM does not
61 KVM does not virtualize CR0.CD on Intel CPUs. Similar to MTRR MSRs, KVM
66 Note, this erratum does not affect AMD CPUs, which fully virtualize CR0.CD in
|
| /Documentation/watchdog/ |
| D | watchdog-kernel-api.rst | 11 This document does not describe what a WatchDog Timer (WDT) Driver or Device is.
12 It also does not describe the API which can be used by user space to communicate
16 So what does this document describe? It describes the API that can be used by
19 the same code does not have to be reproduced each time. This also means that
84 This is the time after which the system will reboot if user space does
99 seconds. max_hw_heartbeat_ms must be set if a driver does not implement
159 driver supporting such hardware does not have to implement the stop routine.
165 If a watchdog driver does not implement the stop function, it must set
173 Most hardware that does not support this as a separate function uses the
175 the watchdog timer driver core does: to send a keepalive ping to the watchdog
[all …]
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | pmc.txt | 18 Compatibility does not include bit assignments in SCCR/PMCDR/DEVDISR; these
52 hardware does not have DEVDISR2) upon a request for permanent device
53 disabling. This sleep controller does not support configuring devices
|
| /Documentation/admin-guide/ |
| D | sysfs-rules.rst | 6 by the kernel developers that the Linux kernel does not provide a stable
22 It makes assumptions about sysfs which are not true. Its API does not
96 context properties. If the device ``eth0`` or ``sda`` does not have a
97 "driver"-link, then this device does not have a driver. Its value is empty.
123 can be ignored. If it does not exist, you always have to scan all three
143 device directory does not end in ``/sys/devices/``, you can use the
153 directory does not contain directories for child devices, these links
|
| /Documentation/arch/riscv/ |
| D | uabi.rst | 57 Similarly, for S-mode extensions, presence in one of these lines does not
61 Inversely, the absence of an extension in these lines does not necessarily mean
62 the hardware does not support that feature. The running kernel may not recognize
|
| /Documentation/nvme/ |
| D | feature-and-quirk-policy.rst | 33 does not aim to implement every feature in the specification. Every additional
44 on-wire protocol, does not contradict any of the NVMe specifications.
45 2. Does not conflict with the Linux architecture, nor the design of the
|
| /Documentation/w1/masters/ |
| D | omap-hdq.rst | 26 initialization pulse.In HDQ mode, the firmware does not require the host to
29 does not respond with a presence pulse as it does in the 1-Wire protocol.
|
| /Documentation/arch/arm/nwfpe/ |
| D | notes.rst | 5 been able to track it down yet. This does not occur with the emulator
23 extended, then does the multiply in extended precision.
|
| /Documentation/spi/ |
| D | spi-sc18is602.rst | 21 The driver does not probe for supported chips, since the SI18IS602/603 does not
|
| /Documentation/firmware-guide/acpi/ |
| D | video_extension.rst | 14 The ACPI video driver does 3 things regarding backlight control.
28 And what ACPI video driver does is:
88 For this case, ACPI video driver does not need to do anything(actually,
115 received a notification, it will set the backlight level accordingly. This does
|
12345678910>>...54