Searched full:does (Results 1 – 25 of 1037) sorted by relevance
12345678910>>...42
| /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/media/uapi/v4l/ |
| D | vidioc-g-modulator.rst | 59 this is a write-only ioctl, it does not return the actual audio
144 channels, a down-mix of channel 1 and 2. This flag does not
152 left and right channel. This flag does not combine with
154 driver does not support stereo audio it shall fall back to mono.
160 or secondary language only. This flag does not combine with
162 ``V4L2_TUNER_SUB_SAP``. If the hardware does not support the
163 respective audio matrix, or the current video standard does not
184 hardware does not support the respective audio matrix, or the
185 current video standard does not permit SAP the
|
| D | vidioc-g-std.rst | 60 does not return the actual new standard as :ref:`VIDIOC_G_STD <VIDIOC_G_STD>` does. When
61 no flags are given or the current input does not support the requested
64 standards. If the current input or output does not support standard
66 does not set the ``V4L2_IN_CAP_STD`` flag), then ``ENODATA`` error code is
|
| D | func-poll.rst | 77 driver does not capture yet, the :ref:`poll() <func-poll>` function starts
84 driver does not stream yet, the :ref:`poll() <func-poll>` function starts
91 streaming if the driver does not stream yet. This makes it possible to
113 The driver does not support multiple read or write streams and the
|
| D | vidioc-g-audioout.rst | 58 write-only ioctl, it does not return the current audio output attributes
59 as ``VIDIOC_G_AUDOUT`` does.
107 number of the selected audio output is out of bounds or it does not
|
| D | selection-api-intro.rst | 33 the device does supports neither cropping nor composing. Their size and
34 position will be fixed in such a case. If the device does not support
|
| /Documentation/devicetree/bindings/serial/ |
| D | snps-dw-apb-uart.yaml | 61 parameter. Define this if your UART does not implement the busy functionality.
74 status register. Define this if your serial port does not use this
81 status register. Define this if your serial port does not use this
88 status register. Define this if your serial port does not use this
95 register. Define this if your serial port does not use this pin.
|
| /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/timer/ |
| D | arm,arch_timer.yaml | 45 only where necessary to work around broken firmware which does not configure
70 description: Firmware does not initialize any of the generic timer CPU
77 description: The main counter does not tick when the system is in
78 low-power system suspend on some SoCs. This behavior does not match the
|
| D | arm,arch_timer_mmio.yaml | 37 only where necessary to work around broken firmware which does not configure
48 description: Firmware does not initialize any of the generic timer CPU
55 description: The main counter does not tick when the system is in
56 low-power system suspend on some SoCs. This behavior does not match the
|
| /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/filesystems/ |
| D | hfs.txt | 37 Select partition number n from the devices. Does only makes
39 For disk devices the generic partition parsing code does this
49 HFS is not a UNIX filesystem, thus it does not have the usual features you'd
56 HFS does on the other have the concepts of multiple forks per file. These
|
| /Documentation/networking/ |
| D | baycom.txt | 20 however if you have a broken UART clone that does not have working
27 does not work with your UART.
49 The modem does all the filtering and regenerates the receiver clock.
59 and can therefore be fed from the parallel port and does not require
72 starts to send as soon as there's a packet to transmit and does not care
130 The modem simply does not provide enough information to implement
|
| D | ray_cs.txt | 9 card. This driver is in early development and does have bugs. See the known
128 tcpdump does not understand 802.11 headers, so it can't
139 Does not work with non x86
141 Does not work with SMP
|
| /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/virt/kvm/arm/ |
| D | psci.txt | 37 KVM_REG_ARM_SMCCC_ARCH_WORKAROUND_1_NOT_AVAIL: KVM does not offer
51 available. KVM does not offer firmware support for the workaround.
53 unknown. KVM does not offer firmware support for the workaround.
|
| /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/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/spi/ |
| D | spi-sc18is602.rst | 21 The driver does not probe for supported chips, since the SI18IS602/603 does not
|
| /Documentation/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/block/ |
| D | inline-encryption.rst | 76 The above is sufficient for simple cases, but does not work if there is a
87 that eventually passes the bio down to a device that really does support IE, we
89 device with IE support. However, blk-crypto does not know a priori whether a
91 not. So in the case that a particular device does not support IE, since it is
114 What blk-crypto does on bio submission
120 request queue the bio is being submitted to (and if this KSM does not exist,
127 In this case, blk-crypto does nothing; it treats the bio as not having
|
| /Documentation/devicetree/bindings/ |
| D | chosen.txt | 4 The chosen node does not represent a real device, but serves as a place
6 arguments. Data in the chosen node does not represent the hardware.
102 While this property does not represent a real hardware, the address
120 While this property does not represent a real hardware, the address
|
| /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
|
| /Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 45 does not define timeouts but the MIPI SoundWire DisCo document adds
60 Note that SoundWire does not provide a mechanism to detect illegal values
63 implementation does not provide a recovery mechanism for such errors, Slave
|
| /Documentation/networking/device_drivers/davicom/ |
| D | dm9000.txt | 113 This can be used to signify that the board does not have an
118 Switch to using the simpler PHY polling method which does not
143 expensive MII accesses. This method is faster, but does not print
160 2) TCP/UDP checksum offloading, which the driver does not currently support.
|
12345678910>>...42