| /linux/Documentation/ABI/testing/ |
| H A 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 …]
|
| H A 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 …]
|
| H A 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
|
| H A 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 …]
|
| H A D | sysfs-bus-pci-devices-aer | 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
[all …]
|
| H A D | debugfs-pcie-ptm | 2 Date: May 2025
9 Date: May 2025
16 Date: May 2025
23 Date: May 2025
30 Date: May 2025
37 Date: May 2025
44 Date: May 2025
58 Date: May 2025
|
| H A 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
101 Date: May 2007
111 Date: May 2007
133 Date: May 2007
196 Date: May 2007
216 Date: May 2007
[all …]
|
| /linux/Documentation/virt/kvm/x86/ |
| H A 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/Documentation/livepatch/ |
| H A 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/drivers/gpu/drm/i915/ |
| H A 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 …]
|
| /linux/LICENSES/deprecated/ |
| H A 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 …]
|
| H A 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 …]
|
| H A D | GPL-1.0 | 67 contains a notice placed by the copyright holder saying it may be
74 1. You may copy and distribute verbatim copies of the Program's source
80 along with the Program. You may charge a fee for the physical act of
83 2. You may modify your copy or copies of the Program or any portion of
94 that you may choose to grant warranty protection to some or all
102 warranty) and that users may redistribute the program under these
106 d) You may charge a fee for the physical act of transferring a
107 copy, and you may at your option offer warranty protection in
114 3. You may copy and distribute the Program (or a portion or derivative of
129 corresponding source code may be obtained. (This alternative is
[all …]
|
| /linux/drivers/block/drbd/ |
| H A 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/Documentation/userspace-api/media/v4l/ |
| H A D | dev-encoder.rst | 26 2. The meaning of words "must", "may", "should", etc. is as per `RFC
31 4. :c:func:`VIDIOC_G_EXT_CTRLS` and :c:func:`VIDIOC_S_EXT_CTRLS` may be used
35 5. Single-planar API (see :ref:`planar-apis`) and applicable structures may be
89 client may call :c:func:`VIDIOC_ENUM_FMT` on ``CAPTURE``.
94 2. To enumerate the set of supported raw formats, the client may call
104 3. The client may use :c:func:`VIDIOC_ENUM_FRAMESIZES` to detect supported
117 4. The client may use :c:func:`VIDIOC_ENUM_FRAMEINTERVALS` to detect supported
138 ``CAPTURE``, if applicable, may be queried using their respective controls
141 6. Any additional encoder capabilities may be discovered by querying
158 desired size of ``CAPTURE`` buffers; the encoder may adjust it to
[all …]
|
| /linux/arch/m68k/ifpsp060/ |
| H A 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/include/linux/ |
| H A 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.
101 * Returns an async_cookie_t that may be used for checkpointing later.
106 * @domain may be used in the async_synchronize_*_domain() functions to
108 * Note: This function may be called from atomic or non-atomic contexts.
|
| /linux/Documentation/userspace-api/media/ |
| H A 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/Documentation/userspace-api/ |
| H A D | dma-buf-alloc-exchange.rst | 25 Conceptually a two-dimensional array of pixels. The pixels may be stored
42 in bytes and at least one handle in some API. May contain one or more
51 more color channels values, e.g. R, G and B, or Y, Cb and Cr. May also
56 of a pixel or an image. The data for one pixel may be spread over several
134 Some modifiers may modify the number of planes required for an image; for
162 calculations. This may be used to combine multiple planes into a single memory
163 buffer; for example, ``DRM_FORMAT_NV12`` may be stored in a single memory buffer
170 with dimensions of 1000x1000 may have been allocated as if it were 1024x1000, in
176 Buffers may also be padded further in the y dimension, simply by allocating a
238 acceptable modifiers, and the buffer's width and height. Each API may extend
[all …]
|
| /linux/Documentation/driver-api/ |
| H A 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 …]
|
| /linux/Documentation/admin-guide/sysctl/ |
| H A D | user.rst | 42 user namespace may create.
48 user namespace may create.
54 user namespace may create.
60 current user namespace may create.
66 user namespace may create.
72 user namespace may create.
78 user namespace may create.
84 user namespace may create.
|
| /linux/Documentation/admin-guide/mm/ |
| H A 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/Documentation/devicetree/bindings/pinctrl/ |
| H A D | pinctrl-bindings.txt | 24 Note that pin controllers themselves may also be client devices of themselves.
25 For example, a pin controller may set up its own "active" state when the
37 property exists to define the pin configuration. Each state may also be
50 entries may exist in this list so that multiple pin
51 controllers may be configured, or so that a state may be built
57 In some cases, it may be useful to define a state, but for it
58 to be empty. This may be required when a common IP block is
62 exist, they must still be defined, but may be left empty.
|
| /linux/include/uapi/linux/ |
| H A D | falloc.h | 20 * Different filesystems may implement different limitations on the
22 * filesystem block size boundaries, but this boundary may be larger or
36 * unwritten extents - even though file system may choose to zero out the
52 * Different filesystems may implement different limitations on the granularity
54 * boundaries, but this boundary may be larger or smaller depending on
69 * Different filesystems may implement different limitations on the
71 * block size boundaries, but this boundary may be larger or smaller
89 * Different filesystems may implement different limitations on the
92 * may not physically write zeros to the media.
|
| /linux/include/xen/interface/ |
| H A D | event_channel.h | 24 * 2. <rdom> may be DOMID_SELF, allowing loopback connections.
41 * 2. <remote_dom> may be DOMID_SELF, allowing loopback connections.
56 * 1. A virtual IRQ may be bound to at most one event channel per vcpu.
58 * may not be changed.
72 * 1. A physical IRQ may be bound to at most one event channel per domain.
73 * 2. Only a sufficiently-privileged domain may bind to a physical IRQ.
89 * may not be changed.
123 * 1. <dom> may be specified as DOMID_SELF.
124 * 2. Only a sufficiently-privileged domain may obtain the status of an event
184 * 1. <dom> may be specified as DOMID_SELF.
[all …]
|