forked from Minki/linux
751d17e23a
In the original HID sensor hub firmwares all Named array enums were to 0-based. But the most recent hub implemented as 1-based, because of the implementation by one of the major OS vendor. Using logical minimum for the field as the base of enum. So we add logical minimum to the selector values before setting those fields. Some sensor hub FWs already changed logical minimum from 0 to 1 to reflect this and hope every other vendor will follow. There is no easy way to add a common HID quirk for NAry elements, even if the standard specifies these field as NAry, the collection used to describe selectors is still just "logical". Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> Signed-off-by: Jonathan Cameron <jic23@kernel.org>
29 lines
882 B
Plaintext
29 lines
882 B
Plaintext
#
|
|
# Hid Sensor common modules
|
|
#
|
|
menu "Hid Sensor IIO Common"
|
|
|
|
config HID_SENSOR_IIO_COMMON
|
|
tristate "Common modules for all HID Sensor IIO drivers"
|
|
depends on HID_SENSOR_HUB
|
|
select HID_SENSOR_IIO_TRIGGER if IIO_BUFFER
|
|
help
|
|
Say yes here to build support for HID sensor to use
|
|
HID sensor common processing for attributes and IIO triggers.
|
|
There are many attributes which can be shared among multiple
|
|
HID sensor drivers, this module contains processing for those
|
|
attributes.
|
|
|
|
config HID_SENSOR_IIO_TRIGGER
|
|
tristate "Common module (trigger) for all HID Sensor IIO drivers"
|
|
depends on HID_SENSOR_HUB && HID_SENSOR_IIO_COMMON
|
|
select IIO_TRIGGER
|
|
help
|
|
Say yes here to build trigger support for HID sensors.
|
|
Triggers will be send if all requested attributes were read.
|
|
|
|
If this driver is compiled as a module, it will be named
|
|
hid-sensor-trigger.
|
|
|
|
endmenu
|