However we'll have to dead reckon the timing without an interrupt. That should be fine, as just configure it to max say 3/4 of the time to fill it. > > There is also a SYSTEM_HISTORY_CTRL register, which configures the HW buffer, > like setting which data to capture (ALS/RANGE) as well as turning the > buffer on/off. > Where should all this configuration be done? > Should it be default or have some sysfs attribute associated with it? So if it were a conventional fifo it would mostly be hidden behind the software fifo and just act as an optimization of the data capture. A few things are exposed though as can make a difference to how you configure the device such as the size of the hardware fifo and the hwfifo threshold (affects latency of data capture). However sounds like you don't have that here. So challenging feature to support. > > Thanks, > Abhash
