Searched full:may (Results 1 – 25 of 6744) sorted by relevance
12345678910>>...270
| /Linux-v6.6/Documentation/ABI/testing/ |
| D | sysfs-class-usb_power_delivery | 2 Date: May 2022
8 Date: May 2022
15 Date: May 2022
24 Date: May 2022
38 Date: May 2022
52 Date: May 2022
66 Date: May 2022
73 Date: May 2022
91 Date: May 2022
100 Date: May 2022
[all …]
|
| D | sysfs-class-net-cdc_ncm | 2 Date: May 2014
42 Date: May 2014
58 Date: May 2014
70 Date: May 2014
90 Date: May 2014
99 Date: May 2014
106 Date: May 2014
113 Date: May 2014
122 Date: May 2014
130 Date: May 2014
[all …]
|
| D | sysfs-class-pwm | 2 Date: May 2013
11 Date: May 2013
20 Date: May 2013
27 Date: May 2013
35 Date: May 2013
42 Date: May 2013
51 Date: May 2013
58 Date: May 2013
65 Date: May 2013
73 Date: May 2013
|
| D | sysfs-driver-chromeos-acpi | 3 Date: May 2022
15 Date: May 2022
29 Date: May 2022
45 Date: May 2022
53 Date: May 2022
61 Date: May 2022
69 Date: May 2022
84 Date: May 2022
96 Date: May 2022
104 Date: May 2022
[all …]
|
| D | sysfs-kernel-slab | 2 Date: May 2007
9 files may be modified to change the behavior of the cache (and
14 Date: May 2007
23 Date: May 2007
32 Date: May 2007
100 Date: May 2007
110 Date: May 2007
132 Date: May 2007
195 Date: May 2007
215 Date: May 2007
[all …]
|
| D | sysfs-bus-pci-devices-aer_stats | 6 Note that this may mean that if an endpoint is causing problems, the AER
7 counters may increment at its link partner (e.g. root port) because the
8 errors may be "seen" / reported by the link partner and not the
9 problematic endpoint itself (which may report all counters as 0 as it never
17 PCI device using ERR_COR. Note that since multiple errors may
19 TOTAL_ERR_COR at the end of the file may not match the actual
38 PCI device using ERR_FATAL. Note that since multiple errors may
40 TOTAL_ERR_FATAL at the end of the file may not match the actual
69 may be reported using a single ERR_FATAL message, thus
70 TOTAL_ERR_NONFATAL at the end of the file may not match the
|
| /Linux-v6.6/Documentation/virt/kvm/x86/ |
| D | timekeeping.rst | 31 timekeeping which may be difficult to find elsewhere, specifically,
279 the APIC CPU-local memory-mapped hardware. Beware that CPU errata may affect
280 the use of the APIC and that workarounds may be required. In addition, some of
283 functionality that may be more computationally expensive to implement.
297 systems designated as legacy free may support only the HPET as a hardware timer
317 timing chips built into the cards which may have registers which are accessible
360 platforms, the TSCs of different CPUs may start at different times depending
364 The BIOS may attempt to resynchronize the TSCs during the poweron process and
365 the operating system or other system software may attempt to do this as well.
367 write the full 64-bits of the TSC, it may be impossible to match the TSC in
[all …]
|
| /Linux-v6.6/Documentation/livepatch/ |
| D | reliable-stacktrace.rst | 15 functions may have live state and therefore may not be safe to patch. One way
18 Existing stacktrace code may not always give an accurate picture of all
35 * The trace includes all functions that the task may be returned to, and the
56 architectures may need to verify that code has been compiled in a manner
57 expected by the unwinder. For example, an unwinder may expect that
63 In some cases, an unwinder may require metadata to correctly unwind.
78 Unwinding may terminate early for a number of reasons, including:
102 manipulating a frame pointer), but there can be code which may not follow these
103 conventions and may require special handling in the unwinder, e.g.
124 There are several ways an architecture may identify kernel code which is deemed
[all …]
|
| /Linux-v6.6/Documentation/security/ |
| D | credentials.rst | 17 Objects are things in the system that may be acted upon directly by
43 indicates the 'objective context' of that object. This may or may not be
58 Objects other than tasks may under some circumstances also be subjects.
59 For instance an open file may send SIGIO to a task using the UID and EUID
77 Linux has a number of actions available that a subject may perform upon an
98 file may supply more than one ACL.
102 'group' and 'other'), each of which may be granted certain privileges
112 The system as a whole may have one or more sets of rules that get
166 The inheritable capabilities are the ones that may get passed across
169 The bounding set limits the capabilities that may be inherited across
[all …]
|
| /Linux-v6.6/drivers/gpu/drm/i915/ |
| D | Kconfig.profile | 13 May be 0 to disable the timeout.
24 May be 0 to disable the timeout, and rely on the foreign fence being
38 May be 0 to disable the extra delay and solely use the device level
52 May be 0 to disable heartbeats and therefore disable automatic GPU
67 May be 0 to disable the timeout.
69 The compiled in default may get overridden at driver probe time on
86 May be 0 to disable the timeout.
88 The compiled in default may get overridden at driver probe time on
97 we may spend some time polling for its completion. As the IRQ may
105 May be 0 to disable the initial spin. In practice, we estimate
[all …]
|
| D | Kconfig.debug | 4 # As this may inadvertently break the build, only allow the user
45 Choose this option to turn on extra driver debugging that may affect
71 paths that may slow the system down and if hit hang the machine.
84 failures. However, more casual testers may not want to trigger
97 Enable additional logging that may help track down the cause of
111 ordinary tests, but may be vital for post-mortem debugging when
125 ordinary tests, but may be vital for post-mortem debugging when
138 Choose this option to turn on extra driver debugging that may affect
150 Choose this option to turn on extra driver debugging that may affect
163 Choose this option to turn on extra driver debugging that may affect
[all …]
|
| /Linux-v6.6/LICENSES/deprecated/ |
| D | GFDL-1.2 | 76 textbook of mathematics, a Secondary Section may not explain any
86 allowed to be designated as Invariant. The Document may contain zero
92 the Document is released under this License. A Front-Cover Text may
93 be at most 5 words, and a Back-Cover Text may be at most 25 words.
134 The Document may include Warranty Disclaimers next to the notice which
138 implication that these Warranty Disclaimers may have is void and has
144 You may copy and distribute the Document in any medium, either
148 conditions whatsoever to those of this License. You may not use
150 copying of the copies you make or distribute. However, you may accept
154 You may also lend copies, under the same conditions stated above, and
[all …]
|
| D | GFDL-1.1 | 73 textbook of mathematics, a Secondary Section may not explain any
119 You may copy and distribute the Document in any medium, either
123 conditions whatsoever to those of this License. You may not use
125 copying of the copies you make or distribute. However, you may accept
129 You may also lend copies, under the same conditions stated above, and
130 you may publicly display copies.
142 visible. You may add other material on the covers in addition.
173 You may copy and distribute a Modified Version of the Document under
183 of the Document). You may use the same title as a previous version
210 it was based on. These may be placed in the "History" section.
[all …]
|
| D | GPL-1.0 | 66 contains a notice placed by the copyright holder saying it may be
73 1. You may copy and distribute verbatim copies of the Program's source
79 along with the Program. You may charge a fee for the physical act of
82 2. You may modify your copy or copies of the Program or any portion of
93 that you may choose to grant warranty protection to some or all
101 warranty) and that users may redistribute the program under these
105 d) You may charge a fee for the physical act of transferring a
106 copy, and you may at your option offer warranty protection in
113 3. You may copy and distribute the Program (or a portion or derivative of
128 corresponding source code may be obtained. (This alternative is
[all …]
|
| /Linux-v6.6/drivers/atm/ |
| D | Kconfig | 61 Note that extended debugging may create certain race conditions
73 chipsets. However, in some cases, large bursts may overrun buffers
80 may increase the cost of setting up a transfer such that the
92 Burst sixteen words at once in the send direction. This may work
106 Burst four words at once in the send direction. You may want to try
108 may or may not improve throughput.
114 Burst two words at once in the send direction. You may want to try
116 are also set may or may not improve throughput.
122 Burst sixteen words at once in the receive direction. This may work
129 Burst eight words at once in the receive direction. This may work
[all …]
|
| /Linux-v6.6/drivers/block/drbd/ |
| D | drbd_req.h | 31 * There are quite a few things that may happen to a drbd request
42 * It may be identified as a concurrent (write) request
45 * It may me handed over to the local disk subsystem.
46 * It may be completed by the local disk subsystem,
49 * it may be retried remotely.
51 * It may be queued for sending.
52 * It may be handed over to the network stack,
53 * which may fail.
54 * It may be acknowledged by the "peer" according to the wire_protocol in use.
55 * this may be a negative ack.
[all …]
|
| /Linux-v6.6/Documentation/userspace-api/media/v4l/ |
| D | dev-encoder.rst | 25 2. The meaning of words "must", "may", "should", etc. is as per `RFC
30 4. :c:func:`VIDIOC_G_EXT_CTRLS` and :c:func:`VIDIOC_S_EXT_CTRLS` may be used
34 5. Single-planar API (see :ref:`planar-apis`) and applicable structures may be
88 client may call :c:func:`VIDIOC_ENUM_FMT` on ``CAPTURE``.
93 2. To enumerate the set of supported raw formats, the client may call
103 3. The client may use :c:func:`VIDIOC_ENUM_FRAMESIZES` to detect supported
116 4. The client may use :c:func:`VIDIOC_ENUM_FRAMEINTERVALS` to detect supported
137 ``CAPTURE``, if applicable, may be queried using their respective controls
140 6. Any additional encoder capabilities may be discovered by querying
157 desired size of ``CAPTURE`` buffers; the encoder may adjust it to
[all …]
|
| D | dev-decoder.rst | 25 2. The meaning of words "must", "may", "should", etc. is as per `RFC
30 4. :c:func:`VIDIOC_G_EXT_CTRLS` and :c:func:`VIDIOC_S_EXT_CTRLS` may be used
34 5. Single-planar API (see :ref:`planar-apis`) and applicable structures may be
82 the order in which frames are decoded; may differ from display order if the
130 a point in the bytestream from which decoding may start/continue, without
218 client may call :c:func:`VIDIOC_ENUM_FMT` on ``OUTPUT``.
227 2. To enumerate the set of supported raw formats, the client may call
237 3. The client may use :c:func:`VIDIOC_ENUM_FRAMESIZES` to detect supported
251 ``OUTPUT``, if applicable, may be queried using their respective controls
274 desired size of ``OUTPUT`` buffers; the decoder may adjust it to
[all …]
|
| /Linux-v6.6/arch/m68k/ifpsp060/ |
| D | fpsp.doc | 206 may exit through _060_real_inex <---|
208 may exit through _060_real_ovfl <---|
210 may exit through _060_fpsp_done <---|
218 may exit through _060_real_inex <---|
220 may exit through _060_real_unfl <---|
222 may exit through _060_fpsp_done <---|
253 |----> may exit through _060_real_trace
255 |----> may exit through _060_real_trap
257 |----> may exit through _060_real_bsun
259 |----> may exit through _060_fpsp_done
[all …]
|
| /Linux-v6.6/Documentation/userspace-api/media/ |
| D | fdl-appendix.rst | 67 may not explain any mathematics.) The relationship could be a matter of
127 You may copy and distribute the :ref:`Document <fdl-document>` in any
131 you add no other conditions whatsoever to those of this License. You may
133 copying of the copies you make or distribute. However, you may accept
138 You may also lend copies, under the same conditions stated above, and
139 you may publicly display copies.
154 with all words of the title equally prominent and visible. You may add
191 You may copy and distribute a :ref:`Modified Version <fdl-modified>`
205 the Document). You may use the same title as a previous version if
259 versions it was based on. These may be placed in the "History"
[all …]
|
| /Linux-v6.6/include/linux/ |
| D | async.h | 49 * Returns an async_cookie_t that may be used for checkpointing later.
50 * Note: This function may be called from atomic or non-atomic contexts.
63 * Returns an async_cookie_t that may be used for checkpointing later.
64 * @domain may be used in the async_synchronize_*_domain() functions to
66 * Note: This function may be called from atomic or non-atomic contexts.
80 * Returns an async_cookie_t that may be used for checkpointing later.
85 * Note: This function may be called from atomic or non-atomic contexts.
99 * Returns an async_cookie_t that may be used for checkpointing later.
104 * @domain may be used in the async_synchronize_*_domain() functions to
106 * Note: This function may be called from atomic or non-atomic contexts.
|
| /Linux-v6.6/Documentation/arch/sparc/oradax/ |
| D | dax-hv-api.txt | 14 …These APIs may only be provided by certain platforms, and may not be available to all virtual mach…
15 …even on supported platforms. Restrictions on the use of these APIs may be imposed in order to supp…
20 …high speed processoring of database-centric operations. The coprocessors may support one or more of
22 functionality offered may vary by virtual machine implementation.
32 …Guest software may implement a software timeout on CCB operations, and if the timeout is exceeded,…
33 …operation may be cancelled or killed via the ccb_kill API function. It is recommended for guest so…
34 …to implement a software timeout to account for certain RAS errors which may result in lost CCBs. I…
36 …killing it in order to determine if the CCB is still in queue, or may have been lost due to a RAS …
38 …There is no fixed limit on the number of outstanding CCBs guest software may have queued in the vi…
49 The query functionality may vary based on the compatibility property of the virtual device:
[all …]
|
| /Linux-v6.6/Documentation/firmware-guide/acpi/ |
| D | DSD-properties-rules.rst | 12 namespace. In principle, the format of the data may be arbitrary, but it has to
28 It also may be regarded as the definition of a key and the associated data type
45 Property sets may be hierarchical. That is, a property set may contain
46 multiple property subsets that each may contain property subsets of its
66 principle, the property set may still not be regarded as a valid one.
68 For example, that applies to device properties which may cause kernel code
71 particular, that may happen if the kernel code uses device properties to
77 In all cases in which kernel code may do something that will confuse AML as a
90 avoided. For this reason, it may not be possible to make _DSD return a property
92 sake of code re-use, it may make sense to provide as much of the configuration
|
| /Linux-v6.6/Documentation/admin-guide/mm/ |
| D | numaperf.rst | 8 Some platforms may have multiple types of memory attached to a compute
9 node. These disparate memory ranges may share some characteristics, such
10 as CPU cache coherence, but may have different performance. For example,
15 characteristics. Some memory may share the same node as a CPU, and others
17 CPUs, they may still be local to one or more compute nodes relative to
35 When multiple memory initiators exist, they may not all have the same
37 pair may be organized into different ranked access classes to represent
40 the highest access class, 0. Any given target may have one or more
41 local initiators, and any given initiator may have multiple local
54 A memory initiator may have multiple memory targets in the same access
[all …]
|
| /Linux-v6.6/Documentation/driver-api/ |
| D | regulator.rst | 32 The regulator API uses a number of terms which may not be familiar:
43 may either be static, requiring only a fixed supply, or dynamic,
83 Note that since multiple consumers may be using a regulator and machine
84 constraints may not allow the regulator to be disabled there is no
87 drivers should assume that the regulator may be enabled at all times.
92 Some consumer devices may need to be able to dynamically configure their
93 supplies. For example, MMC drivers may need to select the correct
94 operating voltage for their cards. This may be done while the regulator
109 Callbacks may also be registered for events such as regulation failures.
141 and the parameters that may be set. This is required since generally
[all …]
|
12345678910>>...270
