Home
last modified time | relevance | path

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

123

/Linux-v4.19/drivers/input/joystick/
Dinteract.c49 struct interact { struct
126 struct interact *interact = gameport_get_drvdata(gameport); in interact_poll() local
127 struct input_dev *dev = interact->dev; in interact_poll()
131 interact->reads++; in interact_poll()
133 if (interact_read_packet(interact->gameport, interact->length, data) < interact->length) { in interact_poll()
134 interact->bads++; in interact_poll()
138 data[i] <<= INTERACT_MAX_LENGTH - interact->length; in interact_poll()
140 switch (interact->type) { in interact_poll()
181 struct interact *interact = input_get_drvdata(dev); in interact_open() local
183 gameport_start_polling(interact->gameport); in interact_open()
[all …]
DMakefile21 obj-$(CONFIG_JOYSTICK_INTERACT) += interact.o
/Linux-v4.19/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-v4.19/Documentation/security/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.txt12 operating system (in Xen terms, a DomU). This allows programs to interact with
13 a TPM in a virtual system the same way they interact with a TPM on the physical
/Linux-v4.19/drivers/soc/fsl/
DKconfig27 buffer management facilities for software to interact with
/Linux-v4.19/Documentation/devicetree/bindings/power/supply/
Dtwl-charger.txt3 The battery charger needs to interact with the USB phy in order
/Linux-v4.19/Documentation/admin-guide/mm/
Dindex.rst22 Here we document in detail how to interact with various mechanisms in
/Linux-v4.19/Documentation/power/
D00-INDEX10 - How drivers interact with system-wide power management
/Linux-v4.19/Documentation/media/uapi/mediactl/
Dmedia-controller-model.rst25 interact with other entities. Data (not restricted to video) produced
/Linux-v4.19/Documentation/devicetree/bindings/arm/msm/
Dqcom,saw2.txt7 the PMIC. It can also be wired up to interact with other processors in the
/Linux-v4.19/Documentation/ABI/testing/
Dsysfs-firmware-gsmi24 for more information on how to interact with
Dsysfs-ocfs26 ocfs2-tools to interact with the filesystem.
/Linux-v4.19/drivers/staging/speakup/
DTODO6 system. It allows blind users to interact with applications on the
/Linux-v4.19/Documentation/admin-guide/
Dbug-bisect.rst48 - interact with git bisect by using either::
/Linux-v4.19/Documentation/virtual/kvm/arm/
Dhyp-abi.txt11 mode, but still needs to interact with it, allowing a built-in
/Linux-v4.19/drivers/clk/
DKconfig80 This driver uses SCMI Message Protocol to interact with the
90 This driver uses SCPI Message Protocol to interact with the
/Linux-v4.19/drivers/cpufreq/
DKconfig.arm53 This driver uses SCPI Message Protocol driver to interact with the
238 This driver uses SCMI Message Protocol driver to interact with the
/Linux-v4.19/drivers/hwtracing/intel_th/
DKconfig12 subdevices to interact with each other and hardware and for
/Linux-v4.19/Documentation/spi/
Dbutterfly19 SPI protocol drivers interact with the AVR, and could even let the AVR
/Linux-v4.19/Documentation/x86/
Dprotection-keys.txt28 There are 3 system calls which directly interact with pkeys:
/Linux-v4.19/Documentation/media/uapi/v4l/
Dvidioc-subdev-g-crop.rst66 applications querying the same sub-device would thus not interact with
Dvidioc-subdev-g-fmt.rst60 same sub-device would thus not interact with each other.
/Linux-v4.19/Documentation/driver-api/
Ds390-drivers.rst55 channel-attached devices, however, will never interact with the
/Linux-v4.19/drivers/usb/phy/
DKconfig52 interface to interact with USB 2.0 and USB 3.0 PHY that is part

123