public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
	William Breathitt Gray <vilhelm.gray@gmail.com>
Subject: [RESEND PATCH 0/6] Counter updates, cleanups, and features for 5.18
Date: Tue, 15 Mar 2022 15:38:51 -0400	[thread overview]
Message-ID: <cover.1647373009.git.vilhelm.gray@gmail.com> (raw)

First set of new Counter updates, cleanups, and features for 5.18

Only a few changes this cycle, but we do see the addition of a new
COUNTER_EVENT_CHANGE_OF_STATE event type that allows userspace to watch
counter pulses.

Features
* Add new COUNTER_EVENT_CHANGE_OF_STATE. This adds new counter event to
  notify user space about every new counter pulse. The interrupt-cnt
  driver is the first to use this new feature.

Cleanups
- Add Counter subsystem git tree to MAINTAINERS file.
- Set counter device name. This provides a convenient way to identify
  the counter device in devres_log events and similar situations.
- Add defaults to switch-statements. This pacifies warning messages from
  Clang static analysis reports.

Driver Updates
* 104-quad-8
  - Add COMPILE_TEST depends
* interrupt-cnt
  - Add counter_push_event()

Oleksij Rempel (2):
  counter: add new COUNTER_EVENT_CHANGE_OF_STATE
  counter: interrupt-cnt: add counter_push_event()

Tom Rix (1):
  counter: add defaults to switch-statements

William Breathitt Gray (3):
  counter: 104-quad-8: Add COMPILE_TEST depends
  counter: Set counter device name
  MAINTAINERS: Add Counter subsystem git tree

 MAINTAINERS                      |  1 +
 drivers/counter/Kconfig          |  2 +-
 drivers/counter/counter-chrdev.c |  4 ++++
 drivers/counter/counter-core.c   | 12 +++++++++++-
 drivers/counter/interrupt-cnt.c  |  7 +++++--
 include/uapi/linux/counter.h     |  2 ++
 6 files changed, 24 insertions(+), 4 deletions(-)


base-commit: 7e57714cd0ad2d5bb90e50b5096a0e671dec1ef3
-- 
2.35.1


             reply	other threads:[~2022-03-15 19:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-15 19:38 William Breathitt Gray [this message]
2022-03-15 19:38 ` [RESEND PATCH 1/6] counter: 104-quad-8: Add COMPILE_TEST depends William Breathitt Gray
2022-03-16  7:39   ` Syed Nayyar Waris
2022-03-15 19:38 ` [RESEND PATCH 2/6] counter: Set counter device name William Breathitt Gray
2022-03-15 19:38 ` [RESEND PATCH 3/6] counter: add new COUNTER_EVENT_CHANGE_OF_STATE William Breathitt Gray
2022-03-15 19:38 ` [RESEND PATCH 4/6] counter: interrupt-cnt: add counter_push_event() William Breathitt Gray
2022-03-15 19:38 ` [RESEND PATCH 5/6] MAINTAINERS: Add Counter subsystem git tree William Breathitt Gray
2022-03-15 19:38 ` [RESEND PATCH 6/6] counter: add defaults to switch-statements William Breathitt Gray
2022-03-16  7:37   ` Syed Nayyar Waris

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=cover.1647373009.git.vilhelm.gray@gmail.com \
    --to=vilhelm.gray@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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