nuttx-apps/system/kbd/Kconfig
Jorge Guzman a8e6021c6e system/kbd: add a keyboard dump that reads any keyboard
The hidkbd and keyboard examples do the same thing for one kind of
keyboard each:  hidkbd reads a USB HID keyboard as a byte stream, and
keyboard reads an upper half keyboard as events.  Neither works with the
other, so bringing up a new keyboard means picking the right example
first, and there is no answer for somebody whose keyboard is neither.

Every keyboard registered with keyboard_register() is read the same way,
so one tool covers them all:  USB HID, matrix, simulator, virtio, VNC.

The payload follows INPUT_KEYBOARD_BYTESTREAM rather than a switch of
its own.  An application has no business knowing what hardware is behind
the device, and a build cannot mix the two formats anyway.

The two examples stay for now.  They are what the in-tree configurations
still name, and removing them has to wait until those configurations
have been moved over.

Signed-off-by: Jorge Guzman <jorge.gzm@gmail.com>
2026-08-02 18:36:37 +08:00

38 lines
918 B
Text

#
# For a description of the syntax of this configuration file,
# see the file kconfig-language.txt in the NuttX tools repository.
#
config SYSTEM_KBD
tristate "Keyboard dump"
default n
depends on INPUT_KEYBOARD
---help---
Dump what a keyboard reports. This reads any keyboard registered
with keyboard_register(), whatever the hardware behind it is, so it
is the tool to reach for when bringing up a new keyboard.
Replaces the hidkbd and keyboard examples, which did the same thing
for one kind of keyboard each.
if SYSTEM_KBD
config SYSTEM_KBD_PROGNAME
string "Program name"
default "kbd"
config SYSTEM_KBD_PRIORITY
int "Task priority"
default 100
config SYSTEM_KBD_STACKSIZE
int "Task stack size"
default DEFAULT_TASK_STACKSIZE
config SYSTEM_KBD_DEVPATH
string "Keyboard device path"
default "/dev/kbd0"
---help---
The keyboard to read when none is named on the command line.
endif