HID Sensor Usage Tables - USB.org

93 HID Sensor Usages
};
HID_REPORT_COUNT(1),
HID_COLLECTION(Logical),
HID_USAGE_SENSOR_EVENT_UNKNOWN,
HID_USAGE_SENSOR_EVENT_STATE_CHANGED,
HID_USAGE_SENSOR_EVENT_PROPERTY_CHANGED,
HID_USAGE_SENSOR_EVENT_DATA_UPDATED,
HID_USAGE_SENSOR_EVENT_POLL_RESPONSE,
HID_USAGE_SENSOR_EVENT_CHANGE_SENSITIVITY,
HID_USAGE_SENSOR_EVENT_MAX_REACHED,
HID_USAGE_SENSOR_EVENT_MIN_REACHED,
HID_USAGE_SENSOR_EVENT_HIGH_THRESHOLD_CROSS_UPWARD,
HID_USAGE_SENSOR_EVENT_HIGH_THRESHOLD_CROSS_DOWNWARD,
HID_USAGE_SENSOR_EVENT_LOW_THRESHOLD_CROSS_UPWARD,
HID_USAGE_SENSOR_EVENT_LOW_THRESHOLD_CROSS_DOWNWARD,
HID_USAGE_SENSOR_EVENT_ZERO_THRESHOLD_CROSS_UPWARD,
HID_USAGE_SENSOR_EVENT_ZERO_THRESHOLD_CROSS_DOWNWARD,
HID_USAGE_SENSOR_EVENT_PERIOD_EXCEEDED,
HID_USAGE_SENSOR_EVENT_FREQUENCY_EXCEEDED,
HID_USAGE_SENSOR_EVENT_COMPLEX_TRIGGER,
HID_INPUT(Const_Arr_Abs),
HID_END_COLLECTION,
HID_USAGE_SENSOR_DATA_LIGHT_ILLUMINANCE,
HID_LOGICAL_MIN_8(0),
HID_LOGICAL_MAX_16(0xFF,0xFF),
HID_USAGE_SENSOR_UNITS_LUX,
HID_UNIT_EXPONENT(0x0F), // scale unit to provide 1 digit past the decimal point
HID_REPORT_SIZE(16),
HID_REPORT_COUNT(1),
HID_INPUT(Const_Var_Abs),
HID_USAGE_SENSOR_DATA_LIGHT_COLOR_TEMPERATURE,
HID_LOGICAL_MIN_8(0),
HID_LOGICAL_MAX_16(0xFF,0xFF),
HID_USAGE_SENSOR_UNITS_KELVIN,
HID_UNIT_EXPONENT(0),
HID_REPORT_SIZE(16),
HID_REPORT_COUNT(1),
HID_INPUT(Const_Var_Abs),
HID_USAGE_SENSOR_DATA_LIGHT_CHROMATICITY_X,
HID_LOGICAL_MIN_8(0),
HID_LOGICAL_MAX_16(0xFF,0xFF),
HID_USAGE_SENSOR_UNITS_NOT_SPECIFIED,
HID_UNIT_EXPONENT(0x0C), // scale unit to provide 4 digits past the decimal point
HID_REPORT_SIZE(16),
HID_REPORT_COUNT(1),
HID_INPUT(Const_Var_Abs),
HID_USAGE_SENSOR_DATA_LIGHT_CHROMATICITY_Y,
HID_LOGICAL_MIN_8(0),
HID_LOGICAL_MAX_16(65535),
HID_USAGE_SENSOR_UNITS_NOT_SPECIFIED,
HID_UNIT_EXPONENT(0x0C), // scale unit to provide 4 digits past the decimal point
HID_REPORT_SIZE(16),
HID_REPORT_COUNT(1),
HID_INPUT(Const_Var_Abs),
HID_END_COLLECTION, // end of ALS TLC
4.2.6 Custom Sensor
The Custom sensor provides a simple means by which platform driver support can be extended
dynamically without changes to the platform driver. The Custom sensor achieves this by encapsulating
datafields within known structures that are defined within the driver.
Use of a Custom sensor may be desireable in several circumstances:
1) The vendor may wish to extend the use of an existing device driver (one that must already support
the Custom sensor definition)
2) The vendor may wish to obfuscate the data being communicated by a sensor; without knowing the
mapping between the data and its encapsulated form, it is difficult for an application to determine
what data is being communcated by the sensor.
In order for an application to be able to make sense of these encapsulated datafields it must have fore
knowledge of the mapping between unencapsulated datafields and and their subsequent presentation by the
driver. Providing this mapping is the responsibility of the sensor vendor.
Provision is made for communicating three types of data: