| /linux/drivers/net/ethernet/netronome/nfp/nfpcore/ |
| H A D | nfp_cppcore.c | 50 * Following fields use explicit locking:
1307 * nfp_cpp_explicit_acquire() - Acquire explicit access handle
1313 * Return: NFP CPP explicit handle
1335 * nfp_cpp_explicit_set_target() - Set target fields for explicit
1336 * @expl: Explicit handle
1354 * nfp_cpp_explicit_set_data() - Set data fields for explicit
1355 * @expl: Explicit handle
1371 * nfp_cpp_explicit_set_signal() - Set signal fields for explicit
1372 * @expl: Explicit handle
1388 * nfp_cpp_explicit_set_posted() - Set completion fields for explicit
[all …]
|
| H A D | nfp6000_pcie.c | 106 /* The number of explicit BARs to reserve.
160 /* Explicit IO access */
162 struct mutex mutex; /* Lock access to this explicit group */
347 /* We don't match explicit bars through the area interface */ in matching_bar()
527 * BAR0.4: Reserved for Explicit 0.0-0.3 access
528 * BAR0.5: Reserved for Explicit 1.0-1.3 access
529 * BAR0.6: Reserved for Explicit 2.0-2.3 access
530 * BAR0.7: Reserved for Explicit 3.0-3.3 access
682 "0.%d: Explicit%d, ", 4 + i, i); in enable_bars()
948 /* Unaligned? Translate to an explicit access */ in nfp6000_area_read()
[all …]
|
| /linux/crypto/asymmetric_keys/ |
| H A D | pkcs7.asn1 | 10 content [0] EXPLICIT SignedData OPTIONAL
32 content [0] EXPLICIT Data OPTIONAL
84 aaSequence [2] EXPLICIT SEQUENCE OF AuthenticatedAttribute
85 -- Explicit because easier to compute digest on
|
| /linux/Documentation/RCU/ |
| H A 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
|
| /linux/tools/testing/selftests/drivers/net/mlxsw/ |
| H A D | vxlan_fdb_veto.sh | 88 check_fail $? "FDB with an explicit port not rejected"
93 check_err $? "FDB with an explicit port rejected without extack"
108 check_fail $? "FDB with an explicit port not rejected"
113 check_err $? "FDB with an explicit port rejected without extack"
|
| /linux/drivers/target/ |
| H A D | target_core_alua.c | 33 int *primary, int explicit);
35 struct se_lun *lun, int explicit, int offline);
266 * SET_TARGET_PORT_GROUPS for explicit ALUA operation.
295 * Determine if explicit ALUA via SET_TARGET_PORT_GROUPS is allowed in target_emulate_set_target_port_groups()
725 * Check implicit and explicit ALUA state change request.
728 core_alua_check_transition(int state, int valid, int *primary, int explicit) in core_alua_check_transition() argument
770 if (!(valid & ALUA_T_SUP) || explicit) in core_alua_check_transition()
821 return "Altered by Explicit STPG"; in core_alua_dump_status()
926 * After an explicit target port asymmetric access state in core_alua_queue_state_change_ua()
943 * After an explicit target port asymmetric access in core_alua_queue_state_change_ua()
[all …]
|
| /linux/Documentation/userspace-api/ |
| H A 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
|
| /linux/Documentation/block/ |
| H A 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
|
| /linux/arch/mips/math-emu/ |
| H A D | sp_maddf.c | 163 /* Put explicit bit at bit 62 if necessary */ in _sp_maddf()
173 * Move explicit bit from bit 62 to bit 26 since the in _sp_maddf()
181 /* Move explicit bit from bit 23 to bit 62 */ in _sp_maddf()
226 * Put explicit bit at bit 62 if necessary. in _sp_maddf()
235 * Move explicit bit from bit 62 to bit 26 since the in _sp_maddf()
|
| H A D | dp_maddf.c | 218 /* Put explicit bit at bit 126 if necessary */ in _dp_maddf()
229 * Move explicit bit from bit 126 to bit 55 since the in _dp_maddf()
237 /* Move explicit bit from bit 52 to bit 126 */ in _dp_maddf()
286 * Put explicit bit at bit 126 if necessary. in _dp_maddf()
291 /* MSB of lzm is the explicit bit */ in _dp_maddf()
315 * Move explicit bit from bit 126 to bit 55 since the in _dp_maddf()
|
| /linux/Documentation/locking/ |
| H A 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.
|
| /linux/drivers/gpu/drm/ |
| H A D | drm_gem_atomic_helper.c | 148 * explicit fencing interfaces on the atomic ioctl. in drm_gem_plane_helper_prepare_fb()
150 * This way explicit fencing can be used to overrule implicit fencing, in drm_gem_plane_helper_prepare_fb()
151 * which is important to make explicit fencing use-cases work: One in drm_gem_plane_helper_prepare_fb()
154 * the slower screen, whereas explicit fence allows 2 independent in drm_gem_plane_helper_prepare_fb()
156 * obeys both implicit and explicit fences for plane updates, then it in drm_gem_plane_helper_prepare_fb()
157 * will break all the benefits of explicit fencing. in drm_gem_plane_helper_prepare_fb()
|
| /linux/Documentation/devicetree/bindings/sound/ |
| H A 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
|
| /linux/Documentation/filesystems/ |
| H A 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
|
| /linux/include/linux/ |
| H A D | cgroup_subsys.h | 5 * DO NOT ADD ANY SUBSYSTEM WITHOUT EXPLICIT ACKS FROM CGROUP MAINTAINERS.
80 * DO NOT ADD ANY SUBSYSTEM WITHOUT EXPLICIT ACKS FROM CGROUP MAINTAINERS.
|
| H A D | devm-helpers.h | 43 * devm_delayed_work_autocancel() can be used to omit the explicit
68 * devm_work_autocancel() can be used to omit the explicit
|
| /linux/drivers/acpi/acpica/ |
| H A D | exconvrt.c | 94 * Explicit conversion is used only by to_integer. in acpi_ex_convert_to_integer()
380 * and explicit conversions and related rules.
452 /* Append "0x" prefix for explicit hex conversion */ in acpi_ex_convert_to_string()
486 * Explicit conversion from the to_decimal_string ASL operator. in acpi_ex_convert_to_string()
526 * Explicit conversion from the to_hex_string ASL operator. in acpi_ex_convert_to_string()
566 /* Emit 0x prefix for explicit/implicit hex conversion */ in acpi_ex_convert_to_string()
652 "Explicit operator, will store (%s) over existing type (%s)\n", in acpi_ex_convert_to_target_type()
|
| H A D | utstrtoul64.c | 24 * 2) Runtime "Explicit conversion" as defined in the ACPI specification.
32 * interpreter - Implicit and explicit conversions, GPE method names
40 * acpi_gbl_integer_byte_width is used to set the 32/64 bit limit for explicit
51 * support (explicit/implicit) for octal string conversions.
246 * an "explicit conversion" by the ACPI specification. The
|
| /linux/include/uapi/rdma/ |
| H A D | cxgb4-abi.h | 97 __u32 reserved; /* explicit padding */
108 __u32 reserved; /* explicit padding (optional for i386) */
|
| /linux/Documentation/arch/arm/ |
| H A 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,
|
| /linux/Documentation/netlink/ |
| H A D | genetlink-c.yaml | 55 … description: The explicit name for constant holding the count of operations (last operation + 1).
146 … description: The explicit name for constant holding the count of attributes (last attr + 1).
149 description: The explicit name for last member of attribute enum.
354 description: Explicit list of the attributes for the notification.
|
| H A D | genetlink-legacy.yaml | 55 … description: The explicit name for constant holding the count of operations (last operation + 1).
191 … description: The explicit name for constant holding the count of attributes (last attr + 1).
194 description: The explicit name for last member of attribute enum.
418 description: Explicit list of the attributes for the notification.
|
| /linux/drivers/nvdimm/ |
| H A D | dimm.c | 36 * The locked status bit reflects explicit status codes from the in nvdimm_probe()
58 * otherwise the locked indication is determined by explicit in nvdimm_probe()
|
| /linux/Documentation/staging/ |
| H A 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.
|
| /linux/tools/memory-model/Documentation/ |
| H A D | control-dependencies.txt | 22 from "a". This means that an explicit read barrier is required, for example
92 you must use explicit memory ordering, for example, smp_store_release():
103 Without explicit memory ordering, control-dependency-based ordering is
|