From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <pbhagavatula@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw99501 [PATCH v3 2/2] event/cnxk: add external clock support for timer
Date: Thu, 23 Sep 2021 23:32:19 +0200 (CEST) [thread overview]
Message-ID: <20210923213219.2368112075A@dpdk.org> (raw)
In-Reply-To: <20210923213046.3157-2-pbhagavatula@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/99501
_coding style issues_
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#87:
RTE_EVENT_TIMER_ADAPTER_EXT_CLK0 = TIM_CLK_SRC_10NS,
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#88:
RTE_EVENT_TIMER_ADAPTER_EXT_CLK1 = TIM_CLK_SRC_GPIO,
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#89:
RTE_EVENT_TIMER_ADAPTER_EXT_CLK2 = TIM_CLK_SRC_PTP,
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#90:
RTE_EVENT_TIMER_ADAPTER_EXT_CLK3 = TIM_CLK_SRC_SYNCE,
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#92:
TIM supports clock input from external GPIO, PTP, SYNCE clocks.
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#96:
Since TIM is unaware of input clock frequency, application is
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#99:
-a 0002:0e:00.0,tim_eclk_freq=122880000-0-0
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#121: FILE: doc/guides/eventdevs/cnxk.rst:167:
+- ``TIM external clock frequency``
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#123: FILE: doc/guides/eventdevs/cnxk.rst:169:
+ The ``tim_eclk_freq`` devagrs can be used to pass external clock frequencies
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#128: FILE: doc/guides/eventdevs/cnxk.rst:174:
+ RTE_EVENT_TIMER_ADAPTER_EXT_CLK0 = TIM_CLK_SRC_10NS,
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#129: FILE: doc/guides/eventdevs/cnxk.rst:175:
+ RTE_EVENT_TIMER_ADAPTER_EXT_CLK1 = TIM_CLK_SRC_GPIO,
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#130: FILE: doc/guides/eventdevs/cnxk.rst:176:
+ RTE_EVENT_TIMER_ADAPTER_EXT_CLK2 = TIM_CLK_SRC_PTP,
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#131: FILE: doc/guides/eventdevs/cnxk.rst:177:
+ RTE_EVENT_TIMER_ADAPTER_EXT_CLK3 = TIM_CLK_SRC_SYNCE
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#137: FILE: doc/guides/eventdevs/cnxk.rst:183:
+ -a 0002:0e:00.0,tim_eclk_freq=122880000-1000000000-0
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#163: FILE: drivers/event/cnxk/cn10k_eventdev.c:979:
+ CNXK_TIM_STATS_ENA "=1"
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#164: FILE: drivers/event/cnxk/cn10k_eventdev.c:980:
+ CNXK_TIM_EXT_CLK "=<string>");
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#205: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:152:
+ } while (ns[i] % (uint64_t)cnxk_tim_ns_per_tck(clk_freq));
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#213: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:160:
+tim_adjust_resolution(uint64_t *req_ns, uint64_t *req_tck, double tck_ns,
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#234: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:181:
+ (TIM_MAX_BUCKET_SIZE - TIM_MIN_BUCKET_SIZE)) {
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#234: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:181:
+ (TIM_MAX_BUCKET_SIZE - TIM_MIN_BUCKET_SIZE)) {
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#239: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:186:
+ (TIM_MAX_BUCKET_SIZE - TIM_MIN_BUCKET_SIZE)) {
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#239: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:186:
+ (TIM_MAX_BUCKET_SIZE - TIM_MIN_BUCKET_SIZE)) {
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#262: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:262:
+ req_ns = tim_ring->tck_nsec;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#265: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:265:
+ tim_adjust_resolution(&req_ns, &req_tck, tck_ns, clk_freq,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#267: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:267:
+ if ((tim_ring->tck_nsec != req_ns) &&
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#270: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:270:
+ goto tim_hw_free;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#272: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:272:
+ tim_ring->tck_nsec = ceil(req_tck * tck_ns);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#282: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:582:
+cnxk_tim_parse_clk_list(const char *value, void *opaque)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#284: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:584:
+ enum roc_tim_clk_src src[] = {ROC_TIM_CLK_SRC_GPIO, ROC_TIM_CLK_SRC_PTP,
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#284: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:584:
+ enum roc_tim_clk_src src[] = {ROC_TIM_CLK_SRC_GPIO, ROC_TIM_CLK_SRC_PTP,
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#284: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:584:
+ enum roc_tim_clk_src src[] = {ROC_TIM_CLK_SRC_GPIO, ROC_TIM_CLK_SRC_PTP,
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#285: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:585:
+ ROC_TIM_CLK_SRC_SYNCE,
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#286: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:586:
+ ROC_TIM_CLK_SRC_INVALID};
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#287: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:587:
+ struct cnxk_tim_evdev *dev = opaque;
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#296: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:596:
+ while (tok != NULL && src[i] != ROC_TIM_CLK_SRC_INVALID) {
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#306: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:606:
+cnxk_tim_parse_kvargs_dsv(const char *key, const char *value, void *opaque)
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#313: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:613:
+ cnxk_tim_parse_clk_list(value, opaque);
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#325: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:640:
+ rte_kvargs_process(kvlist, CNXK_TIM_EXT_CLK, &cnxk_tim_parse_kvargs_dsv,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#325: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:640:
+ rte_kvargs_process(kvlist, CNXK_TIM_EXT_CLK, &cnxk_tim_parse_kvargs_dsv,
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#338: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:42:
+#define CNXK_TIM_EXT_CLK "tim_eclk_freq"
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#338: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:42:
+#define CNXK_TIM_EXT_CLK "tim_eclk_freq"
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#346: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:98:
+ uint64_t ext_clk_freq[ROC_TIM_CLK_SRC_INVALID];
total: 0 errors, 42 warnings, 216 lines checked
next parent reply other threads:[~2021-09-23 21:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210923213046.3157-2-pbhagavatula@marvell.com>
2021-09-23 21:32 ` checkpatch [this message]
2021-09-28 0:58 ` [dpdk-test-report] |FAILURE| pw99501 [dpdk-dev] " 0-day Robot
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=20210923213219.2368112075A@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=pbhagavatula@marvell.com \
--cc=test-report@dpdk.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;
as well as URLs for NNTP newsgroup(s).