| /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/hwmon/ |
| D | submitting-patches.rst | 22 * Please use the standard multi-line comment style. Do not mix C and C++
32 * Please test your patch thoroughly. We are not your test group.
33 Sometimes a patch can not or not completely be tested because of missing
35 architecture. If run-time testing was not achieved, it should be written
60 * Running your patch or driver file(s) through checkpatch does not mean its
62 through Lindent. Lindent is not perfect, and you may have to do some minor
79 * Avoid macros to generate groups of sensor attributes. It not only confuses
87 * Limit the number of kernel log messages. In general, your driver should not
90 that kernel error log messages not only fill up the kernel log, but also are
96 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/arch/arm64/ |
| D | acpi_object_usage.rst | 24 - Not supported: AEST, APMT, BOOT, DBGP, DMAR, ETDT, HPET, IVRS, LPIT,
62 Microsoft only table, will not be supported.
68 Optional, not currently supported, with no real use-case for an
82 Optional, not currently supported, and not recommended until such
90 Optional, not currently supported.
103 Microsoft only table, will not be supported.
119 x86 only table, will not be supported.
125 Optional, not currently supported.
131 Optional, not currently supported, but could be used on ARM if and
142 if it had actually occurred. However, this table should not be
[all …]
|
| D | cpu-hotplug.rst | 10 CPUs that were not available during boot to be added to the system later.
15 CPU Hotplug on physical systems - CPUs not present at boot
18 Physical systems need to mark a CPU that is ``possible`` but not ``present`` as
22 This is not supported.
24 In the arm64 world CPUs are not a single device but a slice of the system.
26 while the system is running, and ACPI is not able to sufficiently describe
31 not discoverable, and must be described by firmware.
36 can't describe whether the redistributor is accessible, only that it is not
42 CPU Hotplug on virtual systems - CPUs not enabled at boot
63 that firmware wishes to disable either from boot (or later) should not be
[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/dev-tools/ |
| D | ktap.rst | 61 While there are cases where the number of tests is not known in advance -- in
76 or "not ok", which indicates that the test case failed.
92 a directive it doesn't support, it should fall back to the "ok" / "not ok"
98 result line can be either "ok" or "not ok" if the SKIP directive is used)
99 - "TODO", which indicates that a test is not expected to pass at the moment,
105 case result line should be “not ok” if the TIMEOUT directive is used)
108 the test case result line should be “not ok” if the ERROR directive is used)
115 directive nor any diagnostic data do not need to include the "#" field
126 not ok 1 test_case_name
139 not ok 1 test # TIMEOUT 30 seconds
[all …]
|
| /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/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/rust/ |
| D | coding-guidelines.rst | 13 contributing from time to time to the kernel does not need to learn and
15 do not need to spend time pointing out style issues anymore, and thus
18 .. note:: Conventions on comments and documentation are not checked by
38 individual files, and does not require a kernel configuration. Sometimes it may
47 comments are, even though they will not be rendered. This improves consistency,
64 Comments should not be used for documentation purposes: comments are intended
65 for implementation details, not users. This distinction is useful even if the
97 ``// SAFETY:`` comments are not to be confused with the ``# Safety`` sections
108 Rust kernel code is not documented like C kernel code (i.e. via kernel-doc).
122 /// without checking that the value is not [`None`].
[all …]
|
| /Documentation/admin-guide/hw-vuln/ |
| D | indirect-target-selection.rst | 35 ICELAKE_X 06_6AH Not affected Affected
36 ICELAKE_D 06_6CH Not affected Affected
37 ICELAKE_L 06_7EH Not affected Affected
38 TIGERLAKE_L 06_8CH Not affected Affected
39 TIGERLAKE 06_8DH Not affected Affected
44 ROCKETLAKE 06_A7H Not affected Affected
53 - Intel Atom CPUs are not affected by ITS.
59 the mitigation is to not allow indirect branches in the lower half.
64 second half of the cacheline. Not all retpoline sites are patched to thunks, if
79 All vulnerable RETs are replaced with a static thunk, they do not use dynamic
[all …]
|
| /Documentation/arch/x86/ |
| D | mds.rst | 22 not possible. But if a thread enters or exits a sleep state the store
83 VERW can be avoided. If the CPU is not affected by L1TF then VERW needs to
90 This does not protect against cross Hyper-Thread attacks except for MSBDS
105 the microcode updated, but the hypervisor does not (yet) expose the
111 itself are not required because the necessary gadgets to expose the leaked
119 off Mitigation is disabled. Either the CPU is not affected or
125 vmwerv Mitigation is enabled. CPU is affected and MD_CLEAR is not
128 hypervisor does not expose MD_CLEAR in CPUID. It's a best
132 If the CPU is affected and mds=off is not supplied on the kernel command
143 on affected CPUs when the mitigation is not disabled on the kernel
[all …]
|
| /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/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/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/userspace-api/gpio/ |
| D | error-codes.rst | 25 - The file descriptor is not valid.
31 usage of a resource that was already allocated. The ioctl must not
47 - Device not found or was removed.
51 - There's not enough memory to handle the desired operation.
62 with a hardware device or requesting features that hardware does not
69 requested, but the line does not support interrupts.
73 #. This list is not exhaustive; ioctls may return other error codes.
|
| /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/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/userspace-api/ioctl/ |
| D | cdrom.rst | 91 Individual drivers may return error codes not listed here.
117 - ENOSYS cd drive not audio-capable.
138 - ENOSYS cd drive not audio-capable.
162 - ENOSYS cd drive not audio-capable.
193 - ENOSYS cd drive not audio-capable.
222 - ENOSYS cd drive not audio-capable.
247 - ENOSYS cd drive not audio-capable.
248 - EINVAL entry.cdte_format not CDROM_MSF or CDROM_LBA
277 - ENOSYS cd drive not audio-capable.
302 - ENOSYS cd drive not audio-capable.
[all …]
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | partition.yaml | 41 not be clobbered.
45 description: Do not unlock the partition at initialization time (not
72 the containing section but is not included in the entry, meaning that
74 must be a power of 2. If ‘align’ is not provided, no alignment is
87 bytes, set this to 64. While this does not affect the content of the
90 bytes, so may grow. If ‘align-size’ is not provided, no alignment is
103 regardless of where they start. This does not move the start of the
105 But there may be padding at the end. While this does not affect the
108 with the padding bytes, so may grow. If ‘align-end’ is not provided,
112 not:
|