| /Documentation/PCI/endpoint/ |
| D | pci-test-howto.rst | 151 BAR4: NOT OKAY
152 BAR5: NOT OKAY
157 LEGACY IRQ: NOT OKAY
175 MSI17: NOT OKAY
176 MSI18: NOT OKAY
177 MSI19: NOT OKAY
178 MSI20: NOT OKAY
179 MSI21: NOT OKAY
180 MSI22: NOT OKAY
181 MSI23: NOT OKAY
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-devices-power | 25 + "disabled\n" not to do so;
31 For the devices that are not capable of generating system wakeup
32 events this file is not present. In that case the device cannot
86 attribute is read-only. If the device is not capable to wake up
87 the system from sleep states, this attribute is not present.
88 If the device is not enabled to wake up the system from sleep
98 is read-only. If the device is not capable to wake up the
99 system from sleep states, this attribute is not present. If
100 the device is not enabled to wake up the system from sleep
111 is not capable to wake up the system from sleep states, this
[all …]
|
| /Documentation/driver-api/md/ |
| D | raid5-ppl.rst | 11 that have not been touched by a write request during the unclean shutdown can
13 this, md by default does not allow starting a dirty degraded array.
15 Partial parity for a write operation is the XOR of stripe data chunks not
19 which chunk writes have completed. If one of the not modified data disks of
23 the array. Because of this, using write-intent bitmap and PPL together is not
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
37 performed for this stripe (parity is not updated). So it is possible to have
46 are not likely due to high risk of multiple disks failure. Such restriction
[all …]
|
| /Documentation/arm64/ |
| D | acpi_object_usage.rst | 24 - Not supported: BOOT, DBGP, DMAR, ETDT, HPET, IBFT, IVRS, LPIT,
41 Microsoft only table, will not be supported.
47 Optional, not currently supported, with no real use-case for an
54 Optional, not currently supported, and not recommended until such
62 Optional, not currently supported.
75 Microsoft only table, will not be supported.
91 x86 only table, will not be supported.
97 Optional, not currently supported.
103 Optional, not currently supported, but could be used on ARM if and
114 if it had actually occurred. However, this table should not be
[all …]
|
| /Documentation/hwmon/ |
| D | submitting-patches.rst | 23 * Please use the standard multi-line comment style. Do not mix C and C++
33 * Please test your patch thoroughly. We are not your test group.
34 Sometimes a patch can not or not completely be tested because of missing
36 architecture. If run-time testing was not achieved, it should be written
61 * Running your patch or driver file(s) through checkpatch does not mean its
63 through Lindent. Lindent is not perfect, and you may have to do some minor
80 * Avoid macros to generate groups of sensor attributes. It not only confuses
88 * Limit the number of kernel log messages. In general, your driver should not
91 that kernel error log messages not only fill up the kernel log, but also are
97 If a function is not supported by devres, consider using devm_add_action().
[all …]
|
| /Documentation/filesystems/spufs/ |
| D | spu_create.rst | 33 other operations are not defined on it. When it is closed, all associ-
64 The current user does not have write access on the spufs mount
69 EFAULT pathname is not a valid string pointer in the current address
72 EINVAL pathname is not a directory in the spufs mount point.
83 ENOENT Part of pathname could not be resolved.
85 ENOMEM The kernel could not allocate all resources required.
87 ENOSPC There are not enough SPU resources available to create a new
91 ENOSYS the functionality is not provided by the current system, because
92 either the hardware does not provide SPUs or the spufs module is
93 not loaded.
[all …]
|
| D | spu_run.rst | 32 not return while the SPU is still running. If there is a need to exe-
95 EBADF fd is not a valid file descriptor.
97 EFAULT npc is not a valid pointer or status is neither NULL nor a valid
103 EINVAL fd is not a file descriptor returned from spu_create(2).
108 ENOSYS the functionality is not provided by the current system, because
109 either the hardware does not provide SPUs or the spufs module is
110 not loaded.
116 abstract interface to SPUs, not to be used from regular applications.
124 ture. Programs using this system call are not portable.
129 The code does not yet fully implement all features lined out here.
|
| /Documentation/admin-guide/ |
| D | sysfs-rules.rst | 6 by the kernel developers that the Linux kernel does not provide a stable
8 may not be stable across kernel releases.
21 - Do not use libsysfs
22 It makes assumptions about sysfs which are not true. Its API does not
24 implementation details in its own API. Therefore it is not better than
26 Also, it is not actively maintained, in the sense of reflecting the
33 system configuration bug you should not try to solve. For test cases,
36 to mount it, if you are not an early boot script.
42 kernel implementation details which should not be expected by
80 - devices which do not have "driver"-link just do not have a
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | func-write.rst | 41 ``buf``. When the hardware outputs are not active yet, this function
45 When the application does not provide more data in time, the previous
47 Sliced Teletext or Closed Caption data is not repeated, the driver
64 ``fd`` is not a valid file descriptor or is not open for writing.
67 The driver does not support multiple write streams and the device is
80 The :c:func:`write()` function is not supported by this driver,
81 not on this device, or generally not on this type of device.
|
| /Documentation/fb/ |
| D | matroxfb.rst | 20 * graphic mode is slower than text mode... but you should not notice
34 box) and matroxfb (for graphics mode). You should not compile-in vesafb
99 head, not even talking about second). Running XFree86 4.x accelerated mga
100 driver is possible, but you must not enable DRI - if you do, resolution and
113 problem and not mine, but I'm not sure.
129 disabled do not load driver; you can use also `off`, but `disabled`
134 noaccel do not use acceleration engine. It does not work on Alphas.
142 not comply to PCI 2.1 specs (it will not guarantee that every
145 novga disables VGA I/O ports. It is default if BIOS did not enable
146 device. You should not use this option, some boards then do not
[all …]
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | max6697.txt | 21 Set to disable SMBus timeout. If not specified, SMBus timeout will be
25 Extended temperature will be disabled if not specified.
29 Beta compensation will be disabled if not specified.
33 If not specified, alert will be enabled for all channels.
38 If not specified, over-temperature reporting will be enabled for all
46 If not specified, resistance cancellation will be disabled for all
52 Transistor ideality will be initialized to default (1.008) if not
|
| /Documentation/infiniband/ |
| D | core_locking.rst | 26 which may not sleep and must be callable from any context.
57 The IB midlayer does not perform any serialization of function calls.
60 consumers are not required to perform any serialization. However,
64 information between different calls of ib_poll_cq() is not defined.
69 A low-level driver must not perform a callback directly from the
70 same callchain as an ib_device method call. For example, it is not
77 completion event handlers for the same CQ are not called
80 following situation is not allowed::
94 callbacks run is not defined. Depending on the low-level driver, it
96 Upper level protocol consumers may not sleep in a callback.
[all …]
|
| /Documentation/networking/ |
| D | msg_zerocopy.rst | 21 Copy avoidance is not a free lunch. As implemented, with page pinning,
30 is not affected, but a buggy program can possibly corrupt its own data
34 Converting an existing application to MSG_ZEROCOPY is not always as
60 avoidance, but not the only one.
86 the socket option was not set, the socket exceeds its optmem limit or
109 counter is not incremented on failure or if called with length zero.
110 The counter counts system call invocations, not bytes. It wraps after
122 POLLERR in its output flags. That flag does not have to be set in the
139 efficient to not wait for notifications, but read without blocking
145 a zero error code, however, to not block send and recv calls.
[all …]
|
| /Documentation/userspace-api/media/ |
| D | gen-errors.rst | 30 - The file descriptor is not a valid.
38 ioctl must not be retried without performing another action to fix
54 - Device not found or was removed.
58 - There's not enough memory to handle the desired operation.
62 - The ioctl is not supported by the driver, actually meaning that
63 the required functionality is not available, or the file
64 descriptor is not for a media device.
90 #. This list is not exhaustive; ioctls may return other error codes.
|
| /Documentation/userspace-api/ |
| D | no_new_privs.rst | 6 its parent did not have. The most obvious examples are setuid/setgid
26 promises not to grant the privilege to do anything that could not have
28 bits will no longer change the uid or gid; file capabilities will not
29 add to the permitted set, and LSMs will not relax constraints after
36 Be careful, though: LSMs might also not tighten constraints on exec
41 Note that ``no_new_privs`` does not prevent privilege changes that do not
|
| /Documentation/driver-api/gpio/ |
| D | using-gpio.rst | 6 as such are normally not user facing abstractions. The most obvious, natural
25 of specialized equipment that is not produced by the numbers, requiring
27 software-hardware interface to be set up. They should not have a natural fit
28 to any existing kernel subsystem and not be a good fit for an operating system,
29 because of not being reusable or abstract enough, or involving a lot of non
36 Do not under any circumstances abuse the GPIO userspace ABI to cut corners in
37 any product development projects. If you use it for prototyping, then do not
38 productify the prototype: rewrite it using proper kernel drivers. Do not under
|
| /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
19 the same code does not have to be reproduced each time. This also means that
85 not send a heartbeat request if WDOG_ACTIVE is set.
91 'timeout'. Not used if max_hw_heartbeat_ms is non-zero.
94 if the hardware can not tolerate lower intervals between heartbeats.
99 seconds. max_hw_heartbeat_ms must be set if a driver does not implement
150 Not all watchdog timer hardware supports the same functionality. That's why
158 Some watchdog timer hardware can only be started and not be stopped. A
159 driver supporting such hardware does not have to implement the stop routine.
[all …]
|
| /Documentation/features/scripts/ |
| D | features-refresh.sh | 10 # be either the empty string (for 'nop') or "not" (the logical
11 # negation operator '!'); other operators are not supported.
16 O="not"
25 # the case 'O = ""' and the case 'O = "not"'. E.g., F may be
30 # 2) K does not exist (e.g., it was renamed/mis-typed);
32 # [case 'O = "not"']
54 printf "WARNING: '%s' is not a valid Kconfig\n" "$F"
73 # - ("not", K) is 'supported by a given arch', if there is
77 # default to 'not yet supported'.
84 elif [ "$O" = "not" ] && [ -z "$K_GREP" ]; then
|
| /Documentation/process/ |
| D | management-style.rst | 13 simple coding style rules, so this document may or may not have anything
15 might not actually be true. You'll have to decide for yourself.
18 lead persons, not the people who do traditional management inside
20 budget of your group, you're almost certainly not a kernel manager.
21 These suggestions may or may not apply to you.
24 People", and NOT read it. Burn it, it's a great symbolic gesture.
26 .. [#f1] This document does so not so much by answering the question, but by
39 manager must be to make it. That's very deep and obvious, but it's not
46 you for a technical decision, you're screwed. You're clearly not
77 fairly easy to backtrack. Since you're not going to be able to waste
[all …]
|
| /Documentation/userspace-api/ioctl/ |
| D | cdrom.rst | 88 Individual drivers may return error codes not listed here.
114 - ENOSYS cd drive not audio-capable.
135 - ENOSYS cd drive not audio-capable.
159 - ENOSYS cd drive not audio-capable.
190 - ENOSYS cd drive not audio-capable.
219 - ENOSYS cd drive not audio-capable.
244 - ENOSYS cd drive not audio-capable.
245 - EINVAL entry.cdte_format not CDROM_MSF or CDROM_LBA
274 - ENOSYS cd drive not audio-capable.
299 - ENOSYS cd drive not audio-capable.
[all …]
|
| /Documentation/driver-api/serial/ |
| D | driver.rst | 7 driver. It is not complete, any questions you have should be directed to
74 If the port does not support this operation, then it should
81 This call must not sleep
102 This call must not sleep
106 of the outputs should not be returned, since the core keeps
115 the port does not support CTS, DCD or DSR, the driver should
117 not available, the signal should not be indicated as active.
123 This call must not sleep
137 This call must not sleep
146 This call must not sleep
[all …]
|
| /Documentation/x86/ |
| D | amd-memory-encryption.rst | 32 so that the PGD is encrypted, but not set the encryption bit in the PGD entry
33 for a PUD which results in the PUD pointed to by that entry to not be
53 system physical addresses, not guest physical
67 Bit[0] 0 = memory encryption is not active
72 CPUID information above) will not conflict with the address space resource
73 requirements for the system. If this bit is not set upon Linux startup then
74 Linux itself will not set it and memory encryption will not be possible.
91 not be necessary to activate the Linux memory encryption support. If the BIOS
95 not enable SME, then Linux will not be able to activate memory encryption, even
|
| D | cpuinfo.rst | 22 If the expected flag does not appear in /proc/cpuinfo, things are murkier.
24 how to enable it, which is not always easy. There are several factors that
26 is missing in hardware, platform firmware did not enable it, the feature is
28 not support the feature and thus has not enabled it. In general, /proc/cpuinfo
53 The intent of scattering CPUID leaves is to not bloat struct
58 memory is not trivial.
72 These flags do not represent hardware features. Instead, they represent a
104 c: The naming override can be "", which means it will not appear in /proc/cpuinfo.
106 The feature shall be omitted from /proc/cpuinfo if it does not make sense for
110 with "". Its flag will not appear in /proc/cpuinfo.
[all …]
|
| /Documentation/filesystems/ |
| D | overlayfs.rst | 20 appear in the filesystem do not always appear to belong to that filesystem.
30 tools ignore these values and will not be affected.
39 On 64bit systems, even if all overlay layers are not on the same
69 | Layers not | N | Y | Y | N | N | Y | N | Y |
101 not need to be writable. The lower filesystem can even be another
104 must provide valid d_type in readdir responses, so NFS is not suitable.
147 In the case where caller MAC or DAC credentials do not overlap, a
151 does not. Several unintended side effects will occur though. The
152 caller without certain key capabilities or lower privilege will not
155 a directory entry is spotty as a result of the cache mechanism not
[all …]
|
| /Documentation/scsi/ |
| D | st.rst | 17 The driver is generic, i.e., it does not contain any code tailored
37 does not perform auto-detection well enough and there is a single
40 or not :-).
55 over some of the buffering parameters not directly accessible to the
64 supported devices. The Linux SCSI tape driver does not contain such
65 tables (and will not do that in future). Instead of that, a utility
82 be a multiple of the block size. This is not required when reading but
102 operation is MTWEOFI, close() does not write a filemark. This can be used if
112 drive is not ready. If O_NONBLOCK is not used, the driver waits for
113 the drive to become ready. If this does not happen in ST_BLOCK_SECONDS
[all …]
|