Home
last modified time | relevance | path

Searched full:communicated (Results 1 – 25 of 51) sorted by relevance

123

/linux/include/uapi/linux/
H A Dif_xdp.h126 * are communicated via csum_start and csum_offset fields of struct
133 * launch time is communicated via launch_time field of struct xsk_tx_metadata.
H A Dfutex.h151 * changed if the change is first communicated with the glibc folks.
/linux/tools/include/uapi/linux/
H A Dif_xdp.h126 * are communicated via csum_start and csum_offset fields of struct
133 * launch time is communicated via launch_time field of struct xsk_tx_metadata.
/linux/drivers/platform/x86/dell/
H A DKconfig154 communicated over ACPI-WMI.
167 communicated over SMI/SMM.
/linux/include/linux/net/intel/libie/
H A Dpctype.h8 * communicated over the virtchnl API as part of struct virtchnl_rss_hashena.
/linux/drivers/gpu/drm/msm/dp/
H A Ddp_debug.h26 * for debugfs input to be communicated with existing modules
/linux/arch/x86/include/asm/
H A Dsev-common.h216 * GHCB-defined return codes that are communicated back to the guest via
225 * communicated back to the guest via SW_EXITINFO2[31:0].
/linux/include/linux/
H A Dapm_bios.h88 * This is the "All Devices" ID communicated to the BIOS
H A Dtfrc.h
H A Dieee802154.h220 * A PAN identifier conflict has been detected and communicated to the
H A Dti_wilink_st.h421 * @chip_awake: Chip specific deep sleep states is communicated to Host
/linux/Documentation/hid/
H A Dhid-sensor.rst162 way to obfuscate the data being communicated by a sensor. Without knowing the
164 an application/driver to determine what data is being communicated by the sensor.
/linux/tools/testing/selftests/gpio/
H A Dgpio-sim.sh180 echo "1.1. Chip name is communicated to user"
195 echo "1.3. Device name is communicated to user"
/linux/arch/mips/include/asm/sn/
H A Dgda.h11 * The GDA contains information communicated between the
/linux/Documentation/admin-guide/hw-vuln/
H A Dcross-thread-rsb.rst41 requests to transition out of the C0 state. This can be communicated with the
/linux/include/linux/net/intel/
H A Di40e_client.h86 * and needs to be communicated to the client when they change
/linux/drivers/infiniband/hw/hfi1/
H A Dcommon.h129 * A bitmask of kernel/global capabilities that should be communicated
/linux/Documentation/gpu/
H A Dafbc.rst35 The component ordering is communicated via the fourcc code in the
/linux/Documentation/ABI/stable/
H A Dsysfs-driver-ib_srp47 communicated from initiator to target via an additional RDMA
/linux/include/uapi/rdma/hfi/
H A Dhfi1_user.h90 * driver features. The same set of bits are communicated to user
/linux/Documentation/arch/x86/
H A Damd-hfi.rst106 This classification is communicated to the OS via logical processor
/linux/drivers/net/ethernet/qlogic/qed/
H A Dqed_vf.h192 * [in case VF is newer than PF]. This is communicated back
228 * If communicated between VF/PF, each TLV relating to queues should be
/linux/kernel/
H A Drseq.c523 * Ensure the provided rseq is properly aligned, as communicated to in rseq_length_valid()
529 * large enough to contain all supported fields, as communicated to in rseq_length_valid()
/linux/Documentation/process/
H A Dembargoed-hardware-issues.rst245 communicated by the silicon vendor to the kernel response team.
/linux/drivers/slimbus/
H A Dcore.c310 * reports absent, OR when the device cannot be communicated with

123