There's a pair of "nub" devices on Pyra handheld PC (https://pyra-handheld.com/), and there's driver for nub, which is going to be reworked for upstreaming. While the device itself fits most to "joystick" category, the computer itself lacks touchpad and mouse buttons, and the existing driver is capable of switching between modes, in which it shows up like one of the following: - scrolling wheel, - mouse buttons set, - pointer updating its absolute position (graphic pad alike AFAIU), - pointer device behaving like actual joystick / pointing stick. Currently modes switching happens through r/w file in /proc, which is of couse going to be changed. I wonder if such mode switching mechanism is tolerable for inclusion to upstream kernel in this case. I'd like some advice how to rearrange the driver to save most of flexibility while matching upstream kernel conventions. I am especially interested in comments from subsystem maintainers. Existing driver: http://git.goldelico.com/?p=gta04-kernel.git;a=blob;f=drivers/input/misc/as5013.c;h=1bfb5243f692c0c0a9c93881968849cac947c92d;hb=refs/heads/work/hns/input/as5013 -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
