From: William Breathitt Gray <william.gray@linaro.org>
To: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
Cc: lee@kernel.org, alexandre.torgue@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: Re: [PATCH v2 0/6] counter: fix, improvements and stm32 timer events support
Date: Fri, 13 Oct 2023 18:57:15 -0400 [thread overview]
Message-ID: <ZSnLSwsr7RxLdPie@fedora> (raw)
In-Reply-To: <20230922143920.3144249-1-fabrice.gasnier@foss.st.com>
[-- Attachment #1: Type: text/plain, Size: 2406 bytes --]
On Fri, Sep 22, 2023 at 04:39:14PM +0200, Fabrice Gasnier wrote:
> This series combines some fix and improvements to the counter interface,
> found while stm32 timer counter driver developements.
> It also introduces a new tool that can be used for testing.
>
> Then, it improves the stm32 timer counter driver by introducing new signals,
> e.g. counting frequency, and missing channels.
> It also adds support for interrupt based events using the chrdev interface.
> Two event types are added in this series: overflows and capture.
>
> Up to now, stm32 timer counter driver focused mainly on quadrature
> encoder feature. With this series, all timer instances can be enabled
> for simple counting (with overflow and capture events).
Hi Fabrice,
Would you give a brief summary of the possible configurations we can
have for these devices. For example, the existing driver supports a
quadrature counting mode where Channel 1 and Channel 2 serve as A and B
inputs; I also see that another mode is a simple tally counter with the
internal clock serving as the input. How do Channel 3 and Channel 4 fit
in here?
If you list out all the possible arrangements, I think it'll help me
understand how the signals match up with each particular mode.
Thanks,
William Breathitt Gray
>
> Changes in v2:
> - counter fix and improvement patch applied, hence dropped in v2 series
> - mfd patch applied, hence dropped in v2 series
> - revisit watch events tool (mainly command line interface)
> - add one patch to rename STM32 Timer counter
> - various review comments from v1
>
> Fabrice Gasnier (6):
> tools/counter: add a flexible watch events tool
> counter: stm32-timer-cnt: rename quadrature signal
> counter: stm32-timer-cnt: rename counter
> counter: stm32-timer-cnt: introduce clock signal
> counter: stm32-timer-cnt: populate capture channels and check encoder
> counter: stm32-timer-cnt: add support for events
>
> drivers/counter/stm32-timer-cnt.c | 558 ++++++++++++++++++++++++++-
> include/linux/mfd/stm32-timers.h | 15 +
> tools/counter/Build | 1 +
> tools/counter/Makefile | 12 +-
> tools/counter/counter_watch_events.c | 368 ++++++++++++++++++
> 5 files changed, 934 insertions(+), 20 deletions(-)
> create mode 100644 tools/counter/counter_watch_events.c
>
> --
> 2.25.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: William Breathitt Gray <william.gray@linaro.org>
To: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
Cc: lee@kernel.org, alexandre.torgue@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: Re: [PATCH v2 0/6] counter: fix, improvements and stm32 timer events support
Date: Fri, 13 Oct 2023 18:57:15 -0400 [thread overview]
Message-ID: <ZSnLSwsr7RxLdPie@fedora> (raw)
In-Reply-To: <20230922143920.3144249-1-fabrice.gasnier@foss.st.com>
[-- Attachment #1.1: Type: text/plain, Size: 2406 bytes --]
On Fri, Sep 22, 2023 at 04:39:14PM +0200, Fabrice Gasnier wrote:
> This series combines some fix and improvements to the counter interface,
> found while stm32 timer counter driver developements.
> It also introduces a new tool that can be used for testing.
>
> Then, it improves the stm32 timer counter driver by introducing new signals,
> e.g. counting frequency, and missing channels.
> It also adds support for interrupt based events using the chrdev interface.
> Two event types are added in this series: overflows and capture.
>
> Up to now, stm32 timer counter driver focused mainly on quadrature
> encoder feature. With this series, all timer instances can be enabled
> for simple counting (with overflow and capture events).
Hi Fabrice,
Would you give a brief summary of the possible configurations we can
have for these devices. For example, the existing driver supports a
quadrature counting mode where Channel 1 and Channel 2 serve as A and B
inputs; I also see that another mode is a simple tally counter with the
internal clock serving as the input. How do Channel 3 and Channel 4 fit
in here?
If you list out all the possible arrangements, I think it'll help me
understand how the signals match up with each particular mode.
Thanks,
William Breathitt Gray
>
> Changes in v2:
> - counter fix and improvement patch applied, hence dropped in v2 series
> - mfd patch applied, hence dropped in v2 series
> - revisit watch events tool (mainly command line interface)
> - add one patch to rename STM32 Timer counter
> - various review comments from v1
>
> Fabrice Gasnier (6):
> tools/counter: add a flexible watch events tool
> counter: stm32-timer-cnt: rename quadrature signal
> counter: stm32-timer-cnt: rename counter
> counter: stm32-timer-cnt: introduce clock signal
> counter: stm32-timer-cnt: populate capture channels and check encoder
> counter: stm32-timer-cnt: add support for events
>
> drivers/counter/stm32-timer-cnt.c | 558 ++++++++++++++++++++++++++-
> include/linux/mfd/stm32-timers.h | 15 +
> tools/counter/Build | 1 +
> tools/counter/Makefile | 12 +-
> tools/counter/counter_watch_events.c | 368 ++++++++++++++++++
> 5 files changed, 934 insertions(+), 20 deletions(-)
> create mode 100644 tools/counter/counter_watch_events.c
>
> --
> 2.25.1
>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-10-13 22:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 14:39 [PATCH v2 0/6] counter: fix, improvements and stm32 timer events support Fabrice Gasnier
2023-09-22 14:39 ` Fabrice Gasnier
2023-09-22 14:39 ` [PATCH v2 1/6] tools/counter: add a flexible watch events tool Fabrice Gasnier
2023-09-22 14:39 ` Fabrice Gasnier
2023-10-04 1:37 ` William Breathitt Gray
2023-10-04 1:37 ` William Breathitt Gray
2023-09-22 14:39 ` [PATCH v2 2/6] counter: stm32-timer-cnt: rename quadrature signal Fabrice Gasnier
2023-09-22 14:39 ` Fabrice Gasnier
2023-09-22 14:39 ` [PATCH v2 3/6] counter: stm32-timer-cnt: rename counter Fabrice Gasnier
2023-09-22 14:39 ` Fabrice Gasnier
2023-09-22 14:39 ` [PATCH v2 4/6] counter: stm32-timer-cnt: introduce clock signal Fabrice Gasnier
2023-09-22 14:39 ` Fabrice Gasnier
2023-10-13 21:22 ` William Breathitt Gray
2023-10-13 21:22 ` William Breathitt Gray
2023-09-22 14:39 ` [PATCH v2 5/6] counter: stm32-timer-cnt: populate capture channels and check encoder Fabrice Gasnier
2023-09-22 14:39 ` Fabrice Gasnier
2023-10-13 22:48 ` William Breathitt Gray
2023-10-13 22:48 ` William Breathitt Gray
2023-12-15 17:13 ` Fabrice Gasnier
2023-12-15 17:13 ` Fabrice Gasnier
2023-12-18 17:58 ` William Breathitt Gray
2023-12-18 17:58 ` William Breathitt Gray
2023-09-22 14:39 ` [PATCH v2 6/6] counter: stm32-timer-cnt: add support for events Fabrice Gasnier
2023-09-22 14:39 ` Fabrice Gasnier
2023-10-13 23:03 ` William Breathitt Gray
2023-10-13 23:03 ` William Breathitt Gray
2023-10-13 22:57 ` William Breathitt Gray [this message]
2023-10-13 22:57 ` [PATCH v2 0/6] counter: fix, improvements and stm32 timer events support 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=ZSnLSwsr7RxLdPie@fedora \
--to=william.gray@linaro.org \
--cc=alexandre.torgue@foss.st.com \
--cc=fabrice.gasnier@foss.st.com \
--cc=lee@kernel.org \
--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 \
/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.