Home
last modified time | relevance | path

Searched refs:paired (Results 1 – 20 of 20) sorted by relevance

/linux/drivers/phy/qualcomm/
H A DKconfig135 PHY which is usually paired with either the ChipIdea or Synopsys DWC3
144 PMICs. The repeater is paired with a Synopsys or M31 eUSB2 Phy
178 up of the associated USB repeater that is paired with the eUSB2
197 to the V1 variants. The PHY is paired with a Synopsys DWC3 USB
215 is usually paired with either the ChipIdea or Synopsys DWC3 USB
/linux/Documentation/firmware-guide/acpi/
H A Dacpi-lid.rst67 firmware cannot make sure "opened"/"closed" events are paired, the ACPI
77 and whether the "opened"/"closed" events are paired fully relies on the
90 are paired fully relies on the firmware implementation.
/linux/Documentation/hwmon/
H A Dltc2991.rst29 supply voltages and can be paired for differential measurements of current sense
/linux/tools/memory-model/Documentation/
H A Dordering.txt313 As mentioned earlier, release operations are often paired with acquire
350 Symmetry being what it is, acquire operations are often paired with the
397 usually paired with a call to rcu_assign_pointer() for that same pointer
398 in much the same way that a call to smp_load_acquire() is paired with
H A Drecipes.txt365 control dependency paired with a full memory barrier:
/linux/Documentation/ABI/testing/
H A Dsysfs-driver-wacom103 reports have been received from the paired device, reading
/linux/drivers/net/ethernet/mellanox/mlx5/core/
H A Deswitch_offloads.c3465 return !!xa_load(&esw->paired, peer_esw_i); in mlx5_eswitch_is_peer()
3480 esw_paired = !!xa_load(&esw->paired, peer_esw_i); in mlx5_esw_offloads_devcom_event()
3503 err = xa_insert(&esw->paired, peer_esw_i, peer_esw, GFP_KERNEL); in mlx5_esw_offloads_devcom_event()
3507 err = xa_insert(&peer_esw->paired, esw_i, esw, GFP_KERNEL); in mlx5_esw_offloads_devcom_event()
3524 xa_erase(&peer_esw->paired, esw_i); in mlx5_esw_offloads_devcom_event()
3525 xa_erase(&esw->paired, peer_esw_i); in mlx5_esw_offloads_devcom_event()
3535 xa_erase(&esw->paired, peer_esw_i); in mlx5_esw_offloads_devcom_event()
3564 xa_init(&esw->paired); in mlx5_esw_offloads_devcom_init()
3592 xa_destroy(&esw->paired); in mlx5_esw_offloads_devcom_cleanup()
H A Deswitch.h439 struct xarray paired; member
/linux/tools/memory-model/
H A Dlock.cat25 * LKR and LKW events always come paired, like all RMW event sequences.
/linux/Documentation/wmi/devices/
H A Dlenovo-wmi-gamezone.rst11 profiles and overclocking. It is paired with multiple event GUIDs
/linux/Documentation/driver-api/
H A Dpin-control.rst1313 ``pinctrl_get()`` must be paired with a plain ``pinctrl_put()``.
1314 ``pinctrl_get()`` may not be paired with ``devm_pinctrl_put()``.
1315 ``devm_pinctrl_get()`` can optionally be paired with ``devm_pinctrl_put()``.
1316 ``devm_pinctrl_get()`` may not be paired with plain ``pinctrl_put()``.
/linux/Documentation/driver-api/dmaengine/
H A Dclient.rst153 paired.
/linux/Documentation/usb/
H A Dgadget_uvc.rst377 must be paired with a userspace program that responds to UVC control requests and
/linux/drivers/gpu/drm/i915/display/
H A Dintel_hdcp.c1259 bool *paired, in hdcp2_verify_rx_cert_prepare_km() argument
1278 rx_cert, paired, in hdcp2_verify_rx_cert_prepare_km()
/linux/Documentation/
H A Dmemory-barriers.txt393 [!] Note that write barriers should normally be paired with read or
434 [!] Note that address-dependency barriers should normally be paired with
455 [!] Note that read barriers should normally be paired with write barriers;
485 An ACQUIRE operation should almost always be paired with a RELEASE
943 always be paired. A lack of appropriate pairing is almost certainly an error.
/linux/arch/loongarch/
H A DKconfig594 LoongArch maintains cache coherency in hardware, but when paired
/linux/Documentation/bpf/
H A Dsigning.rst340 To bound the map and let a reused id read as a fresh load, this can be paired
/linux/Documentation/networking/
H A Dj1939.rst783 - It is typically paired with a corresponding ``SCM_TSTAMP_SCHED`` event
/linux/Documentation/filesystems/
H A Dvfs.rst1394 should be paired with ``d_unalias_trylock``; that one is called after
/linux/drivers/mfd/
H A DKconfig1300 SoCs. Note, that this will only be useful paired with descriptions