Searched refs:userio (Results 1 – 7 of 7) sorted by relevance
57 struct userio_device *userio = id->port_data; in userio_device_write() local60 spin_lock_irqsave(&userio->buf_lock, flags); in userio_device_write()62 userio->buf[userio->head] = val; in userio_device_write()63 userio->head = (userio->head + 1) % USERIO_BUFSIZE; in userio_device_write()65 if (userio->head == userio->tail) in userio_device_write()69 spin_unlock_irqrestore(&userio->buf_lock, flags); in userio_device_write()71 wake_up_interruptible(&userio->waitq); in userio_device_write()78 struct userio_device *userio; in userio_char_open() local80 userio = kzalloc(sizeof(struct userio_device), GFP_KERNEL); in userio_char_open()81 if (!userio) in userio_char_open()[all …]
35 obj-$(CONFIG_USERIO) += userio.o
312 subsystem accessible under char device 10:240 - /dev/userio. Using318 called userio.
4 The userio Protocol19 of them. userio accomplishes this by allowing any privileged userspace program26 In order to interact with the userio kernel module, one simply opens the27 /dev/userio character device in their applications. Commands are sent to the29 driver is read as-is from the /dev/userio device. All of the structures and30 macros you need to interact with the device are defined in <linux/userio.h> and36 The struct used for sending commands to /dev/userio is as follows::44 of the USERIO_CMD macros defined in <linux/userio.h>. ``data`` is the argument53 To close the virtual serio port, just close /dev/userio.81 The userio userspace tools are able to record PS/2 devices using some of the[all …]
22 userio
376 240 = /dev/userio Serio driver testing device
22945 F: drivers/input/serio/userio.c22946 F: include/uapi/linux/userio.h
