summaryrefslogtreecommitdiff
path: root/sys/dev/evdev
AgeCommit message (Collapse)Author
2025-12-01evdev: Sync event codes with Linux kernel 6.18Vladimir Kondratyev
MFC after: 1 month
2025-12-01evdev: Allow setting of character device ownership and access modeVladimir Kondratyev
by device driver. That is required as game pad and joystick events have to be accessible by ordinary users. MFC after: 1 month
2025-10-18knotes: kqueue: handle copy for trivial filtersKonstantin Belousov
Reviewed by: markj Tested by: pho Sponsored by: The FreeBSD Foundation MFC after: 2 weeks Differential revision: https://reviews.freebsd.org/D52045
2025-03-07sysmouse(4): Add wsp(4)-style T-Axis reporting.Joshua Rogers
Neither the ums(4) nor psm(4) reporting can be used by the wsp(4) driver, as they rely on static-length movements, while wsp(4) may need to scroll in large amounts per evdev event push. This style uses a false button-5 press as an indicator that the z-axis movement is a horizontal scroll, otherwise a vertical scroll. Signed-off-by: Joshua Rogers <Joshua@Joshua.Hu>
2024-11-26kern: Make fileops and filterops tables const where possibleMark Johnston
No functional change intended. MFC after: 1 week
2023-11-02evdev: Sync event codes with Linux kernel 6.5Vladimir Kondratyev
MFC after: 1 week
2023-08-16sys: Remove $FreeBSD$: two-line .h patternWarner Losh
Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/
2022-11-19evdev: Extend EVIOCGRAB ioctl scope to cover kbd interfaceVladimir Kondratyev
of various keyboard drivers. EVIOCGRAB ioctl execution on /dev/input/event# device node gains exclusive access to this device to caller. It is used mostly for development purposes and remote control software. See e.g. https://reviews.freebsd.org/D30020 which is the reason of creation of this change. Keyboard grabbing is disabled in KDB and during panics. MFC with: 4a0db5e2920c Tested by: corvink Differential revision: https://reviews.freebsd.org/D30542
2022-11-18evdev: Extend EVIOCGRAB ioctl scope to cover sysmouse interfaceVladimir Kondratyev
of psm(4), ums(4) and sysmouse(4) drivers. EVIOCGRAB ioctl execution on /dev/input/event# device node gains exclusive access to this device to caller. It is used mostly for development purposes and remote control software. See e.g. https://reviews.freebsd.org/D30020 which is the reason of creation of this change. MFC after: 2 weeks Tested by: corvink Differential revision: https://reviews.freebsd.org/D30542
2022-07-20atkbd(4): Fix "hancha" and "han/yong" korean keys handling.Vladimir Kondratyev
The Korean keyboard has two keys, the Korean/Chinese and the Korean/English toggles, that generate scancodes 0xF1 and 0xF2 (respectively) when pressed, and nothing when released. They do not repeat. As Hanyong/Hancha keys are generally greater than 0x80, which is generally considered a release key, add extra preceding press key event to generate press/release pair. Swap Hanyong/Hancha key codes to match reality. Reported by: Warioburn <warioburn@yahoo.co.jp> PR: 265260 MFC after: 1 week
2021-10-02evdev: Fix a typo in a commitGordon Bergling
- s/prefered/preferred/ MFC after: 3 days
2021-09-15evdev: Add parentheses around '-' expression in operand of '&'.John Baldwin
This fixes a -Wparentheses error with GCC 9. Reviewed by: wulf Differential Revision: https://reviews.freebsd.org/D31947
2021-09-02evdev: Do not export multitouch functions which are unused outside evdevVladimir Kondratyev
2021-08-25evdev: Add support for automatic MT protocol type A to type B conversion.Vladimir Kondratyev
MFC after: 2 weeks
2021-08-25evdev: Add implicit mode for touch tracking.Vladimir Kondratyev
In implicit mode assignment of slot number and tracking id is performed automatically on each synchronization requested by device driver. This is done with creation of intermediate buffer for multitouch events. This buffer holds untracked events until synchronization is requested by device driver. It is needed as touch assigment requires knowledges of all touch positions pushed in current and previous reports. MFC after: 2 weeks
2021-08-25evdev: Import support for touch-tracking.Vladimir Kondratyev
Touch tracking is a process of assignment of unique trackingID to each initiated contact on the surface. Keeping the trackingIDs persistent across multitouch reports requires solving of so called Euclidian Bipartite Matching problem. This commit imports EBM-solver implementation based on Dinitz-Kronrod algorithm to find minimum cost matching between contacts listed in two consecutive reports. Obtained from: OpenBSD MFC after: 2 weeks
2021-08-25evdev: Make MT tracking IDs monotonically increasing sequence.Vladimir Kondratyev
MFC after: 2 weeks
2021-08-25evdev: Give short aliases to items of evdev_mt_slot arrayVladimir Kondratyev
with using of unioned anonymous structure. Access to the same data by using different members of union generally works despite it is not supported by C specs. Also add helper function to report entire slot state. MFC after: 2 weeks
2021-08-25evdev: Normalize width and pressure of single touch compat eventsVladimir Kondratyev
to match Synaptics touchpad reporting range. MFC after: 2 weeks
2021-08-25evdev: force no fuzz for autogenerated single touch compat events.Vladimir Kondratyev
As fuzz has already been applied on multitouch event processing. This allows to remove existing workaround for double fuzz procesing. MFC after: 2 weeks
2021-08-25evdev: Send first active rather than 0-th slot state as ST reportVladimir Kondratyev
MFC after: 2 weeks
2021-08-25evdev: Use bitsets to track active touches and slots changed in current reportVladimir Kondratyev
Obtained from: OpenBSD MFC after: 2 weeks
2021-08-25evdev: Multitouch code style changes.Vladimir Kondratyev
1. Move touch count reporting helpers to utils. They are not multitouch. 2. Use evdev_mt prefix for private multitouch support routines. 3. Use int instead of int32_t where fixed size is not required. 4. Export some internal functions. This change should be no-op. MFC after: 2 weeks
2021-08-17evdev: Use bit_foreach helper macroVladimir Kondratyev
for traversing all bits set in the bitstring(9). While here move bit_change() definition to common header. MFC after: 1 week
2021-08-16evdev: Do not check maximal contact number for MT initializationVladimir Kondratyev
This allows singletouch devices which use multitouch protocols to work. Reported by: Mark Kane <mark_AT_kane_DOT_mn> MFC after: 1 week
2021-01-20evdev: Make variable-size ioctls return actual length of copyouted dataVladimir Kondratyev
on success instead of 0 to match Linux. Imprivata binary depends on this. Submitted by: Shunchao Hu <ankohuu_outlook.com> Reviewed by: wulf Differential revision: https://reviews.freebsd.org/D28218
2021-01-14hid: Add missing input enter/exit epoch pairs.Vladimir Kondratyev
This was affecting unloading keyboard driver and kdb-related code.
2021-01-08evdev: Implement fuzz.Vladimir Kondratyev
Fuzz is used to filter noise from the event stream. Upcoming gamepad drivers use it. Reviewed by: hselasky (as part of D27993)
2021-01-08evdev: Allow open() handler to be interrupted by a signalVladimir Kondratyev
It is possible that the client list lock is taken by other process for too long due to e.g. IO timeouts. Allow user to terminate open() in this case. Reviewed by: markj (as part of D27865)
2021-01-08evdev: Make open(2) and close(3) handlers sleepable.Vladimir Kondratyev
At the beginning of evdev there was a LOR between hardware driver's and evdev client list locks as they were taken in different order at driver's interrupt and evdev open()/close() handlers. The LOR was fixed with introduction of evdev_register_mtx() function which allowed to use a hardware driver's lock as evdev client list lock. While this works good with PS/2 and USB, this does not work with I2C. Unlike PS/2 and USB, I2C open()/close() handlers do unbound sleeps while waiting for I2C bus to release and while performing IO. This change uses epoch(9) for traversing evdev client list in interrupt handler to avoid the LOR thus making possible to convert evdev client list lock to sleepable sx. While here add brief locking protocol description. Reviewed by: markj Differential revision: https://reviews.freebsd.org/D27865
2021-01-08evdev: Remove useless "initial value" parameter from evdev_support_abs()Vladimir Kondratyev
It can not be used for setting of state of multitouch events. If necessary, use evdev_push_event() instead of it.
2020-11-09kqueue: save space by using only one func pointer for assertionsMateusz Guzik
Notes: svn path=/head/; revision=367498
2020-10-08Allow evdev's rcpt_mask and sysmouse_t_axis parameters to be specified inHans Petter Selasky
/boot/loader.conf . MFC after: 1 week Sponsored by: Mellanox Technologies // NVIDIA Networking Notes: svn path=/head/; revision=366533
2020-06-25atkbd/evdev: recognize the Chromebook menu key as F13 like Linux does.Vladimir Kondratyev
This is the key on the right side of the function keys, with the "hamburger menu" icon on it. Submitted by: GregV <greg@unrelenting.technology> MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D25390 Notes: svn path=/head/; revision=362599
2020-06-17evdev: Add AT translated set1 scancodes for 'Eisu' & 'Kana' keys.Vladimir Kondratyev
PR: 247292 Submitted by: Yuichiro NAITO <naito.yuichiro@gmail.com> MFC after: 1 week Notes: svn path=/head/; revision=362260
2020-05-04[evdev] Sync event codes with Linux kernel 5.6Vladimir Kondratyev
MFC after: 2 weeks Notes: svn path=/head/; revision=360625
2020-05-04[evdev] Add AT translated set1 scancodes for F-unlocked F1-12 keys.Vladimir Kondratyev
"F lock" is a switch between two sets of scancodes for function keys F1-F12 found on some Logitech and Microsoft PS/2 keyboards [1]. When "F lock" is pressed, then F1-F12 act as function keys and produce usual keyscans for these keys. When "F lock" is depressed, F1-F12 produced the same keyscans but prefixed with E0. Some laptops use [2] E0-prefixed F1-F12 scancodes for non-standard keys. [1] https://www.win.tue.nl/~aeb/linux/kbd/scancodes-6.html [2] https://reviews.freebsd.org/D21565 MFC after: 2 weeks Notes: svn path=/head/; revision=360624
2020-04-20Fix kern.evdev.rcpt_mask on powerpcNiclas Zeising
In r360126, I meant to have a different mask only on powerpc, not powerpc64. Update the check to check that we're not compiling for powerpc64. Reported by: jhibbits Approved by: wulf (implicit) MFC after: 2 weeks X-MFC-Note: 12 only X-MFC-With: r360126 Differential Revision: D24370 (followup) Notes: svn path=/head/; revision=360132
2020-04-20Change kern.evdev.rcpt_mask to 12 by defaultNiclas Zeising
Change kern.evdev.rcpt_mask from 3 to 12 by default. This makes us much more evdev-friendly, and will prevent everyone using xorg and wayland with evdev devices (the default) from needing to change this locally. powerpc32 still uses the old value for the keyboard part, becaues the adb keyboard driver used there is not evdev compatible. Reviewed by: wulf Approved by: wulf MFC after: 2 weeks X-MFC-Note: 12 only Relnotes: yes Differential Revision: https://reviews.freebsd.org/D24370 Notes: svn path=/head/; revision=360126
2020-04-19Use LIST_FOREACH_SAFE instead of LIST_FOREACH as we are removingXin LI
elements in the middle. This fixes a panic when detaching USB mouse. PR: 245732 Reviewed by: wulf MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D24500 Notes: svn path=/head/; revision=360104
2020-04-13[evdev] Use proper mutex reference in autorepeat callout initialization.Vladimir Kondratyev
This fixes panic occuring when evdev key autorepeat is enabled by driver which initializes evdev with external mutex. Notes: svn path=/head/; revision=359905
2020-03-29evdev: return error rather than zero-length data on blocked read()Vladimir Kondratyev
if blocked process has been woken up by evdev device destruction. MFC after: 2 weeks Notes: svn path=/head/; revision=359429
2020-03-29evdev: Add COMPAT_FREEBSD32 support for amd64 archVladimir Kondratyev
Incompatibility between i386 and amd64 evdev ABIs was caused by presence of 'struct timeval' in evdev protocol. Replace it with 'struct timeval32' for 32 bit binaries. Big-endian platforms may require additional work due to bitstr_t (array of unsigned longs) usage in ioctl interface. MFC after: 2 weeks Notes: svn path=/head/; revision=359428
2020-02-26Mark more nodes as CTLFLAG_MPSAFE or CTLFLAG_NEEDGIANT (17 of many)Pawel Biernacki
r357614 added CTLFLAG_NEEDGIANT to make it easier to find nodes that are still not MPSAFE (or already are but aren’t properly marked). Use it in preparation for a general review of all nodes. This is non-functional change that adds annotations to SYSCTL_NODE and SYSCTL_PROC nodes using one of the soon-to-be-required flags. Mark all obvious cases as MPSAFE. All entries that haven't been marked as MPSAFE before are by default marked as NEEDGIANT Approved by: kib (mentor, blanket) Commented by: kib, gallatin, melifaro Differential Revision: https://reviews.freebsd.org/D23718 Notes: svn path=/head/; revision=358333
2019-05-20Extract eventfilter declarations to sys/_eventfilter.hConrad Meyer
This allows replacing "sys/eventfilter.h" includes with "sys/_eventfilter.h" in other header files (e.g., sys/{bus,conf,cpu}.h) and reduces header pollution substantially. EVENTHANDLER_DECLARE and EVENTHANDLER_LIST_DECLAREs were moved out of .c files into appropriate headers (e.g., sys/proc.h, powernv/opal.h). As a side effect of reduced header pollution, many .c files and headers no longer contain needed definitions. The remainder of the patch addresses adding appropriate includes to fix those files. LOCK_DEBUG and LOCK_FILE_LINE_ARG are moved to sys/_lock.h, as required by sys/mutex.h since r326106 (but silently protected by header pollution prior to this change). No functional change (intended). Of course, any out of tree modules that relied on header pollution for sys/eventhandler.h, sys/lock.h, or sys/mutex.h inclusion need to be fixed. __FreeBSD_version has been bumped. Notes: svn path=/head/; revision=347984
2019-02-24Fix build when EVDEV_SUPPORT is option disabled after r344494Vladimir Kondratyev
MFC with: 344494 Notes: svn path=/head/; revision=344495
2019-02-24evdev: export event device properties through sysctl interfaceVladimir Kondratyev
A big security advantage of Wayland is not allowing applications to read input devices all the time. Having /dev/input/* accessible to the user account subverts this advantage. libudev-devd was opening the evdev devices to detect their types (mouse, keyboard, touchpad, etc). This don't work if /dev/input/* is inaccessible. With the kernel exposing this information as sysctls (kern.evdev.input.*), we can work w/o /dev/input/* access, preserving the Wayland security model. Submitted by: Greg V <greg@unrelenting.technology> Reviewed by: wulf, imp MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D18694 Notes: svn path=/head/; revision=344494
2018-11-25evdev: Fix pause key release event in AT keyboard set 1 to evdev xlat-or.Vladimir Kondratyev
MFC after: 2 weeks Notes: svn path=/head/; revision=340926
2018-10-27evdev: disable evdev if it is invoked from KDB or panic contextVladimir Kondratyev
This allow to prevent deadlock on entering KDB if one of evdev locks is already taken by userspace process. Also this change discards all but LED console events produced by KDB as unrelated to userspace. Tested by: dumbbell (as part of D15070) Objected by: bde (as 'KDB lock an already locked mutex' problem solution) MFC after: 1 month Notes: svn path=/head/; revision=339824
2018-10-27evdev: Use console lock as evdev lock for all supported keyboard drivers.Vladimir Kondratyev
Now evdev part of keyboard drivers does not take any locks if corresponding input/eventN device node is not opened by userland consumers. Do not assert console lock inside evdev to handle the cases when keyboard driver is called from some special single-threaded context like shutdown thread. Notes: svn path=/head/; revision=339823
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-19 16:27:35 +0000