[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240301102505.591918-1-fabrice.gasnier@foss.st.com>
Date: Fri, 1 Mar 2024 11:25:05 +0100
From: Fabrice Gasnier <fabrice.gasnier@...s.st.com>
To: <william.gray@...aro.org>
CC: <syednwaris@...il.com>, <vigneshr@...com>, <jpanis@...libre.com>,
<alexandre.torgue@...s.st.com>, <fabrice.gasnier@...s.st.com>,
<linux-iio@...r.kernel.org>,
<linux-stm32@...md-mailman.stormreply.com>,
<linux-arm-kernel@...ts.infradead.org>, <linux-kernel@...r.kernel.org>
Subject: [PATCH v5] counter: Introduce the COUNTER_COMP_FREQUENCY() macro
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@...aro.org>
Signed-off-by: Fabrice Gasnier <fabrice.gasnier@...s.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
Powered by blists - more mailing lists