From: Jonathan Cameron <jic23@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Rob Herring <robh+dt@kernel.org>,
William Breathitt Gray <vilhelm.gray@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Pengutronix Kernel Team <kernel@pengutronix.de>,
David Jander <david@protonic.nl>,
Robin van der Gracht <robin@protonic.nl>,
linux-iio@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v8 0/2] add support for GPIO or IRQ based event counter
Date: Sun, 14 Mar 2021 16:55:04 +0000 [thread overview]
Message-ID: <20210314165504.536d9ba6@archlinux> (raw)
In-Reply-To: <20210301080401.22190-1-o.rempel@pengutronix.de>
On Mon, 1 Mar 2021 09:03:59 +0100
Oleksij Rempel <o.rempel@pengutronix.de> wrote:
> changes v8:
> - use use enum index instead of enum value for the counter function
> - register signal unconditionally and return error is signal revel is
> read
>
> changes v7:
> - make most of structs dynamically allocatable to assign IRQ based
> description to the signal
> - assign dev name instead for driver name to the IRQ
>
> changes v6:
> - rename it to interrupt-counter
> - driver fixes
> - device tree fixes
>
> changes v5:
> - rename it to event counter, since it support different event sources
> - make it work with gpio-only or irq-only configuration
> - update yaml binding
>
> changes v4:
> - use IRQ_NOAUTOEN to not enable IRQ by default
> - rename gpio_ from name pattern and make this driver work any IRQ
> source.
>
> changes v3:
> - convert counter to atomic_t
>
> changes v2:
> - add commas
> - avoid possible unhandled interrupts in the enable path
> - do not use of_ specific gpio functions
>
> Add support for GPIO based pulse counter. For now it can only count
> pulses. With counter char device support, we will be able to attach
> timestamps and measure actual pulse frequency.
>
> Never the less, it is better to mainline this driver now (before chardev
> patches go mainline), to provide developers additional use case for the counter
> framework with chardev support.
>
> Oleksij Rempel (2):
> dt-bindings: counter: add interrupt-counter binding
> counter: add IRQ or GPIO based counter
Series applied to the togreg branch of iio.git and pushed out as testing.
thanks,
Jonathan
>
> .../bindings/counter/interrupt-counter.yaml | 62 +++++
> MAINTAINERS | 7 +
> drivers/counter/Kconfig | 10 +
> drivers/counter/Makefile | 1 +
> drivers/counter/interrupt-cnt.c | 244 ++++++++++++++++++
> 5 files changed, 324 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/counter/interrupt-counter.yaml
> create mode 100644 drivers/counter/interrupt-cnt.c
>
prev parent reply other threads:[~2021-03-14 16:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 8:03 [PATCH v8 0/2] add support for GPIO or IRQ based event counter Oleksij Rempel
2021-03-01 8:04 ` [PATCH v8 1/2] dt-bindings: counter: add interrupt-counter binding Oleksij Rempel
2021-03-02 1:16 ` William Breathitt Gray
2021-03-08 17:30 ` Rob Herring
2021-03-01 8:04 ` [PATCH v8 2/2] counter: add IRQ or GPIO based counter Oleksij Rempel
2021-03-02 1:18 ` William Breathitt Gray
2021-03-14 16:55 ` Jonathan Cameron [this message]
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=20210314165504.536d9ba6@archlinux \
--to=jic23@kernel.org \
--cc=david@protonic.nl \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=robin@protonic.nl \
--cc=vilhelm.gray@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).