Just a quick note to say I'm hold off on this in the hope for some feedback on my suggested interface for position devices that I sent in response to the previous version. I think lumping these under proximity devices is the wrong approach as that doesn't generalize well. On 12/02/14 04:31, Matt Ranostay wrote:
This series adds support for the AMS AS3935 lightning sensor that allows reporting back estimated storm distance and strike events. Chagges from v6 * Revised binding documents to not use the term "interrupts mapping" * Renamed tune-cap property to a more clear tuning-capacitor-pf Changes from v5 * SPI write cache-aligned issues fixed * Fixed mutex_unlock's being missed * Reports distance in meters instead of kilometers (1km steps) * tune_cap is now in picofarads and not a register value Matt Ranostay (2): iio:as3935: Add DT binding docs for AS3935 driver iio: Add AS3935 lightning sensor support .../ABI/testing/sysfs-bus-iio-proximity-as3935 | 18 + .../devicetree/bindings/iio/proximity/as3935.txt | 28 ++ .../devicetree/bindings/vendor-prefixes.txt | 1 + drivers/iio/Kconfig | 1 + drivers/iio/Makefile | 1 + drivers/iio/proximity/Kconfig | 19 + drivers/iio/proximity/Makefile | 6 + drivers/iio/proximity/as3935.c | 446 +++++++++++++++++++++ 8 files changed, 520 insertions(+) create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-proximity-as3935 create mode 100644 Documentation/devicetree/bindings/iio/proximity/as3935.txt create mode 100644 drivers/iio/proximity/Kconfig create mode 100644 drivers/iio/proximity/Makefile create mode 100644 drivers/iio/proximity/as3935.c
-- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
