Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 62fc6a9f authored by Harry Cutts's avatar Harry Cutts
Browse files

uinput: note that UI_SET_EVBIT configuration is always needed 

If you don't add a UI_SET_EVBIT configuration entry to a register
command, the other configuration entries will just be silently ignored.
This isn't very obvious to someone not familiar with the uinput Kernel
API, so let's add a note about it in the README.

Bug: 245989146
Test: check rendering in Gitiles
Flag: DOCS_ONLY
Change-Id: I290bafb276a8caf0639f062eff16aeff32bac8d0
parent 86f10baf

cmds/uinput/README.md

+5 −0
Original line number Diff line number Diff line
@@ -83,6 +83,11 @@ control values to be sent to the uinput device, which depends on the control cod 
Due to the sequential nature in which this is parsed, the `type` field must be specified before

the `data` field in this JSON Object.



Every `register` command will need a `"UI_SET_EVBIT"` configuration entry that lists what types of

axes it declares. This entry should be the first in the list. For example, if the uinput device has

`"UI_SET_KEYBIT"` and `"UI_SET_RELBIT"` configuration entries, it will also need a `"UI_SET_EVBIT"`

entry with data of `["EV_KEY", "EV_REL"]` or the other configuration entries will be ignored.



`ff_effects_max` must be provided if `UI_SET_FFBIT` is used in `configuration`.



`abs_info` fields are provided to set the device axes information. It is an array of below objects: