1. 03 Dec, 2016 1 commit
  2. 23 Oct, 2016 2 commits
  3. 27 Sep, 2016 1 commit
  4. 05 Jul, 2016 2 commits
  5. 30 Jun, 2016 1 commit
  6. 11 Jun, 2016 3 commits
  7. 04 May, 2016 1 commit
  8. 20 Mar, 2016 2 commits
  9. 12 Mar, 2016 1 commit
  10. 05 Mar, 2016 3 commits
  11. 23 Jan, 2016 3 commits
  12. 19 Dec, 2015 2 commits
  13. 25 Oct, 2015 1 commit
    • Martin Kepplinger's avatar
      iio: mma8452: support either of the available interrupt pins · d2a3e093
      Martin Kepplinger authored
      This change is important in order for everyone to be easily able to use the
      driver for one of the supported accelerometer chips!
      Until now, the driver blindly assumed that the INT1 interrupt line is wired
      on a user's board. But these devices have 2 interrupt lines and can route
      their interrupt sources to one of them. Now, if "INT2" is found and matches
      i2c_client->irq, INT2 will be used.
      The chip's default actually is INT2, which is why probably many boards will
      have it wired and can make use of this.
      Of course, this also falls back to assuming INT1, so for existing users
      nothing will break. The new functionality is described in the bindings doc.
      Signed-off-by: default avatarMartin Kepplinger <martin.kepplinger@theobroma-systems.com>
      For the binding: Acked-by: Rob Herring <robh@kernel.org>
      Signed-off-by: default avatarJonathan Cameron <jic23@kernel.org>
  14. 23 Sep, 2015 6 commits
  15. 08 Aug, 2015 6 commits
  16. 02 Aug, 2015 1 commit
    • Javier Martinez Canillas's avatar
      iio: Export OF module alias information in missing drivers · 119c4fce
      Javier Martinez Canillas authored
      The I2C core always reports the MODALIAS uevent as "i2c:<client name"
      regardless if the driver was matched using the I2C id_table or the
      of_match_table. So technically there's no need for a driver to export
      the OF table since currently it's not used.
      In fact, the I2C device ID table is mandatory for I2C drivers since
      a i2c_device_id is passed to the driver's probe function even if the
      I2C core used the OF table to match the driver.
      And since the I2C core uses different tables, OF-only drivers needs to
      have duplicated data that has to be kept in sync and also the dev node
      compatible manufacturer prefix is stripped when reporting the MODALIAS.
      To avoid the above, the I2C core behavior may be changed in the future
      to not require an I2C device table for OF-only drivers and report the
      OF module alias. So, it's better to also export the OF table to prevent
      breaking module autoloading if that happens.
      Signed-off-by: default avatarJavier Martinez Canillas <javier@osg.samsung.com>
      Signed-off-by: default avatarJonathan Cameron <jic23@kernel.org>
  17. 19 Jul, 2015 1 commit
  18. 07 Jun, 2015 3 commits