| /linux/drivers/input/joystick/ |
| H A D | interact.c | 34 struct interact { struct
111 struct interact *interact = gameport_get_drvdata(gameport); in interact_poll() local
112 struct input_dev *dev = interact->dev; in interact_poll()
116 interact->reads++; in interact_poll()
118 if (interact_read_packet(interact->gameport, interact->length, data) < interact->length) { in interact_poll()
119 interact->bads++; in interact_poll()
123 data[i] <<= INTERACT_MAX_LENGTH - interact->length; in interact_poll()
125 switch (interact->type) { in interact_poll()
166 struct interact *interact = input_get_drvdata(dev); in interact_open() local
168 gameport_start_polling(interact->gameport); in interact_open()
[all …]
|
| H A D | Makefile | 23 obj-$(CONFIG_JOYSTICK_INTERACT) += interact.o
|
| /linux/Documentation/security/tpm/ |
| H A D | tpm_ftpm_tee.rst | 12 environment. The driver allows programs to interact with the TPM in the same
13 way they would interact with a hardware TPM.
|
| H A D | tpm_vtpm_proxy.rst | 15 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
|
| H A D | xen-tpmfront.rst | 15 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/Documentation/input/ |
| H A D | userio.rst | 20 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/Documentation/admin-guide/acpi/ |
| H A D | index.rst | 5 Here we document in detail how to interact with various mechanisms in
|
| /linux/arch/arm/boot/dts/broadcom/ |
| H A D | bcm2835-rpi-common.dtsi | 4 * bcm2835, bcm2836 and bcm2837 implementations that interact with RPi's
|
| /linux/Documentation/mm/ |
| H A D | page_cache.rst | 8 interact with filesystems. It can be bypassed (e.g. with O_DIRECT),
|
| /linux/drivers/platform/x86/intel/int1092/ |
| H A D | Kconfig | 9 to SAR driver. The front end application in userspace will interact with SAR
|
| /linux/drivers/accessibility/speakup/ |
| H A D | TODO | 6 system. It allows blind users to interact with applications on the
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | index.rst | 21 Here we document in detail how to interact with various mechanisms in
|
| H A D | shrinker_debugfs.rst | 7 and interact with them.
|
| /linux/drivers/phy/socionext/ |
| H A D | Kconfig | 14 on UniPhier SoCs. This driver provides interface to interact
|
| /linux/drivers/staging/fieldbus/anybuss/ |
| H A D | Kconfig | 33 so userspace can interact with it via the fieldbus_dev userspace
|
| /linux/drivers/soc/fsl/ |
| H A D | Kconfig | 31 buffer management facilities for software to interact with
|
| /linux/drivers/s390/char/ |
| H A D | Kconfig | 103 Using IOCTLs one can interact with the UV.
158 Select this option if you want to be able to interact with the control
|
| /linux/Documentation/driver-api/ |
| H A D | vfio-pci-device-specific-driver-acceptance.rst | 19 variants may interact with parent devices (ex. SR-IOV PF in support of
|
| /linux/Documentation/userspace-api/media/mediactl/ |
| H A D | media-controller-model.rst | 25 interact with other entities. Data (not restricted to video) produced
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-firmware-gsmi | 24 for more information on how to interact with
|
| /linux/Documentation/devicetree/bindings/interconnect/ |
| H A D | interconnect.txt | 43 components it has to interact with.
|
| /linux/Documentation/gpu/amdgpu/ |
| H A D | driver-core.rst | 24 their interface to interact with those common components. For things
86 provides the driver interface to interact with the GFX/Compute engine.
|
| /linux/Documentation/bpf/libbpf/ |
| H A D | libbpf_overview.rst | 15 * Provides high-level and low-level APIs for user space programs to interact
120 libbpf provides BPF-side APIs that BPF programs can use to interact with the
123 debugging messages, get the time since the system was booted, interact with BPF
|
| /linux/drivers/cpufreq/ |
| H A D | Kconfig.arm | 55 This driver uses SCPI Message Protocol driver to interact with the
202 This driver uses SCMI Message Protocol driver to interact with the
|
| /linux/drivers/hwtracing/intel_th/ |
| H A D | Kconfig | 13 subdevices to interact with each other and hardware and for
|