| /Linux-v6.1/Documentation/ABI/testing/ |
| D | sysfs-bus-coresight-devices-trbe | 12 Description: (Read) Shows if TRBE updates in the memory are with access
13 and dirty flag updates as well. This value is fetched from
|
| D | sysfs-bus-counter | 124 Rising edges on signal A updates the respective count.
129 signal A updates the respective count; if the direction
131 updates the respective count. Quadrature encoding
136 signal B updates the respective count; if the direction
138 updates the respective count. Quadrature encoding
142 Any state transition on quadrature pair signal A updates
147 Any state transition on quadrature pair signal B updates
153 updates the respective count. Quadrature encoding
|
| /Linux-v6.1/drivers/gpu/drm/amd/amdgpu/ |
| D | amdgpu_ids.c | 264 uint64_t updates = amdgpu_vm_tlb_seq(vm); in amdgpu_vmid_grab_reserved() local
270 (*id)->flushed_updates < updates || in amdgpu_vmid_grab_reserved()
297 (*id)->flushed_updates = updates; in amdgpu_vmid_grab_reserved()
325 uint64_t updates = amdgpu_vm_tlb_seq(vm); in amdgpu_vmid_grab_used() local
346 if ((*id)->flushed_updates < updates) in amdgpu_vmid_grab_used()
359 (*id)->flushed_updates = updates; in amdgpu_vmid_grab_used()
|
| /Linux-v6.1/Documentation/RCU/ |
| D | arrayRCU.rst | 48 as updates are rare.
51 Why is it so important that updates be rare when using seqlock?
69 the remainder of the new, updates the ids->entries pointer to point to
160 Why is it so important that updates be rare when using seqlock?
162 The reason that it is important that updates be rare when
163 using seqlock is that frequent updates can livelock readers.
|
| D | checklist.rst | 32 for lockless updates. This does result in the mildly
34 rcu_read_unlock() are used to protect updates, however, this
45 c. restricting updates to a single task.
87 be running while updates are in progress. There are a number
106 c. Make updates appear atomic to readers. For example,
107 pointer updates to properly aligned fields will
115 d. Carefully order the updates and the reads so that
214 Restructure your code so that it batches the updates, allowing
269 primitive will correspondingly delay updates. In contrast,
280 limit on this number, stalling updates as needed to allow
[all …]
|
| /Linux-v6.1/Documentation/driver-api/firmware/ |
| D | fw_search_path.rst | 9 * /lib/firmware/updates/UTS_RELEASE/
10 * /lib/firmware/updates/
|
| /Linux-v6.1/drivers/net/ |
| D | LICENSE.SRC | 14 on an "as-is" basis. No further updates to this software should be
15 expected. Although updates may occur, no commitment exists.
|
| /Linux-v6.1/Documentation/core-api/ |
| D | entry.rst | 4 All transitions between execution domains require state updates which are
5 subject to strict ordering constraints. State updates are required for the
167 irq_enter_rcu() updates the preemption count which makes in_hardirq()
212 The state update on entry is handled in irqentry_nmi_enter() which updates
278 while handling an NMI. So NMI entry code has to be reentrant and state updates
|
| /Linux-v6.1/drivers/base/firmware_loader/ |
| D | Kconfig | 13 o /lib/firmware/updates/UTS_RELEASE
14 o /lib/firmware/updates
207 bool "Enable users to initiate firmware updates using sysfs"
212 sysfs interface that allows firmware updates to be initiated from
216 to support cards that rely on user-initiated updates for firmware files.
|
| /Linux-v6.1/Documentation/driver-api/ |
| D | generic-counter.rst | 107 Rising edges on signal A updates the respective count. The input level
116 updates the respective count; if the direction is backward, falling
117 edges on quadrature pair signal A updates the respective count.
122 updates the respective count; if the direction is backward, falling
123 edges on quadrature pair signal B updates the respective count.
127 Any state transition on quadrature pair signal A updates the
131 Any state transition on quadrature pair signal B updates the
135 Any state transition on either quadrature pair signals updates the
186 of movement and updates the respective position data. The "Quadrature
|
| /Linux-v6.1/sound/pci/ctxfi/ |
| D | cttimer.c | 183 int updates = 0; in ct_xfitimer_reprogram() local
208 updates++; in ct_xfitimer_reprogram()
225 return updates; in ct_xfitimer_reprogram()
|
| /Linux-v6.1/drivers/gpu/drm/amd/display/include/ |
| D | logger_interface.h | 50 const struct dc_surface_update *updates,
|
| /Linux-v6.1/Documentation/virt/acrn/ |
| D | io-request.rst | 93 registered clients based on the address of the I/O accesses, updates
96 f. The HSM updates I/O requests states to COMPLETE and notifies the hypervisor
|
| /Linux-v6.1/Documentation/x86/ |
| D | intel-hfi.rst | 66 that there may be many HFI updates every second, the updates relayed to
|
| /Linux-v6.1/Documentation/trace/coresight/ |
| D | coresight-trbe.rst | 38 * ``flag``: TRBE updates memory with access and dirty flags
|
| /Linux-v6.1/Documentation/translations/ko_KR/ |
| D | stable_api_nonsense.txt | 10 a fork. So if you have any comments or updates for this file please
|
| /Linux-v6.1/drivers/gpu/drm/amd/display/dc/core/ |
| D | dc_debug.c | 179 const struct dc_surface_update *updates, in update_surface_trace() argument
186 const struct dc_surface_update *update = &updates[i]; in update_surface_trace()
|
| /Linux-v6.1/Documentation/networking/devlink/ |
| D | devlink-flash.rst | 16 (usually ``/lib/firmware/``). Drivers may send status updates to inform
74 design, e.g. for looking up applicable firmware updates. This is why
|
| /Linux-v6.1/Documentation/translations/ja_JP/ |
| D | stable_api_nonsense.txt | 11 fork. So if you have any comments or updates of this file, please try
|
| D | SubmitChecklist | 11 fork. So if you have any comments or updates of this file, please try
|
| /Linux-v6.1/Documentation/gpu/amdgpu/display/ |
| D | dcn-overview.rst | 191 for most other updates that don't require enabling or disabling of new pipes.
197 These atomic register updates are driven by global sync signals in DCN. In
198 order to understand how atomic updates interact with DCN hardware, and how DCN
226 updates, i.e. it allows for multiple re-configurations between VUpdate
|
| /Linux-v6.1/drivers/net/ethernet/dlink/ |
| D | Kconfig | 42 More specific information and updates are available from
|
| /Linux-v6.1/Documentation/mhi/ |
| D | mhi.rst | 109 * When the host has a new buffer to send, it updates the ring element with
136 * When there is a new event the device needs to send, the device updates ED
216 * Host updates the WP of the corresponding event ring to indicate that the
|
| /Linux-v6.1/Documentation/livepatch/ |
| D | callbacks.rst | 10 - Safe updates to global data
126 may be possible to implement similar updates via pre/post-patch
|
| /Linux-v6.1/Documentation/admin-guide/hw-vuln/ |
| D | special-register-buffer-data-sampling.rst | 64 Intel will release microcode updates that modify the RDRAND, RDSEED, and
86 The microcode updates provide an opt-out mechanism (RNGDS_MITG_DIS) to disable
|
