Home
last modified time | relevance | path

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

12345

/Linux-v5.15/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 …]
DMakefile23 obj-$(CONFIG_JOYSTICK_INTERACT) += interact.o
/Linux-v5.15/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.15/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.15/Documentation/admin-guide/acpi/
Dindex.rst5 Here we document in detail how to interact with various mechanisms in
/Linux-v5.15/arch/arm/boot/dts/
Dbcm2835-rpi-common.dtsi4 * bcm2835, bcm2836 and bcm2837 implementations that interact with RPi's
/Linux-v5.15/drivers/platform/x86/intel/int1092/
DKconfig9 to SAR driver. The front end application in userspace will interact with SAR
/Linux-v5.15/drivers/accessibility/speakup/
DTODO6 system. It allows blind users to interact with applications on the
/Linux-v5.15/Documentation/admin-guide/mm/
Dindex.rst22 Here we document in detail how to interact with various mechanisms in
/Linux-v5.15/drivers/phy/socionext/
DKconfig14 on UniPhier SoCs. This driver provides interface to interact
/Linux-v5.15/drivers/staging/fieldbus/anybuss/
DKconfig33 so userspace can interact with it via the fieldbus_dev userspace
/Linux-v5.15/drivers/staging/vc04_services/
DKconfig34 by userspace libraries and testing tools to interact with VideoCore, via
/Linux-v5.15/drivers/soc/fsl/
DKconfig29 buffer management facilities for software to interact with
/Linux-v5.15/Documentation/userspace-api/media/mediactl/
Dmedia-controller-model.rst25 interact with other entities. Data (not restricted to video) produced
/Linux-v5.15/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.15/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.15/Documentation/admin-guide/
Dbug-bisect.rst48 - interact with git bisect by using either::
/Linux-v5.15/Documentation/devicetree/bindings/interconnect/
Dinterconnect.txt43 components it has to interact with.
/Linux-v5.15/sound/soc/
DKconfig53 Do note that it creates fake playback devices which do not interact
/Linux-v5.15/drivers/phy/
DKconfig61 interface to interact with USB GEN-II and USB 3.x PHY that is part
/Linux-v5.15/drivers/hwtracing/intel_th/
DKconfig13 subdevices to interact with each other and hardware and for
/Linux-v5.15/Documentation/virt/kvm/arm/
Dhyp-abi.rst20 mode, but still needs to interact with it, allowing a built-in

12345