From: Jonathan Cameron <jic23@kernel.org>
To: Matt Ranostay <mranostay@gmail.com>,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org
Cc: matt.porter@linaro.org, pantelis.antoniou@gmail.com
Subject: Re: [PATCH v7 0/2] AS3935 lightning sensor support
Date: Sat, 22 Feb 2014 12:50:17 +0000 [thread overview]
Message-ID: <53089D09.1020203@kernel.org> (raw)
In-Reply-To: <1392179475-2611-1-git-send-email-mranostay@gmail.com>
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
>
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Cameron <jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Matt Ranostay <mranostay-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: matt.porter-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
pantelis.antoniou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH v7 0/2] AS3935 lightning sensor support
Date: Sat, 22 Feb 2014 12:50:17 +0000 [thread overview]
Message-ID: <53089D09.1020203@kernel.org> (raw)
In-Reply-To: <1392179475-2611-1-git-send-email-mranostay-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
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
>
next prev parent reply other threads:[~2014-02-22 12:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 4:31 [PATCH v7 0/2] AS3935 lightning sensor support Matt Ranostay
2014-02-12 4:31 ` Matt Ranostay
2014-02-12 4:31 ` [PATCH v7 1/2] iio:as3935: Add DT binding docs for AS3935 driver Matt Ranostay
2014-02-12 4:31 ` [PATCH v7 2/2] iio: Add AS3935 lightning sensor support Matt Ranostay
2014-03-06 19:04 ` Jonathan Cameron
2014-03-06 19:04 ` Jonathan Cameron
2014-03-11 3:01 ` Matt Ranostay
2014-03-11 3:01 ` Matt Ranostay
2014-02-22 12:50 ` Jonathan Cameron [this message]
2014-02-22 12:50 ` [PATCH v7 0/2] " Jonathan Cameron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53089D09.1020203@kernel.org \
--to=jic23@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.porter@linaro.org \
--cc=mranostay@gmail.com \
--cc=pantelis.antoniou@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.