Searched refs:userio (Results 1 – 7 of 7) sorted by relevance
60 userio->buf[userio->head] = val; in userio_device_write()61 userio->head = (userio->head + 1) % USERIO_BUFSIZE; in userio_device_write()63 if (userio->head == userio->tail) in userio_device_write()77 if (!userio) in userio_char_open()89 userio->serio->port_data = userio; in userio_char_open()110 kfree(userio); in userio_char_release()122 available = CIRC_CNT_TO_END(userio->head, userio->tail, in userio_fetch_data()126 memcpy(buf, &userio->buf[userio->tail], len); in userio_fetch_data()127 userio->tail = (userio->tail + len) % USERIO_BUFSIZE; in userio_fetch_data()166 userio->head != userio->tail); in userio_char_read()[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 …]
19 userio
376 240 = /dev/userio Serio driver testing device
25923 F: drivers/input/serio/userio.c25924 F: include/uapi/linux/userio.h