Lines Matching refs:can

16 and also the individual data fields. Each sensor can have variable number of
18 example a part of report descriptor can look like:
47 for different sensors. For example an accelerometer can send X,Y and Z data, whereas
48 an ambient light sensor can send illumination data.
61 function will be called. So an accelerometer processing driver can register
64 The core driver provides a set of APIs which can be used by the processing
71 the report and get the indexes of the fields and also can get events. This driver
72 can use IIO interface to use the standard ABI defined for a type of sensor.
79 Each processing driver can use this structure to set some callbacks.
83 	int (*send_event)(..): One complete event is received which can have
107 A processing driver can look for some field of interest and check if it exists
109 so that fields can be set or get individually.
119 sensor_hub_input_get_attribute_info before, then it can directly set that individual
128 sensor_hub_input_get_attribute_info before, then it can directly get that individual
137 accelerometer wants to poll X axis value, then it can call this function with
138 the usage id of X axis. HID sensors can provide events, so this is not necessary
154 This allows some differentiating use cases, where vendor can provide applications.
212 By default sensor can be power gated. To enable sysfs attribute "enable" can be
216 Once enabled and powered on, sensor can report value using HID reports.
222 Each reports can be of variable length preceded by a header. This header