Searched full:explicit (Results 1 – 25 of 134) sorted by relevance
123456
/Documentation/core-api/ |
D | atomic_ops.rst | 44 proper implicit or explicit read memory barrier is needed before reading the 65 or explicit memory barrier is needed before the value set with the operation 75 implicit or explicit memory barrier is used after possible runtime 79 interface must take care of that with a proper implicit or explicit memory 195 atomic_t value. The first two routines pass explicit integers by 200 require any explicit memory barriers. They need only perform the 213 include explicit memory barriers that are performed before and after 221 If the atomic instructions used in an implementation provide explicit 231 explicit counter adjustment is given instead of the implicit "1". 244 Again, these primitives provide explicit memory barrier semantics around [all …]
|
/Documentation/RCU/ |
D | lockdep.rst | 39 Use explicit check expression "c" along with 43 Use explicit check expression "c" along with 47 Use explicit check expression "c" along with 51 Use explicit check expression "c" along with 57 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/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/devicetree/bindings/power/reset/ |
D | ltc2952-poweroff.txt | 19 until an explicit kill signal is received
|
/Documentation/devicetree/bindings/power/supply/ |
D | twl-charger.txt | 8 is no value in explicit configuration in device-tree. Rather
|
/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/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/ABI/testing/ |
D | sysfs-firmware-gsmi | 6 that provides callback functionality via explicit SMI
|
/Documentation/staging/ |
D | rpmsg.rst | 96 its length (in bytes), and an explicit destination address. 121 its length (in bytes), and explicit source and destination addresses. 160 its length (in bytes), and an explicit destination address. 182 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
|
/Documentation/devicetree/bindings/net/dsa/ |
D | sja1105.txt | 15 Although the device ID could be detected at runtime, explicit bindings 30 The effect of this property (in either its implicit or explicit form)
|
/Documentation/userspace-api/media/dvb/ |
D | fe-get-property.rst | 54 parameters used. If the actual parameters are needed, an explicit
|
/Documentation/process/ |
D | code-of-conduct.rst | 36 address, without explicit permission
|
/Documentation/devicetree/bindings/powerpc/ |
D | ibm,powerpc-cpu-features.txt | 122 If no bits are set, the hypervisor must have explicit/custom support for 141 If no bits are set, the operating system must have explicit/custom support
|
/Documentation/driver-api/ |
D | sync_file.rst | 13 to/from userspace. It enables userspace to do explicit fencing, where instead
|
/Documentation/devicetree/bindings/crypto/ |
D | fsl-sec4.txt | 103 Usage: required if SEC 4.0 requires explicit enablement of clocks 109 Usage: required if SEC 4.0 requires explicit enablement of clocks 398 Usage: optional, required if SNVS LP RTC requires explicit 405 Usage: optional, required if SNVS LP RTC requires explicit
|
/Documentation/infiniband/ |
D | core_locking.rst | 5 This guide is an attempt to make explicit the locking assumptions
|
/Documentation/driver-api/usb/ |
D | anchors.rst | 31 An association of URBs to an anchor is made by an explicit
|
/Documentation/gpu/ |
D | vkms.rst | 102 any explicit form through e.g. possible property values. Userspace can only
|
/Documentation/firmware-guide/acpi/ |
D | gpio-properties.rst | 74 Explicit x (no _DSD) as Pull Bias (Up == High, Down == Low), 83 is explicit and _DSD is present, will be treated as active with a high
|
/Documentation/filesystems/ |
D | configfs.rst | 29 A configfs config_item is created via an explicit userspace operation: 436 more explicit to have a method whereby userspace sees this divergence. 510 Far better would be an explicit action notifying the subsystem that the 511 config_item is ready to go. More importantly, an explicit action allows
|
D | porting.rst | 43 Keep in mind that now you need explicit initialization of private data 70 Replace DECLARE_FSTYPE... with explicit initializer and have ->get_sb set as 159 explicit support for exporting, e.g. via NFS. The structure is fully 600 the body to traverse and store the cookie using explicit void ** argument. 830 Note that the callback (be it via ->free_inode() or explicit call_rcu()
|
123456