| /linux/drivers/input/joystick/ |
| A D | interact.c | 37 struct interact { struct
114 struct interact *interact = gameport_get_drvdata(gameport); in interact_poll() local
119 interact->reads++; in interact_poll()
121 if (interact_read_packet(interact->gameport, interact->length, data) < interact->length) { in interact_poll()
169 struct interact *interact = input_get_drvdata(dev); in interact_open() local
181 struct interact *interact = input_get_drvdata(dev); in interact_close() local
192 struct interact *interact; in interact_connect() local
198 interact = kzalloc(sizeof(struct interact), GFP_KERNEL); in interact_connect()
274 kfree(interact); in interact_connect()
280 struct interact *interact = gameport_get_drvdata(gameport); in interact_disconnect() local
[all …]
|
| A D | Makefile | 23 obj-$(CONFIG_JOYSTICK_INTERACT) += interact.o
|
| /linux/Documentation/security/tpm/ |
| 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.
|
| 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
|
| 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/ |
| 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/ |
| A D | index.rst | 5 Here we document in detail how to interact with various mechanisms in
|
| /linux/arch/arm/boot/dts/ |
| A D | bcm2835-rpi-common.dtsi | 4 * bcm2835, bcm2836 and bcm2837 implementations that interact with RPi's
|
| /linux/drivers/platform/x86/intel/int1092/ |
| A D | Kconfig | 9 to SAR driver. The front end application in userspace will interact with SAR
|
| /linux/drivers/accessibility/speakup/ |
| A D | TODO | 6 system. It allows blind users to interact with applications on the
|
| /linux/Documentation/admin-guide/mm/ |
| A D | index.rst | 22 Here we document in detail how to interact with various mechanisms in
|
| /linux/drivers/staging/fieldbus/anybuss/ |
| A D | Kconfig | 33 so userspace can interact with it via the fieldbus_dev userspace
|
| /linux/drivers/phy/socionext/ |
| A D | Kconfig | 14 on UniPhier SoCs. This driver provides interface to interact
|
| /linux/Documentation/devicetree/bindings/power/supply/ |
| A D | twl4030-charger.yaml | 10 The battery charger needs to interact with the USB phy in order to know when
|
| /linux/Documentation/devicetree/bindings/iio/adc/ |
| A D | adc.yaml | 51 device design and can interact with other characteristics such as
|
| /linux/drivers/staging/vc04_services/ |
| A D | Kconfig | 34 by userspace libraries and testing tools to interact with VideoCore, via
|
| /linux/drivers/soc/fsl/ |
| A D | Kconfig | 30 buffer management facilities for software to interact with
|
| /linux/Documentation/userspace-api/media/mediactl/ |
| A D | media-controller-model.rst | 25 interact with other entities. Data (not restricted to video) produced
|
| /linux/Documentation/devicetree/bindings/arm/msm/ |
| A D | qcom,saw2.txt | 7 the PMIC. It can also be wired up to interact with other processors in the
|
| /linux/Documentation/ABI/testing/ |
| A D | sysfs-firmware-gsmi | 24 for more information on how to interact with
|
| /linux/Documentation/admin-guide/ |
| A D | bug-bisect.rst | 48 - interact with git bisect by using either::
|
| /linux/Documentation/devicetree/bindings/interconnect/ |
| A D | interconnect.txt | 43 components it has to interact with.
|
| /linux/sound/soc/ |
| A D | Kconfig | 53 Do note that it creates fake playback devices which do not interact
|
| /linux/drivers/phy/ |
| A D | Kconfig | 61 interface to interact with USB GEN-II and USB 3.x PHY that is part
|
| /linux/Documentation/x86/ |
| A D | sva.rst | 104 thread can interact with a device. Threads that belong to the same
134 * The single process-wide PASID is used by all threads to interact
157 Traditionally, in order for userspace applications to interact with hardware,
|