public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Breathitt Gray <william.gray@linaro.org>
To: jic23@kernel.org, lars@metafoo.de, benjamin.gaignard@st.com,
	mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com
Cc: fabrice.gasnier@foss.st.com, linux-iio@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Removing the last of IIO_COUNT (stm32-timer-trigger)
Date: Sun, 16 Oct 2022 08:05:40 -0400	[thread overview]
Message-ID: <Y0vzlOmFrVCQVXMq@fedora> (raw)

[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]

Hi all,

The drivers/iio/trigger/stm32-timer-trigger.c file remains the last
consumer if the IIO_COUNT type. The IIO_COUNT type was deprecated some
time ago with the introduction of the Counter subsystem. Most of the
previous IIO_COUNT consumers were migrated successfully to the Counter
subsystem, but the stm32-timer-trigger driver remains as the sole module
preventing the final removal of IIO_COUNT.

At the time we deprecated IIO_COUNT, the Counter subsystem was nascent
and lacked some of the functionality we have nowadays such as a
character device interface, timestamping, hardware buffer support, etc.
If I recall correctly, the decision to delay the migration of
stm32-timer-trigger to the Counter subsystem was a lack of some
functionality the Counter subsystem could not provide at the time.

I hoping someone can evaluate stm32-timer-trigger to see if we are able
transition now to the Counter subsystem, or if that necessary
functionality is still missing today. Even if it turns out that we are
unable to migrate, it'll be useful to know what's left to implement in
the Counter subsystem to support stm32-timer-trigger or similar devices
in the future.

Thanks,

William Breathitt Gray

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

             reply	other threads:[~2022-10-16 12:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-16 12:05 William Breathitt Gray [this message]
2022-10-27  9:41 ` Removing the last of IIO_COUNT (stm32-timer-trigger) Fabrice Gasnier
2022-11-27  0:23   ` William Breathitt Gray
2022-12-03 16:20     ` 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=Y0vzlOmFrVCQVXMq@fedora \
    --to=william.gray@linaro.org \
    --cc=alexandre.torgue@foss.st.com \
    --cc=benjamin.gaignard@st.com \
    --cc=fabrice.gasnier@foss.st.com \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mcoquelin.stm32@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