From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: 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, Jonathan Cameron <jic23@kernel.org>
Subject: Re: [PATCH v2 2/2] counter: interrupt-cnt: add counter_push_event()
Date: Fri, 4 Feb 2022 16:35:12 +0900 [thread overview]
Message-ID: <YfzXMKusj22MEisY@shinobu> (raw)
In-Reply-To: <20220203135727.2374052-3-o.rempel@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1699 bytes --]
On Thu, Feb 03, 2022 at 02:57:27PM +0100, Oleksij Rempel wrote:
> Add counter_push_event() to notify user space about new pulses
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
This is a simple solution so if it works for your use-case I'm okay with
it; I think future counter devices could make use of this new
COUNTER_EVENT_CHANGE_OF_STATE event type too, so that's a plus.
I'm going to wait a week to give others time to chime in if they want.
Otherwise I'll give a proper approval for this series next week.
William Breathitt Gray
> ---
> drivers/counter/interrupt-cnt.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/counter/interrupt-cnt.c b/drivers/counter/interrupt-cnt.c
> index 9e99702470c2..3b13f56bbb11 100644
> --- a/drivers/counter/interrupt-cnt.c
> +++ b/drivers/counter/interrupt-cnt.c
> @@ -26,10 +26,13 @@ struct interrupt_cnt_priv {
>
> static irqreturn_t interrupt_cnt_isr(int irq, void *dev_id)
> {
> - struct interrupt_cnt_priv *priv = dev_id;
> + struct counter_device *counter = dev_id;
> + struct interrupt_cnt_priv *priv = counter_priv(counter);
>
> atomic_inc(&priv->count);
>
> + counter_push_event(counter, COUNTER_EVENT_CHANGE_OF_STATE, 0);
> +
> return IRQ_HANDLED;
> }
>
> @@ -209,7 +212,7 @@ static int interrupt_cnt_probe(struct platform_device *pdev)
> irq_set_status_flags(priv->irq, IRQ_NOAUTOEN);
> ret = devm_request_irq(dev, priv->irq, interrupt_cnt_isr,
> IRQF_TRIGGER_RISING | IRQF_NO_THREAD,
> - dev_name(dev), priv);
> + dev_name(dev), counter);
> if (ret)
> return ret;
>
> --
> 2.30.2
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-02-04 7:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 13:57 [PATCH v2 0/2] counter: push event on every pulse Oleksij Rempel
2022-02-03 13:57 ` [PATCH v2 1/2] counter: add new COUNTER_EVENT_CHANGE_OF_STATE Oleksij Rempel
2022-02-03 13:57 ` [PATCH v2 2/2] counter: interrupt-cnt: add counter_push_event() Oleksij Rempel
2022-02-04 7:35 ` William Breathitt Gray [this message]
2022-02-11 9:41 ` [PATCH v2 0/2] counter: push event on every pulse William Breathitt Gray
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=YfzXMKusj22MEisY@shinobu \
--to=vilhelm.gray@gmail.com \
--cc=david@protonic.nl \
--cc=jic23@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=robin@protonic.nl \
/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