Searched full:explicit (Results 1 – 25 of 171) sorted by relevance
1234567
| /Documentation/RCU/ |
| D | lockdep.rst | 41 Use explicit check expression "c" along with
45 Use explicit check expression "c" along with
49 Use explicit check expression "c" along with
53 Use explicit check expression "c" along with
61 Use explicit check expression "c", and omit all barriers
|
| /Documentation/devicetree/bindings/sound/ |
| D | tdm-slot.txt | 18 to specify an explicit mapping of the channels and the slots. If it's absent
26 The explicit masks are given as array of integers, where the first
|
| /Documentation/block/ |
| D | writeback_cache_control.rst | 2 Explicit volatile write back cache control
20 Explicit cache flushes
28 set on an otherwise empty bio structure, which causes only an explicit cache
45 worry if the underlying devices need any explicit cache flushing and how
|
| /Documentation/userspace-api/ |
| D | dma-buf-alloc-exchange.rst | 27 format and modifier (implicit or explicit).
332 ``DRM_FORMAT_MOD_LINEAR``, which is an explicit guarantee that the image
340 as the sole member of a modifier list to declare that explicit modifiers are
345 at all) to declare that explicit modifiers are not supported and must not be
350 that the underlying layout is implementation-defined and that an explicit
357 not been allocated with an explicit modifier
361 explicit. For example, if a user wishes to allocate a buffer for use between
363 user **must not** allocate the buffer with explicit modifiers and attempt to
369 to explicit modifiers. For example, if the buffer is allocated with
371 ``gbm_bo_get_modifier`` and then use this modifier as an explicit modifier token
|
| /Documentation/locking/ |
| D | preempt-locking.rst | 15 requires explicit additional locking for very few additional situations.
21 RULE #1: Per-CPU data structures need explicit protection
32 First, since the data is per-CPU, it may not have explicit SMP locking, but
132 in doubt, rely on locking or explicit preemption disabling.
|
| /Documentation/filesystems/ |
| D | zonefs.rst | 311 * explicit-open
336 "explicit-open" option
341 implicit open, explicit open or closed conditions. This potential limitation
346 To avoid these potential errors, the "explicit-open" mount option forces zones
350 "explicit-open" mount option will result in a zone close command being issued
368 state of other zones. When the *explicit-open* mount option is used, zonefs
373 zone files open for writing. When the "explicit-open" mount option is used,
374 this number can never exceed *max_wro_seq_files*. If the *explicit-open*
382 is explicitly open (which happens only if the *explicit-open* mount option is
389 *nr_active_seq_files*, regardless of the use of the *explicit-open* mount
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | ltc2952-poweroff.txt | 19 until an explicit kill signal is received
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | brcm,bcm963xx-imagetag.txt | 6 needs to be used with an explicit firmware partition.
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-gpio | 8 userspace. GPIOs are only made available to userspace by an explicit
|
| /Documentation/netlink/ |
| D | genetlink-c.yaml | 54 … description: The explicit name for constant holding the count of operations (last operation + 1).
142 … description: The explicit name for constant holding the count of attributes (last attr + 1).
145 description: The explicit name for last member of attribute enum.
350 description: Explicit list of the attributes for the notification.
|
| D | genetlink-legacy.yaml | 54 … description: The explicit name for constant holding the count of operations (last operation + 1).
184 … description: The explicit name for constant holding the count of attributes (last attr + 1).
187 description: The explicit name for last member of attribute enum.
411 description: Explicit list of the attributes for the notification.
|
| D | netlink-raw.yaml | 54 … description: The explicit name for constant holding the count of operations (last operation + 1).
205 … description: The explicit name for constant holding the count of attributes (last attr + 1).
208 description: The explicit name for last member of attribute enum.
473 description: Explicit list of the attributes for the notification.
|
| /Documentation/arch/arm/ |
| D | cluster-pm-race-avoidance.rst | 153 a) an explicit hardware power-up operation, resulting
189 The CPU remains in this state until an explicit policy decision
197 explicit policy decision
309 a) an explicit hardware power-up operation, resulting
398 a) an explicit hardware power-up operation,
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | twl4030-charger.yaml | 14 value in explicit configuration in device-tree. Rather if there is a sibling
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-gsmi | 6 that provides callback functionality via explicit SMI
|
| /Documentation/staging/ |
| D | rpmsg.rst | 97 its length (in bytes), and an explicit destination address.
123 its length (in bytes), and explicit source and destination addresses.
164 its length (in bytes), and an explicit destination address.
186 its length (in bytes), and explicit source and destination addresses.
|
| /Documentation/networking/ |
| D | dctcp.rst | 8 center networks and leverages Explicit Congestion Notification (ECN) in
|
| D | bridge.rst | 210 The Linux bridge supports IGMPv3/MLDv2 EHT (Explicit Host Tracking), which
214 The explicit host tracking enables the device to keep track of each
216 benefit of the explicit host tracking in IGMP is to allow minimal leave
221 with IGMPv3 or MLDv2 and explicit tracking can immediately stop forwarding
|
| /Documentation/virt/hyperv/ |
| D | overview.rst | 28 * Explicit hypercalls: Linux makes an explicit function call to
40 arm64, these synthetic registers must be accessed using explicit
|
| /Documentation/devicetree/bindings/memory-controllers/ddr/ |
| D | jedec,lpddr-props.yaml | 21 Compatible strings can be either explicit vendor names and part numbers
|
| /Documentation/userspace-api/media/dvb/ |
| D | fe-get-property.rst | 54 parameters used. If the actual parameters are needed, an explicit
|
| /Documentation/arch/arm64/ |
| D | asymmetric-32bit.rst | 39 explicit "opt-in" and can be enabled by passing the
105 Explicit admission of a 32-bit deadline task to the default root domain
|
| /Documentation/networking/devlink/ |
| D | index.rst | 10 Driver facing APIs are currently transitioning to allow more explicit
|
| /Documentation/devicetree/bindings/ipmi/ |
| D | aspeed,ast2400-kcs-bmc.yaml | 26 - description: Old-style with explicit channel ID, no reg
|
| /Documentation/process/ |
| D | code-of-conduct.rst | 36 address, without explicit permission
|
1234567