Searched full:dependency (Results 1 – 25 of 66) sorted by relevance
123
| /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 | 123 This defines a dependency for this menu entry. If multiple
167 from a direct dependency or with a visible prompt.
208 FOO should imply not only BAZ, but also its dependency BAR::
251 module state. Dependency expressions have the following syntax::
310 the menu entry, e.g. this means the dependency "NET" is added to the
311 dependency list of the config option NETDEVICES.
316 be part of the dependency list and then one of these two conditions
389 dependency, but will not appear under menuconfig M anymore, because
446 This defines an if block. The dependency expression <expr> is appended
517 to describe the dependency on the compiler feature is to use "depends on"
[all …]
|
| D | Kconfig.select-break | 1 # Select broken dependency issue
21 mainmenu "Simple example to demo kconfig select broken dependency issue"
|
| D | kconfig-macro-language.rst | 9 two languages in one. One language describes dependency graphs consisting of
29 Then, Make analyzes the dependency graph and determines the targets to be
47 dependency as explained in kconfig-language.rst.
|
| D | Kconfig.recursion-issue-02 | 47 mainmenu "Simple example to demo cumulative kconfig recursive dependency implication"
|
| /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 …]
|
| /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
|
| D | pwrseq.rst | 37 to the power sequencer. Via the dependency system, multiple targets may
|
| D | dma-buf.rst | 277 :alt: Indefinite Fencing Dependency Cycle
278 :caption: Indefinite Fencing Dependency Cycle
366 memory blocks or runtime tracking of the full dependency graph of all DMA
|
| /Documentation/ |
| D | memory-barriers.txt | 55 - Address-dependency barriers (historical).
189 There is an obvious address dependency here, as the value loaded into D depends
394 address-dependency barriers; see the "SMP barrier pairing" subsection.
397 (2) Address-dependency barriers (historical).
404 An address-dependency barrier is a weaker form of read barrier. In the
407 the second load will be directed), an address-dependency barrier would
411 An address-dependency barrier is a partial ordering on interdependent
417 considered can then perceive. An address-dependency barrier issued by
422 the address-dependency barrier.
427 [!] Note that the first load really has to have an _address_ dependency and
[all …]
|
| /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
|
| D | ipv6.rst | 24 has a dependency on the IPv6 module being loaded, but no
|
| /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
|
| /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
135 * fully ordered --> control dependency on success for stores
177 * fully ordered --> RELEASE ordering + control dependency
192 * fully ordered --> RELEASE ordering + control dependency + hold
|
| D | dma-isa-lpc.rst | 57 will require a Kconfig dependency to ISA, not just ISA_DMA_API which
|
| /Documentation/bpf/libbpf/ |
| D | libbpf_build.rst | 31 dependency installed in /build/root/ and install them together with libbpf
|
| /Documentation/crypto/ |
| D | async-tx-api.rst | 53 2. cross channel dependency chains: the API allows a chain of dependent
99 before the dependency is submitted. This requires that all descriptors be
105 2. submitting an unacknowledged descriptor as a dependency to another
128 it polls for the completion of the operation. It handles dependency
|
| /Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 188 resolve dependencies. These dependency issues do happen at times, and
194 Often, though, dependency issues indicate that a change of approach is
195 needed. Merging another subsystem tree to resolve a dependency risks
201 merged into both trees. If the dependency is related to major
|
| /Documentation/arch/arm/samsung/ |
| D | overview.rst | 53 where to simplify the include and dependency issues involved with having
|
| /Documentation/devicetree/bindings/net/ |
| D | socfpga-dwmac.txt | 29 This device node has additional phandle dependency, the sgmii converter:
|
| /Documentation/filesystems/ |
| D | ocfs2-online-filecheck.rst | 31 This feature is not suited for extravagant checks which involve dependency of
|
| /Documentation/devicetree/bindings/power/ |
| D | power-domain.yaml | 66 dependencies). For representing such dependency a standard PM domain
|
| /Documentation/RCU/ |
| D | rcu_dereference.rst | 12 dependency) or the value written by a later memory access (representing
13 a data dependency).
192 so that a control dependency preserves the needed ordering.
|
| /Documentation/gpu/rfc/ |
| D | i915_vm_bind.rst | 49 work will be able to support requirements of object dependency setting in all
150 dependency setting.
|
| /Documentation/admin-guide/ |
| D | module-signing.rst | 94 their signatures checked without causing a dependency loop.
121 Note that enabling module signing adds a dependency on the OpenSSL devel
|
123