summaryrefslogtreecommitdiffstats
path: root/include/dt-bindings
diff options
context:
space:
mode:
authorPhilip Chen <philipchen@chromium.org>2021-02-22 21:05:04 -0800
committerDmitry Torokhov <dmitry.torokhov@gmail.com>2021-02-22 21:22:15 -0800
commit820c8727956da82b7a841c299fabb2fdca9a37d4 (patch)
treeda79002995173e09e7799e9e6a4f448823fc5ce2 /include/dt-bindings
parent311a27da6271394afdca5773f4272eb6f48fae2d (diff)
downloadlinux-820c8727956da82b7a841c299fabb2fdca9a37d4.tar.bz2
Input: cros-ec-keyb - expose function row physical map to userspace
The top-row keys in a keyboard usually have dual functionalities. E.g. A function key "F1" is also an action key "Browser back". Therefore, when an application receives an action key code from a top-row key press, the application needs to know how to correlate the action key code with the function key code and do the conversion whenever necessary. Since the userpace already knows the key scanlines (row/column) associated with a received key code. Essentially, the userspace only needs a mapping between the key row/column and the matching physical location in the top row. So, enhance the cros-ec-keyb driver to create such a mapping and expose it to userspace in the form of a function_row_physmap attribute. The attribute would be a space separated ordered list of row/column codes for the keys in the function row, in a left-to-right order. The attribute will only be present when the device has a custom design for the top-row keys. Signed-off-by: Philip Chen <philipchen@chromium.org> Reviewed-by: Stephen Boyd <swboyd@chromium.org> Link: https://lore.kernel.org/r/20210115122412.v7.2.I6542d7d9d0b246e7079bb16b41e697b2ac4b4e39@changeid Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Diffstat (limited to 'include/dt-bindings')
0 files changed, 0 insertions, 0 deletions