From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Shijith Thotton <sthotton@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw96356 [PATCH] drivers: add external clock support for cnxk timer
Date: Wed, 28 Jul 2021 17:26:02 +0200 (CEST) [thread overview]
Message-ID: <20210728152602.9E6BE122E58@dpdk.org> (raw)
In-Reply-To: <ee6a527b0e824a34cbebbf0865a5bdc172d5207e.1627483481.git.sthotton@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/96356
_coding style issues_
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#77:
To configure tim with external clock, requested resolution should be
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#80:
tim_ext_clk is the devarg used to pass external clock frequency.
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#82:
E.g. -a 0002:0e:00.0,tim_ext_clk=122880000
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#103: FILE: doc/guides/eventdevs/cnxk.rst:167:
+- ``TIM external clock frequency``
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#105: FILE: doc/guides/eventdevs/cnxk.rst:169:
+ The ``tim_ext_clk`` devagrs can be used to pass external clock frequency when
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#110: FILE: doc/guides/eventdevs/cnxk.rst:174:
+ -a 0002:0e:00.0,tim_ext_clk=122880000
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#176: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:152:
+ } while (ns[i] % cnxk_tim_min_resolution_ns(clk_freq));
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#184: 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'?
#192: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:168:
+ uint64_t m_tck = cnxk_tim_min_tmo_ticks(cnxk_tim_cntfrq());
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#192: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:168:
+ uint64_t m_tck = cnxk_tim_min_tmo_ticks(cnxk_tim_cntfrq());
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#206: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:182:
+ (TIM_MAX_BUCKET_SIZE - TIM_MIN_BUCKET_SIZE)) {
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#206: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:182:
+ (TIM_MAX_BUCKET_SIZE - TIM_MIN_BUCKET_SIZE)) {
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#211: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:187:
+ (TIM_MAX_BUCKET_SIZE - TIM_MIN_BUCKET_SIZE)) {
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#211: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:187:
+ (TIM_MAX_BUCKET_SIZE - TIM_MIN_BUCKET_SIZE)) {
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#242: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:240:
+ cnxk_tim_min_resolution_ns(cnxk_tim_cntfrq()));
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#242: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:240:
+ cnxk_tim_min_resolution_ns(cnxk_tim_cntfrq()));
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#249: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:247:
+ goto tim_hw_free;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#255: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:253:
+ tim_adjust_resolution(&req_ns, &req_tck, tck_ns,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#256: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:254:
+ cnxk_tim_cntfrq(), rcfg->max_tmo_ns);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#260: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:258:
+ goto tim_hw_free;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#264: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:262:
+ tim_ring->tck_nsec = rcfg->timer_tick_ns;
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#278: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:307:
+ interval = NSEC2TICK(tim_ring->tck_nsec, cnxk_tim_cntfrq());
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#278: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:307:
+ interval = NSEC2TICK(tim_ring->tck_nsec, cnxk_tim_cntfrq());
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#280: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:309:
+ interval = NSEC2TICK(tim_ring->tck_nsec, dev->ext_clk_frq);
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#282: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:311:
+ rc = roc_tim_lf_config(&dev->tim, tim_ring->ring_id,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#282: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:311:
+ rc = roc_tim_lf_config(&dev->tim, tim_ring->ring_id,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#282: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:311:
+ rc = roc_tim_lf_config(&dev->tim, tim_ring->ring_id,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#283: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:312:
+ cnxk_tim_convert_clk_src(tim_ring->clk_src), 0,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#283: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:312:
+ cnxk_tim_convert_clk_src(tim_ring->clk_src), 0,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#284: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:313:
+ 0, tim_ring->nb_bkts, tim_ring->chunk_sz,
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#284: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:313:
+ 0, tim_ring->nb_bkts, tim_ring->chunk_sz,
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#293: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:589:
+ rte_kvargs_process(kvlist, CNXK_TIM_EXT_CLK, &parse_kvargs_value,
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#306: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:42:
+#define CNXK_TIM_EXT_CLK "tim_ext_clk"
WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#306: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:42:
+#define CNXK_TIM_EXT_CLK "tim_ext_clk"
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#323: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:192:
+ ROC_TIM_CLK_SRC_GTI;
WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#325: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:194:
+ return ROC_TIM_CLK_SRC_GPIO;
total: 0 errors, 36 warnings, 208 lines checked
next parent reply other threads:[~2021-07-28 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ee6a527b0e824a34cbebbf0865a5bdc172d5207e.1627483481.git.sthotton@marvell.com>
2021-07-28 15:26 ` checkpatch [this message]
2021-07-28 16:05 ` [dpdk-test-report] |FAILURE| pw96356 [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=20210728152602.9E6BE122E58@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=sthotton@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).