From: William Breathitt Gray <william.gray@linaro.org>
To: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
Cc: syednwaris@gmail.com, vigneshr@ti.com, jpanis@baylibre.com,
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 v5] counter: Introduce the COUNTER_COMP_FREQUENCY() macro
Date: Fri, 1 Mar 2024 10:55:39 -0500 [thread overview]
Message-ID: <ZeH6e02zzfAjw-sd@ishi> (raw)
In-Reply-To: <20240301102505.591918-1-fabrice.gasnier@foss.st.com>
[-- Attachment #1: Type: text/plain, Size: 1569 bytes --]
On Fri, Mar 01, 2024 at 11:25:05AM +0100, Fabrice Gasnier wrote:
> Now that there are two users for the "frequency" extension, introduce a
> new COUNTER_COMP_FREQUENCY() macro.
> This extension is intended to be a read-only signal attribute.
>
> Suggested-by: William Breathitt Gray <william.gray@linaro.org>
> Signed-off-by: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
> ---
> Changes in v5
> - "frequency" extension is read-only, so there's no need to provide
> a write parameter.
> - patch sent separately from "counter: Add stm32 timer events support" [1]
> [1] https://lore.kernel.org/lkml/20240227173803.53906-2-fabrice.gasnier@foss.st.com/
> ---
> include/linux/counter.h | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/include/linux/counter.h b/include/linux/counter.h
> index 702e9108bbb4..0ac36f815b7d 100644
> --- a/include/linux/counter.h
> +++ b/include/linux/counter.h
> @@ -602,6 +602,13 @@ struct counter_array {
> #define COUNTER_COMP_FLOOR(_read, _write) \
> COUNTER_COMP_COUNT_U64("floor", _read, _write)
>
> +#define COUNTER_COMP_FREQUENCY(_read) \
> +{ \
> + .type = COUNTER_COMP_U64, \
> + .name = "frequency", \
> + .signal_u64_read = (_read), \
> +}
> +
> #define COUNTER_COMP_POLARITY(_read, _write, _available) \
> { \
> .type = COUNTER_COMP_SIGNAL_POLARITY, \
> --
> 2.25.1
Hi Fabrice,
Setting the structure members directly works, but why not use
COUNTER_COMP_SIGNAL_U64("frequency", _read, NULL) instead to keep the
code more succinct?
William Breathitt Gray
[-- 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: syednwaris@gmail.com, vigneshr@ti.com, jpanis@baylibre.com,
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 v5] counter: Introduce the COUNTER_COMP_FREQUENCY() macro
Date: Fri, 1 Mar 2024 10:55:39 -0500 [thread overview]
Message-ID: <ZeH6e02zzfAjw-sd@ishi> (raw)
In-Reply-To: <20240301102505.591918-1-fabrice.gasnier@foss.st.com>
[-- Attachment #1.1: Type: text/plain, Size: 1569 bytes --]
On Fri, Mar 01, 2024 at 11:25:05AM +0100, Fabrice Gasnier wrote:
> Now that there are two users for the "frequency" extension, introduce a
> new COUNTER_COMP_FREQUENCY() macro.
> This extension is intended to be a read-only signal attribute.
>
> Suggested-by: William Breathitt Gray <william.gray@linaro.org>
> Signed-off-by: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
> ---
> Changes in v5
> - "frequency" extension is read-only, so there's no need to provide
> a write parameter.
> - patch sent separately from "counter: Add stm32 timer events support" [1]
> [1] https://lore.kernel.org/lkml/20240227173803.53906-2-fabrice.gasnier@foss.st.com/
> ---
> include/linux/counter.h | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/include/linux/counter.h b/include/linux/counter.h
> index 702e9108bbb4..0ac36f815b7d 100644
> --- a/include/linux/counter.h
> +++ b/include/linux/counter.h
> @@ -602,6 +602,13 @@ struct counter_array {
> #define COUNTER_COMP_FLOOR(_read, _write) \
> COUNTER_COMP_COUNT_U64("floor", _read, _write)
>
> +#define COUNTER_COMP_FREQUENCY(_read) \
> +{ \
> + .type = COUNTER_COMP_U64, \
> + .name = "frequency", \
> + .signal_u64_read = (_read), \
> +}
> +
> #define COUNTER_COMP_POLARITY(_read, _write, _available) \
> { \
> .type = COUNTER_COMP_SIGNAL_POLARITY, \
> --
> 2.25.1
Hi Fabrice,
Setting the structure members directly works, but why not use
COUNTER_COMP_SIGNAL_U64("frequency", _read, NULL) instead to keep the
code more succinct?
William Breathitt Gray
[-- 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:[~2024-03-01 15:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 10:25 [PATCH v5] counter: Introduce the COUNTER_COMP_FREQUENCY() macro Fabrice Gasnier
2024-03-01 10:25 ` Fabrice Gasnier
2024-03-01 15:55 ` William Breathitt Gray [this message]
2024-03-01 15:55 ` William Breathitt Gray
2024-03-04 8:41 ` Fabrice Gasnier
2024-03-04 8:41 ` Fabrice Gasnier
2024-03-04 13:28 ` William Breathitt Gray
2024-03-04 13:28 ` 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=ZeH6e02zzfAjw-sd@ishi \
--to=william.gray@linaro.org \
--cc=alexandre.torgue@foss.st.com \
--cc=fabrice.gasnier@foss.st.com \
--cc=jpanis@baylibre.com \
--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=syednwaris@gmail.com \
--cc=vigneshr@ti.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.