1. 03 Apr, 2015 10 commits
  2. 02 Apr, 2015 3 commits
  3. 01 Apr, 2015 21 commits
  4. 30 Mar, 2015 1 commit
  5. 29 Mar, 2015 5 commits
    • Martin Kepplinger's avatar
      5798cd23
    • Vianney le Clément de Saint-Marcq's avatar
      iio: mlx90614: Support devices with dual IR sensor · bad4d1a0
      Vianney le Clément de Saint-Marcq authored
      The model is detected by reading the EEPROM configuration during
      probing.
      Signed-off-by: default avatarVianney le Clément de Saint-Marcq <vianney.leclement@essensium.com>
      Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
      Signed-off-by: default avatarJonathan Cameron <jic23@kernel.org>
      bad4d1a0
    • Vianney le Clément de Saint-Marcq's avatar
      iio: mlx90614: Add symbols for accessible registers · 209c0069
      Vianney le Clément de Saint-Marcq authored
      Add symbols for all accessible RAM and EEPROM registers, as well as the
      sleep command and timings defined in the datasheet.
      Signed-off-by: default avatarVianney le Clément de Saint-Marcq <vianney.leclement@essensium.com>
      Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
      Signed-off-by: default avatarJonathan Cameron <jic23@kernel.org>
      209c0069
    • Octavian Purdila's avatar
      iio: bmc150_accel: add support for hardware fifo · 3bbec977
      Octavian Purdila authored
      We only advertise hardware fifo support if the I2C bus supports full
      I2C or smbus I2C block data reads since it is mandatory to read the
      full frame in one read (otherwise the rest of the frame is discarded).
      
      The hardware fifo is enabled only when triggers are not active because:
      
      (a) when using the any-motion trigger the user expects to see samples
      based on ROC events, but the fifo stores samples based on the sample
      frequency
      
      (b) the data-ready trigger is waking the CPU for for every sample, so
      using the hardware fifo does not have any benefit
      Signed-off-by: default avatarOctavian Purdila <octavian.purdila@intel.com>
      Reviewed-by: default avatarLars-Peter Clausen <lars@metafoo.de>
      Signed-off-by: default avatarJonathan Cameron <jic23@kernel.org>
      3bbec977
    • Octavian Purdila's avatar
      iio: add support for hardware fifo · f4f4673b
      Octavian Purdila authored
      Some devices have hardware buffers that can store a number of samples
      for later consumption. Hardware usually provides interrupts to notify
      the processor when the FIFO is full or when it has reached a certain
      watermark level. This helps with reducing the number of interrupts to
      the host processor and thus it helps decreasing the power consumption.
      
      This patch enables usage of hardware FIFOs for IIO devices in
      conjunction with software device buffers. When the hardware FIFO is
      enabled the samples are stored in the hardware FIFO. The samples are
      later flushed to the device software buffer when the number of entries
      in the hardware FIFO reaches the hardware watermark or when a flush
      operation is triggered by the user when doing a non-blocking read
      on an empty software device buffer.
      
      In order to implement hardware FIFO support the device drivers must
      implement the following new operations: setting and getting the
      hardware FIFO watermark level, flushing the hardware FIFO to the
      software device buffer. The device must also expose information about
      the hardware FIFO such it's minimum and maximum watermark and if
      necessary a list of supported watermark values. Finally, the device
      driver must activate the hardware FIFO when the device buffer is
      enabled, if the current device settings allows it.
      
      The software device buffer watermark is passed by the IIO core to the
      device driver as a hint for the hardware FIFO watermark. The device
      driver can adjust this value to allow for hardware limitations (such
      as capping it to the maximum hardware watermark or adjust it to a
      value that is supported by the hardware). It can also disable the
      hardware watermark (and implicitly the hardware FIFO) it this value is
      below the minimum hardware watermark.
      
      Since a driver may support hardware FIFO only when not in triggered
      buffer mode (due to different semantics of hardware FIFO sampling and
      triggered sampling) this patch changes the IIO core code to allow
      falling back to non-triggered buffered mode if no trigger is enabled.
      Signed-off-by: default avatarOctavian Purdila <octavian.purdila@intel.com>
      Reviewed-by: default avatarLars-Peter Clausen <lars@metafoo.de>
      Signed-off-by: default avatarJonathan Cameron <jic23@kernel.org>
      f4f4673b