| /Linux-v5.10/scripts/kconfig/tests/err_recursive_dep/ |
| D | expected_stderr | 1 Kconfig:11:error: recursive dependency detected!
4 subsection "Kconfig recursive dependency limitations"
6 Kconfig:5:error: recursive dependency detected!
9 subsection "Kconfig recursive dependency limitations"
11 Kconfig:17:error: recursive dependency detected!
15 subsection "Kconfig recursive dependency limitations"
17 Kconfig:32:error: recursive dependency detected!
21 subsection "Kconfig recursive dependency limitations"
23 Kconfig:37:error: recursive dependency detected!
27 subsection "Kconfig recursive dependency limitations"
[all …]
|
| /Linux-v5.10/drivers/gpu/drm/scheduler/ |
| D | sched_entity.c | 134 if (READ_ONCE(entity->dependency)) in drm_sched_entity_is_ready()
279 if (entity->dependency) { in drm_sched_entity_fini()
280 dma_fence_remove_callback(entity->dependency, in drm_sched_entity_fini()
282 dma_fence_put(entity->dependency); in drm_sched_entity_fini()
283 entity->dependency = NULL; in drm_sched_entity_fini()
317 entity->dependency = NULL; in drm_sched_entity_clear_dep()
363 struct dma_fence *fence = entity->dependency; in drm_sched_entity_add_dependency_cb()
373 dma_fence_put(entity->dependency); in drm_sched_entity_add_dependency_cb()
385 dma_fence_put(entity->dependency); in drm_sched_entity_add_dependency_cb()
386 entity->dependency = fence; in drm_sched_entity_add_dependency_cb()
[all …]
|
| /Linux-v5.10/Documentation/kbuild/ |
| D | Kconfig.recursion-issue-01 | 8 # This Kconfig file has a simple recursive dependency issue. In order to
9 # understand why this recursive dependency issue occurs lets consider what
34 # the "recursive dependency detected" error.
39 # since CORE_BELL_A depends on CORE. Recursive dependency issues are not always
42 # easy to understand. Note that matching semantics on the dependency on
45 mainmenu "Simple example to demo kconfig recursive dependency issue"
|
| D | kconfig-language.rst | 119 This defines a dependency for this menu entry. If multiple
157 from a direct dependency or with a visible prompt.
198 FOO should imply not only BAZ, but also its dependency BAR::
311 the menu entry, e.g. this means the dependency "NET" is added to the
312 dependency list of the config option NETDEVICES.
317 be part of the dependency list and then one of these two conditions
390 dependency, but will not appear under menuconfig M anymore, because
461 This defines an if block. The dependency expression <expr> is appended
532 to describe the dependency on the compiler feature is to use "depends on"
556 Kconfig recursive dependency limitations
[all …]
|
| D | Kconfig.select-break | 1 # Select broken dependency issue
21 mainmenu "Simple example to demo kconfig select broken dependency issue"
|
| /Linux-v5.10/include/trace/events/ |
| D | timer.h | 400 TP_PROTO(int success, int dependency),
402 TP_ARGS(success, dependency),
406 __field( int , dependency )
411 __entry->dependency = dependency;
415 show_tick_dep_name(__entry->dependency))
|
| /Linux-v5.10/tools/memory-model/litmus-tests/ |
| D | LB+fencembonceonce+ctrlonceonce.litmus | 9 * combination of a control dependency and a full memory barrier are enough
11 * another control dependency and order would still be maintained.)
|
| /Linux-v5.10/Documentation/locking/ |
| D | lockdep-design.rst | 22 dependency can be understood as lock order, where L1 -> L2 suggests that
25 dependency just means the order ever happened. The validator maintains a
137 Multi-lock dependency rules:
151 validator will find such dependency circle in arbitrary complexity,
173 dependency rules are enforced:
375 likely to be linked into the lock-dependency graph. This turns out to
512 Dependency types and strong dependency paths:
519 For each lock dependency::
531 With the above combination for simplification, there are 4 types of dependency edges
535 exclusive writer to recursive reader dependency, "X -(ER)-> Y" means
[all …]
|
| /Linux-v5.10/scripts/ |
| D | dev-needs.sh | 14 /sys/devices and then lists the probe dependency chain (suppliers and
15 parents) of these devices. It does a breadth first search of the dependency
17 dependency chain.
|
| /Linux-v5.10/Documentation/core-api/ |
| D | refcount-vs-atomic.rst | 64 A control dependency (on success) for refcounters guarantees that
68 Control dependency on stores are not implemented using any explicit
123 * fully ordered --> control dependency on success for stores
152 * fully ordered --> RELEASE ordering + control dependency
167 * fully ordered --> RELEASE ordering + control dependency + hold
|
| /Linux-v5.10/drivers/gpu/drm/v3d/ |
| D | v3d_sched.c | 358 .dependency = v3d_job_dependency,
365 .dependency = v3d_job_dependency,
372 .dependency = v3d_job_dependency,
379 .dependency = v3d_job_dependency,
386 .dependency = v3d_job_dependency,
|
| /Linux-v5.10/tools/memory-model/Documentation/ |
| D | cheatsheet.txt | 31 DR: Dependent read (address dependency)
32 DW: Dependent write (address, data, or control dependency)
|
| D | recipes.txt | 274 against later accesses that depend on the value loaded. A dependency
276 (address dependency, as shown above), the value written by a later store
277 (data dependency), or whether or not a later store is executed in the
278 first place (control dependency). Note that the term "data dependency"
361 control dependency paired with a full memory barrier:
378 This pairing of a control dependency in CPU0() with a full memory
384 control dependency on the kernel side and a full memory barrier on
398 The kernel's control dependency between the load from ->data_tail
555 the LB litmus test, a control dependency was enough to do the
|
| /Linux-v5.10/include/drm/ |
| D | gpu_scheduler.h | 97 struct dma_fence *dependency; member
221 struct dma_fence *(*dependency)(struct drm_sched_job *sched_job, member
|
| /Linux-v5.10/Documentation/driver-api/memory-devices/ |
| D | ti-gpmc.rst | 28 dependency for certain gpmc timings on gpmc clock frequency. Hence a
54 gpmc timing dependency on peripheral timings:
175 indirect dependency of peripheral timings to gpmc timings other than
|
| /Linux-v5.10/Documentation/ |
| D | memory-barriers.txt | 55 - Data dependency barriers (historical).
190 There is an obvious data dependency here, as the value loaded into D depends on
395 dependency barriers; see the "SMP barrier pairing" subsection.
398 (2) Data dependency barriers.
400 A data dependency barrier is a weaker form of read barrier. In the case
403 load will be directed), a data dependency barrier would be required to
407 A data dependency barrier is a partial ordering on interdependent loads
413 considered can then perceive. A data dependency barrier issued by the CPU
418 dependency barrier.
423 [!] Note that the first load really has to have a _data_ dependency and
[all …]
|
| /Linux-v5.10/Documentation/driver-api/ |
| D | device_link.rst | 21 Often these two dependency types come together, so a device depends on
27 In its standard or *managed* form, a device link combines *both* dependency
60 represents a driver presence dependency, yet is added from the consumer's
82 driver presence dependency is needed (but only correct suspend/resume and
109 Driver authors should be aware that a driver presence dependency for managed
178 (supplier). A driver presence dependency is not necessary for this
194 * In some SoCs a functional dependency exists from display, video codec and
208 ordering or a driver presence dependency.
235 To prevent introduction of dependency loops into the graph, it is
246 such a device link only makes sense if a driver presence dependency is
|
| /Linux-v5.10/drivers/clk/zynqmp/ |
| D | Kconfig | 9 It has a dependency on the PMU firmware.
|
| /Linux-v5.10/Documentation/networking/ |
| D | tcp-thin.rst | 15 dependency on the arrival of new data from the application to trigger
22 lifespan. The combination of time-dependency and the fact that the
|
| /Linux-v5.10/Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,apr.txt | 52 that the particular apr service has a dependency on.
102 have no such dependency.
|
| /Linux-v5.10/drivers/virt/nitro_enclaves/ |
| D | Kconfig | 8 # TODO: Add dependency for ARM64 once NE is supported on Arm platforms. For now,
|
| /Linux-v5.10/kernel/bpf/preload/ |
| D | Kconfig | 10 # The dependency on !COMPILE_TEST prevents it from being enabled
|
| /Linux-v5.10/tools/build/ |
| D | Build.include | 59 # Copy dependency data into .cmd file
60 # - gcc -M dependency info
|
| /Linux-v5.10/drivers/gpu/drm/i915/ |
| D | Kconfig.unstable | 7 # We use the dependency on !COMPILE_TEST to not be enabled in
|
| /Linux-v5.10/drivers/mtd/lpddr/ |
| D | Kconfig | 23 # ARM dependency is only for writel_relaxed()
|
