| /linux/tools/perf/pmu-events/arch/x86/lunarlake/ |
| H A D | memory.json | 11 …atch to completion is greater than 1024 cycles. Reported latency may be longer than just the memo…
25 …patch to completion is greater than 128 cycles. Reported latency may be longer than just the memo…
39 …spatch to completion is greater than 16 cycles. Reported latency may be longer than just the memo…
53 …atch to completion is greater than 2048 cycles. Reported latency may be longer than just the memo…
67 …patch to completion is greater than 256 cycles. Reported latency may be longer than just the memo…
81 …spatch to completion is greater than 32 cycles. Reported latency may be longer than just the memo…
95 …ispatch to completion is greater than 4 cycles. Reported latency may be longer than just the memo…
109 …patch to completion is greater than 512 cycles. Reported latency may be longer than just the memo…
123 …spatch to completion is greater than 64 cycles. Reported latency may be longer than just the memo…
137 …ispatch to completion is greater than 8 cycles. Reported latency may be longer than just the memo…
|
| /linux/tools/perf/pmu-events/arch/x86/graniterapids/ |
| H A D | memory.json | 76 …atch to completion is greater than 1024 cycles. Reported latency may be longer than just the memo…
89 …patch to completion is greater than 128 cycles. Reported latency may be longer than just the memo…
102 …spatch to completion is greater than 16 cycles. Reported latency may be longer than just the memo…
115 …atch to completion is greater than 2048 cycles. Reported latency may be longer than just the memo…
128 …patch to completion is greater than 256 cycles. Reported latency may be longer than just the memo…
141 …spatch to completion is greater than 32 cycles. Reported latency may be longer than just the memo…
154 …ispatch to completion is greater than 4 cycles. Reported latency may be longer than just the memo…
167 …patch to completion is greater than 512 cycles. Reported latency may be longer than just the memo…
180 …spatch to completion is greater than 64 cycles. Reported latency may be longer than just the memo…
193 …ispatch to completion is greater than 8 cycles. Reported latency may be longer than just the memo…
|
| /linux/kernel/printk/ |
| H A D | nbcon.c | 125 * Only to be used when the console is not yet or no longer visible in the
181 * If the specified record no longer exists, the oldest available record in nbcon_seq_force()
199 * nbcon_seq_force() was used or the current context no longer owns the
327 * or this context is no longer the waiter.
333 * except when this context is no longer the waiter.
699 * When this function returns false then the calling context no longer owns
700 * the console and is no longer allowed to go forward. In this case it must
701 * back out immediately and carefully. The buffer content is also no longer
702 * trusted since it no longer belongs to the calling context.
742 * The calling context no longer owns the console so go back all the in nbcon_context_can_proceed()
[all …]
|
| /linux/tools/perf/pmu-events/arch/x86/tigerlake/ |
| H A D | memory.json | 29 …patch to completion is greater than 128 cycles. Reported latency may be longer than just the memo…
42 …spatch to completion is greater than 16 cycles. Reported latency may be longer than just the memo…
55 …patch to completion is greater than 256 cycles. Reported latency may be longer than just the memo…
68 …spatch to completion is greater than 32 cycles. Reported latency may be longer than just the memo…
81 …ispatch to completion is greater than 4 cycles. Reported latency may be longer than just the memo…
94 …patch to completion is greater than 512 cycles. Reported latency may be longer than just the memo…
107 …spatch to completion is greater than 64 cycles. Reported latency may be longer than just the memo…
120 …ispatch to completion is greater than 8 cycles. Reported latency may be longer than just the memo…
|
| /linux/tools/perf/pmu-events/arch/x86/meteorlake/ |
| H A D | memory.json | 147 …atch to completion is greater than 1024 cycles. Reported latency may be longer than just the memo…
161 …patch to completion is greater than 128 cycles. Reported latency may be longer than just the memo…
175 …spatch to completion is greater than 16 cycles. Reported latency may be longer than just the memo…
189 …atch to completion is greater than 2048 cycles. Reported latency may be longer than just the memo…
203 …patch to completion is greater than 256 cycles. Reported latency may be longer than just the memo…
217 …spatch to completion is greater than 32 cycles. Reported latency may be longer than just the memo…
231 …ispatch to completion is greater than 4 cycles. Reported latency may be longer than just the memo…
245 …patch to completion is greater than 512 cycles. Reported latency may be longer than just the memo…
259 …spatch to completion is greater than 64 cycles. Reported latency may be longer than just the memo…
273 …ispatch to completion is greater than 8 cycles. Reported latency may be longer than just the memo…
|
| /linux/Documentation/pcmcia/ |
| H A D | driver-changes.rst | 41 dev_info_t and a few other typedefs are removed. No longer use them
115 The irq_mask and irq_list parameters should no longer be used in
121 client->PendingEvents is no longer available.
127 * core functions no longer available (as of 2.6.11)
140 It is no longer necessary to iterate on the driver's internal
145 it no longer marks these resources busy. This means that driver
|
| /linux/tools/perf/pmu-events/arch/x86/alderlake/ |
| H A D | memory.json | 137 …atch to completion is greater than 1024 cycles. Reported latency may be longer than just the memo…
151 …patch to completion is greater than 128 cycles. Reported latency may be longer than just the memo…
165 …spatch to completion is greater than 16 cycles. Reported latency may be longer than just the memo…
179 …patch to completion is greater than 256 cycles. Reported latency may be longer than just the memo…
193 …spatch to completion is greater than 32 cycles. Reported latency may be longer than just the memo…
207 …ispatch to completion is greater than 4 cycles. Reported latency may be longer than just the memo…
221 …patch to completion is greater than 512 cycles. Reported latency may be longer than just the memo…
235 …spatch to completion is greater than 64 cycles. Reported latency may be longer than just the memo…
249 …ispatch to completion is greater than 8 cycles. Reported latency may be longer than just the memo…
|
| /linux/tools/perf/pmu-events/arch/x86/sapphirerapids/ |
| H A D | memory.json | 67 …atch to completion is greater than 1024 cycles. Reported latency may be longer than just the memo…
80 …patch to completion is greater than 128 cycles. Reported latency may be longer than just the memo…
93 …spatch to completion is greater than 16 cycles. Reported latency may be longer than just the memo…
106 …patch to completion is greater than 256 cycles. Reported latency may be longer than just the memo…
119 …spatch to completion is greater than 32 cycles. Reported latency may be longer than just the memo…
132 …ispatch to completion is greater than 4 cycles. Reported latency may be longer than just the memo…
145 …patch to completion is greater than 512 cycles. Reported latency may be longer than just the memo…
158 …spatch to completion is greater than 64 cycles. Reported latency may be longer than just the memo…
171 …ispatch to completion is greater than 8 cycles. Reported latency may be longer than just the memo…
|
| /linux/tools/perf/pmu-events/arch/x86/emeraldrapids/ |
| H A D | memory.json | 67 …atch to completion is greater than 1024 cycles. Reported latency may be longer than just the memo…
80 …patch to completion is greater than 128 cycles. Reported latency may be longer than just the memo…
93 …spatch to completion is greater than 16 cycles. Reported latency may be longer than just the memo…
106 …patch to completion is greater than 256 cycles. Reported latency may be longer than just the memo…
119 …spatch to completion is greater than 32 cycles. Reported latency may be longer than just the memo…
132 …ispatch to completion is greater than 4 cycles. Reported latency may be longer than just the memo…
145 …patch to completion is greater than 512 cycles. Reported latency may be longer than just the memo…
158 …spatch to completion is greater than 64 cycles. Reported latency may be longer than just the memo…
171 …ispatch to completion is greater than 8 cycles. Reported latency may be longer than just the memo…
|
| /linux/drivers/gpu/drm/i915/gt/ |
| H A D | intel_reset_types.h | 28 * #I915_WEDGED - If reset fails and we can no longer use the GPU,
34 * longer use the GPU - similar to #I915_WEDGED bit. The difference in
39 * use it to mark that the GPU is no longer available (and prevent
|
| H A D | intel_engine_heartbeat.c | 43 long longer; in next_heartbeat() local
50 longer = READ_ONCE(engine->props.preempt_timeout_ms) * 2; in next_heartbeat()
51 longer = intel_clamp_heartbeat_interval_ms(engine, longer); in next_heartbeat()
52 if (longer > delay) in next_heartbeat()
53 delay = longer; in next_heartbeat()
|
| /linux/include/uapi/linux/ |
| H A D | tty_flags.h | 12 * [x] in the bit comments indicates the flag is defunct and no longer used.
39 * WARNING: These flags are no longer used and have been superceded by the
50 #define ASYNCB_SHARE_IRQ 24 /* for multifunction cards, no longer used */
85 /* These flags are no longer used (and were always masked from userspace) */
|
| /linux/tools/perf/pmu-events/arch/x86/rocketlake/ |
| H A D | memory.json | 92 …patch to completion is greater than 128 cycles. Reported latency may be longer than just the memo…
105 …spatch to completion is greater than 16 cycles. Reported latency may be longer than just the memo…
118 …patch to completion is greater than 256 cycles. Reported latency may be longer than just the memo…
131 …spatch to completion is greater than 32 cycles. Reported latency may be longer than just the memo…
144 …ispatch to completion is greater than 4 cycles. Reported latency may be longer than just the memo…
157 …patch to completion is greater than 512 cycles. Reported latency may be longer than just the memo…
170 …spatch to completion is greater than 64 cycles. Reported latency may be longer than just the memo…
183 …ispatch to completion is greater than 8 cycles. Reported latency may be longer than just the memo…
|
| /linux/tools/perf/pmu-events/arch/x86/icelake/ |
| H A D | memory.json | 92 …patch to completion is greater than 128 cycles. Reported latency may be longer than just the memo…
105 …spatch to completion is greater than 16 cycles. Reported latency may be longer than just the memo…
118 …patch to completion is greater than 256 cycles. Reported latency may be longer than just the memo…
131 …spatch to completion is greater than 32 cycles. Reported latency may be longer than just the memo…
144 …ispatch to completion is greater than 4 cycles. Reported latency may be longer than just the memo…
157 …patch to completion is greater than 512 cycles. Reported latency may be longer than just the memo…
170 …spatch to completion is greater than 64 cycles. Reported latency may be longer than just the memo…
183 …ispatch to completion is greater than 8 cycles. Reported latency may be longer than just the memo…
|
| /linux/Documentation/hwmon/ |
| H A D | it87.rst | 34 Datasheet: Once publicly available at the ITE website, but no longer
42 Datasheet: Once publicly available at the ITE website, but no longer
50 Datasheet: Once publicly available at the ITE website, but no longer
58 Datasheet: Once publicly available at the ITE website, but no longer
170 Datasheet: No longer be available
222 longer supports this interface though, as it is slower and less reliable
|
| /linux/tools/perf/pmu-events/arch/x86/icelakex/ |
| H A D | memory.json | 29 …patch to completion is greater than 128 cycles. Reported latency may be longer than just the memo…
42 …spatch to completion is greater than 16 cycles. Reported latency may be longer than just the memo…
55 …patch to completion is greater than 256 cycles. Reported latency may be longer than just the memo…
68 …spatch to completion is greater than 32 cycles. Reported latency may be longer than just the memo…
81 …ispatch to completion is greater than 4 cycles. Reported latency may be longer than just the memo…
94 …patch to completion is greater than 512 cycles. Reported latency may be longer than just the memo…
107 …spatch to completion is greater than 64 cycles. Reported latency may be longer than just the memo…
120 …ispatch to completion is greater than 8 cycles. Reported latency may be longer than just the memo…
|
| /linux/Documentation/arch/x86/x86_64/ |
| H A D | fred.rst | 58 transient states due to %cr2 and/or %dr6, and it is no longer needed
65 FRED always restores the full value of %rsp, thus ESPFIX is no longer
80 longer needed when FRED is enabled, thus is disallowed (#UD).
|
| /linux/Documentation/gpu/ |
| H A D | tegra.rst | 79 display controller can no longer drive all of the outputs. While two of these
103 longer do and instead provide standard interfaces such as DSI and eDP/DP.
110 This interface is no longer available since Tegra124. It has been replaced by
171 longer needed, it can be closed using the ``DRM_IOCTL_TEGRA_CLOSE_CHANNEL``
|
| /linux/include/linux/soc/apple/ |
| H A D | sart.h | 47 * @paddr: Start address of the region no longer used for DMA
48 * @size: Size of the region no longer used for DMA.
|
| /linux/Documentation/livepatch/ |
| H A D | system-state.rst | 14 change the system behavior or state so that it is no longer safe to
139 not longer needed.
156 - Remove any not longer needed setting or data.
|
| /linux/net/core/ |
| H A D | request_sock.c | 45 * to NULL when a TFO socket no longer needs to access the request_sock.
60 * NULL since it's no longer needed. More importantly, "req->sk == NULL"
73 * decremented by this function when fastopen_rsk is no longer needed.
|
| /linux/sound/soc/intel/boards/ |
| H A D | sof_sdw_common.h | 39 /* Deprecated and no longer supported by the code */
45 /* Deprecated and no longer supported by the code */
|
| /linux/Documentation/userspace-api/media/cec/ |
| H A D | cec-pin-error-inj.rst | 63 # <op>[,<mode>] tx-long-bit <bit> make this bit longer than allowed
205 for longer than is strictly needed. Especially given how slow the bus is.
256 Make this bit period longer than is valid. The bit position cannot be
263 Even though this bit period is longer than is valid it is undefined what
281 Make this start bit period longer than is valid. Normally the period of
287 Even though this start bit period is longer than is valid it is undefined
|
| /linux/drivers/gpu/drm/nouveau/nvkm/engine/disp/ |
| H A D | hdmi.c | 20 * We presume that no valid frame is longer than 17 in pack_hdmi_infoframe()
22 * if it's longer. in pack_hdmi_infoframe()
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-platform-chipidea-usb-otg | 8 and to be 0 when the application no longer wants to use
40 bus as host, and is 0 when the application no longer wants to
|