| /linux-6.12.1/drivers/pinctrl/qcom/ |
| D | pinctrl-ssbi-mpp.c | 113 bool paired; member
199 if (pin->paired) in pm8xxx_mpp_update()
210 if (pin->paired) in pm8xxx_mpp_update()
226 if (pin->paired) in pm8xxx_mpp_update()
358 arg = pin->paired; in pm8xxx_pin_config_get()
414 pin->paired = !!arg; in pm8xxx_pin_config_set()
578 if (!pin->paired) { in pm8xxx_mpp_dbg_show_one()
591 if (!pin->paired) { in pm8xxx_mpp_dbg_show_one()
607 if (!pin->paired) { in pm8xxx_mpp_dbg_show_one()
675 pin->paired = !!(ctrl & BIT(1)); in pm8xxx_pin_populate()
[all …]
|
| D | pinctrl-spmi-mpp.c | 129 bool paired; member
287 else if (pad->paired) in pmic_mpp_write_mode_ctl()
382 if (!pad->paired) in pmic_mpp_config_get()
468 pad->paired = !!arg; in pmic_mpp_config_set()
550 if (pad->paired) in pmic_mpp_config_dbg_show()
740 pad->paired = true; in pmic_mpp_populate()
|
| /linux-6.12.1/drivers/phy/qualcomm/ |
| D | Kconfig | 125 PHY which is usually paired with either the ChipIdea or Synopsys DWC3
134 chipsets. The PHY is paired with a Synopsys DWC3 USB controller
143 PMICs. The repeater is paired with a Synopsys eUSB2 Phy
173 to the V1 variants. The PHY is paired with a Synopsys DWC3 USB
191 is usually paired with either the ChipIdea or Synopsys DWC3 USB
|
| /linux-6.12.1/Documentation/firmware-guide/acpi/ |
| D | acpi-lid.rst | 67 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-6.12.1/Documentation/hwmon/ |
| D | ltc2991.rst | 29 supply voltages and can be paired for differential measurements of current sense
|
| /linux-6.12.1/tools/memory-model/Documentation/ |
| D | ordering.txt | 313 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 a call to rcu_assign_pointer() for that
399 paired with a call to smp_store_release(). Calls to rcu_dereference()
|
| D | recipes.txt | 361 control dependency paired with a full memory barrier:
|
| /linux-6.12.1/drivers/soc/tegra/ |
| D | Kconfig | 85 the Tegra210 has four Cortex-A57 cores paired with four Cortex-A53
|
| /linux-6.12.1/Documentation/ABI/testing/ |
| D | sysfs-platform-asus-wmi | 87 Enable the external GPU paired with ROG X-Flow laptops.
|
| D | sysfs-driver-wacom | 103 reports have been received from the paired device, reading
|
| /linux-6.12.1/drivers/net/ethernet/mellanox/mlx5/core/ |
| D | eswitch_offloads.c | 2995 esw_paired = !!xa_load(&esw->paired, peer_esw_i); in mlx5_esw_offloads_devcom_event()
3018 err = xa_insert(&esw->paired, peer_esw_i, peer_esw, GFP_KERNEL); in mlx5_esw_offloads_devcom_event()
3022 err = xa_insert(&peer_esw->paired, esw_i, esw, GFP_KERNEL); in mlx5_esw_offloads_devcom_event()
3039 xa_erase(&peer_esw->paired, esw_i); in mlx5_esw_offloads_devcom_event()
3040 xa_erase(&esw->paired, peer_esw_i); in mlx5_esw_offloads_devcom_event()
3050 xa_erase(&esw->paired, peer_esw_i); in mlx5_esw_offloads_devcom_event()
3078 xa_init(&esw->paired); in mlx5_esw_offloads_devcom_init()
3105 xa_destroy(&esw->paired); in mlx5_esw_offloads_devcom_cleanup()
|
| D | eswitch.h | 384 struct xarray paired; member
|
| /linux-6.12.1/tools/memory-model/ |
| D | lock.cat | 25 * LKR and LKW events always come paired, like all RMW event sequences.
|
| /linux-6.12.1/Documentation/driver-api/usb/ |
| D | hotplug.rst | 98 specific criteria are identified by bits set in "match_flags", paired
|
| /linux-6.12.1/Documentation/driver-api/ |
| D | eisa.rst | 102 optionally be paired with a driver-dependent value
|
| D | pin-control.rst | 1258 ``pinctrl_get()`` must be paired with a plain ``pinctrl_put()``.
1259 ``pinctrl_get()`` may not be paired with ``devm_pinctrl_put()``.
1260 ``devm_pinctrl_get()`` can optionally be paired with ``devm_pinctrl_put()``.
1261 ``devm_pinctrl_get()`` may not be paired with plain ``pinctrl_put()``.
|
| /linux-6.12.1/Documentation/driver-api/dmaengine/ |
| D | client.rst | 144 paired.
|
| /linux-6.12.1/Documentation/scheduler/ |
| D | sched-bwc.rst | 47 does maintain stability, since every overrun must be paired with an
|
| /linux-6.12.1/drivers/gpu/drm/i915/display/ |
| D | intel_hdcp.c | 1228 bool *paired, in hdcp2_verify_rx_cert_prepare_km() argument
1247 rx_cert, paired, in hdcp2_verify_rx_cert_prepare_km()
|
| D | intel_hdmi.c | 1657 u8 msg_id, bool paired) in intel_hdmi_hdcp2_wait_for_msg() argument
1664 timeout = get_hdcp2_msg_timeout(msg_id, paired); in intel_hdmi_hdcp2_wait_for_msg()
|
| /linux-6.12.1/Documentation/usb/ |
| D | gadget_uvc.rst | 377 must be paired with a userspace program that responds to UVC control requests and
|
| /linux-6.12.1/arch/loongarch/ |
| D | Kconfig | 521 LoongArch maintains cache coherency in hardware, but when paired
|
| /linux-6.12.1/Documentation/ |
| D | memory-barriers.txt | 393 [!] 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-6.12.1/Documentation/admin-guide/device-mapper/ |
| D | vdo-design.rst | 84 record consists of this block name paired with the presumed location of
505 the packer if it cannot be paired with any other compressed block
|
| /linux-6.12.1/Documentation/filesystems/ |
| D | porting.rst | 892 mnt_want_write_file() can now only be paired with mnt_drop_write_file(),
893 whereas previously it could be paired with mnt_drop_write() as well.
|