| /Linux-v5.10/drivers/net/ethernet/mellanox/mlx5/core/lib/ |
| D | devcom.c | 21 bool paired; member
207 bool paired) in mlx5_devcom_set_paired() argument
214 comp->paired = paired; in mlx5_devcom_set_paired()
223 return devcom->priv->components[id].paired; in mlx5_devcom_is_paired()
237 if (!comp->paired) { in mlx5_devcom_get_peer_data()
|
| D | devcom.h | 36 bool paired);
|
| /Linux-v5.10/drivers/pinctrl/qcom/ |
| D | pinctrl-ssbi-mpp.c | 113 bool paired; member
197 if (pin->paired) in pm8xxx_mpp_update()
208 if (pin->paired) in pm8xxx_mpp_update()
224 if (pin->paired) in pm8xxx_mpp_update()
356 arg = pin->paired; in pm8xxx_pin_config_get()
412 pin->paired = !!arg; in pm8xxx_pin_config_set()
581 if (!pin->paired) { in pm8xxx_mpp_dbg_show_one()
594 if (!pin->paired) { in pm8xxx_mpp_dbg_show_one()
610 if (!pin->paired) { in pm8xxx_mpp_dbg_show_one()
680 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()
751 pad->paired = true; in pmic_mpp_populate()
|
| /Linux-v5.10/drivers/phy/qualcomm/ |
| D | Kconfig | 59 PHY which is usually paired with either the ChipIdea or Synopsys DWC3
78 to the V1 variants. The PHY is paired with a Synopsys DWC3 USB
96 is usually paired with either the ChipIdea or Synopsys DWC3 USB
|
| /Linux-v5.10/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-v5.10/Documentation/devicetree/bindings/timer/ |
| D | qcom,msm-timer.txt | 6 properties specify which subsystem the timers are paired with.
|
| /Linux-v5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | qcom,pmic-mpp.txt | 160 - qcom,paired:
163 Definition: Indicates that the pin should be operating in paired mode.
|
| D | qcom,pmic-gpio.txt | 120 "paired",
|
| /Linux-v5.10/drivers/soc/tegra/ |
| D | Kconfig | 85 the Tegra210 has four Cortex-A57 cores paired with four Cortex-A53
|
| /Linux-v5.10/Documentation/devicetree/bindings/mtd/ |
| D | partition.txt | 66 paired-pages corruptions
|
| D | brcm,brcmnand.txt | 6 paired with a custom DMA engine (inventively named "Flash DMA") which supports
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | sysfs-driver-wacom | 103 reports have been received from the paired device, reading
|
| /Linux-v5.10/tools/memory-model/ |
| D | lock.cat | 25 * LKR and LKW events always come paired, like all RMW event sequences.
|
| /Linux-v5.10/Documentation/driver-api/usb/ |
| D | hotplug.rst | 98 specific criteria are identified by bits set in "match_flags", paired
|
| /Linux-v5.10/Documentation/driver-api/ |
| D | eisa.rst | 102 optionally be paired with a driver-dependent value
|
| D | pinctl.rst | 1281 pinctrl_get() must be paired with a plain pinctrl_put().
1282 pinctrl_get() may not be paired with devm_pinctrl_put().
1283 devm_pinctrl_get() can optionally be paired with devm_pinctrl_put().
1284 devm_pinctrl_get() may not be paired with plain pinctrl_put().
|
| /Linux-v5.10/Documentation/driver-api/dmaengine/ |
| D | client.rst | 133 paired.
|
| /Linux-v5.10/drivers/gpu/drm/i915/display/ |
| D | intel_hdcp.c | 1042 bool *paired, in hdcp2_verify_rx_cert_prepare_km() argument
1060 rx_cert, paired, in hdcp2_verify_rx_cert_prepare_km()
|
| D | intel_hdmi.c | 1666 u8 msg_id, bool paired) in intel_hdmi_hdcp2_wait_for_msg() argument
1673 timeout = get_hdcp2_msg_timeout(msg_id, paired); in intel_hdmi_hdcp2_wait_for_msg()
|
| /Linux-v5.10/Documentation/filesystems/caching/ |
| D | fscache.rst | 507 and the following paired letters:
|
| /Linux-v5.10/tools/memory-model/Documentation/ |
| D | recipes.txt | 361 control dependency paired with a full memory barrier:
|
| /Linux-v5.10/Documentation/ |
| D | memory-barriers.txt | 394 [!] Note that write barriers should normally be paired with read or data
430 [!] Note that data dependency barriers should normally be paired with
447 [!] Note that read barriers should normally be paired with write barriers;
477 An ACQUIRE operation should almost always be paired with a RELEASE
924 always be paired. A lack of appropriate pairing is almost certainly an error.
|
| /Linux-v5.10/Documentation/power/ |
| D | runtime_pm.rst | 583 pm_runtime_get_sync() call paired with a pm_runtime_put() call will be
|
| /Linux-v5.10/Documentation/trace/ |
| D | histogram-design.rst | 577 The sched_switch histogram paired with the above sched_waking | |
|
