Home
last modified time | relevance | path

Searched refs:interact (Results 1 – 25 of 80) sorted by relevance

1234

/Linux-v5.4/drivers/input/joystick/
Dinteract.c37 struct interact { struct
114 struct interact *interact = gameport_get_drvdata(gameport); in interact_poll() local
115 struct input_dev *dev = interact->dev; in interact_poll()
119 interact->reads++; in interact_poll()
121 if (interact_read_packet(interact->gameport, interact->length, data) < interact->length) { in interact_poll()
122 interact->bads++; in interact_poll()
126 data[i] <<= INTERACT_MAX_LENGTH - interact->length; in interact_poll()
128 switch (interact->type) { in interact_poll()
169 struct interact *interact = input_get_drvdata(dev); in interact_open() local
171 gameport_start_polling(interact->gameport); in interact_open()
[all …]
DMakefile22 obj-$(CONFIG_JOYSTICK_INTERACT) += interact.o
/Linux-v5.4/Documentation/security/tpm/
Dtpm_ftpm_tee.rst12 environment. The driver allows programs to interact with the TPM in the same
13 way they would interact with a hardware TPM.
Dtpm_vtpm_proxy.rst15 container. This allows programs to interact with a TPM in a container
16 the same way they interact with a TPM on the physical system. Each
Dxen-tpmfront.rst15 operating system (in Xen terms, a DomU). This allows programs to interact with
16 a TPM in a virtual system the same way they interact with a TPM on the physical
/Linux-v5.4/Documentation/input/
Duserio.rst20 to directly interact with the kernel's serio driver and control a virtual serio
26 In order to interact with the userio kernel module, one simply opens the
30 macros you need to interact with the device are defined in <linux/userio.h> and
/Linux-v5.4/Documentation/admin-guide/acpi/
Dindex.rst5 Here we document in detail how to interact with various mechanisms in
/Linux-v5.4/Documentation/devicetree/bindings/power/supply/
Dtwl-charger.txt3 The battery charger needs to interact with the USB phy in order
/Linux-v5.4/drivers/phy/socionext/
DKconfig14 on UniPhier SoCs. This driver provides interface to interact
/Linux-v5.4/Documentation/admin-guide/mm/
Dindex.rst22 Here we document in detail how to interact with various mechanisms in
/Linux-v5.4/drivers/soc/fsl/
DKconfig29 buffer management facilities for software to interact with
/Linux-v5.4/drivers/staging/fieldbus/anybuss/
DKconfig33 so userspace can interact with it via the fieldbus_dev userspace
/Linux-v5.4/Documentation/devicetree/bindings/interconnect/
Dinterconnect.txt42 components it has to interact with.
/Linux-v5.4/Documentation/media/uapi/mediactl/
Dmedia-controller-model.rst32 interact with other entities. Data (not restricted to video) produced
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-firmware-gsmi24 for more information on how to interact with
Dsysfs-ocfs26 ocfs2-tools to interact with the filesystem.
/Linux-v5.4/Documentation/devicetree/bindings/arm/msm/
Dqcom,saw2.txt7 the PMIC. It can also be wired up to interact with other processors in the
/Linux-v5.4/drivers/staging/speakup/
DTODO6 system. It allows blind users to interact with applications on the
/Linux-v5.4/Documentation/admin-guide/
Dbug-bisect.rst48 - interact with git bisect by using either::
/Linux-v5.4/Documentation/virt/kvm/arm/
Dhyp-abi.txt11 mode, but still needs to interact with it, allowing a built-in
/Linux-v5.4/drivers/hwtracing/intel_th/
DKconfig13 subdevices to interact with each other and hardware and for
/Linux-v5.4/Documentation/core-api/
Dprotection-keys.rst35 There are 3 system calls which directly interact with pkeys::
/Linux-v5.4/Documentation/spi/
Dbutterfly.rst20 SPI protocol drivers interact with the AVR, and could even let the AVR
/Linux-v5.4/drivers/cpufreq/
DKconfig.arm67 This driver uses SCPI Message Protocol driver to interact with the
278 This driver uses SCMI Message Protocol driver to interact with the
/Linux-v5.4/Documentation/media/uapi/v4l/
Dvidioc-subdev-g-crop.rst73 applications querying the same sub-device would thus not interact with

1234