URL
https://opencores.org/ocsvn/test_project/test_project/trunk
Subversion Repositories test_project
[/] [test_project/] [trunk/] [linux_sd_driver/] [drivers/] [hid/] [Kconfig] - Rev 62
Compare with Previous | Blame | View Log
## HID driver configuration#menuconfig HID_SUPPORTbool "HID Devices"depends on INPUTdefault y---help---Say Y here to get to see options for various computer-human interfacedevice drivers. This option alone does not add any kernel code.If you say N, all options in this submenu will be skipped and disabled.if HID_SUPPORTconfig HIDtristate "Generic HID support"depends on INPUTdefault y---help---A human interface device (HID) is a type of computer device thatinteracts directly with and takes input from humans. The term "HID"most commonly used to refer to the USB-HID specification, but otherdevices (such as, but not strictly limited to, Bluetooth) aredesigned using HID specification (this involves certain keyboards,mice, tablets, etc). This option compiles into kernel the genericHID layer code (parser, usages, etc.), which can then be used bytransport-specific HID implementation (like USB or Bluetooth).For docs and specs, see http://www.usb.org/developers/hidpage/If unsure, say Yconfig HID_DEBUGbool "HID debugging support"default y if !EMBEDDEDdepends on HID---help---This option lets the HID layer output diagnostics about its internalstate, resolve HID usages, dump HID fields, etc. Individual HID driversuse this debugging facility to output information about individual HIDdevices, etc.This feature is useful for those who are either debugging the HID parseror any HID hardware device.If unsure, say Nconfig HIDRAWbool "/dev/hidraw raw HID device support"depends on HID---help---Say Y here if you want to support HID devices (from the USBspecification standpoint) that aren't strictly user interfacedevices, like monitor controls and Uninterruptable Power Supplies.This module supports these devices separately using a separateevent interface on /dev/hidraw.There is also a /dev/hiddev configuration option in the USB HIDconfiguration menu. In comparison to hiddev, this device does not processthe hid events at all (no parsing, no lookups). This lets applicationsto work on raw hid events when they want to, and avoid using transport-specificuserspace libhid/libusb libraries.If unsure, say Y.source "drivers/hid/usbhid/Kconfig"endif # HID_SUPPORT
