automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <pbhagavatula@marvell.com>
Subject: |WARNING| pw114055 [PATCH 4/4] event/cnxk: disable timer resolution estimation
Date: Tue, 19 Jul 2022 13:12:53 +0200 (CEST)	[thread overview]
Message-ID: <20220719111253.C54C01231C5@dpdk.org> (raw)
In-Reply-To: <20220719111125.8276-4-pbhagavatula@marvell.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/114055

_coding style issues_


WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#80: 
Disable timer resolution estimation, read TIM LF clock registers

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#101: FILE: drivers/common/cnxk/hw/tim.h:34:
+#define TIM_LF_FR_RN_GPIOS	   (0x020)

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#102: FILE: drivers/common/cnxk/hw/tim.h:35:
+#define TIM_LF_FR_RN_GTI	   (0x030)

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#103: FILE: drivers/common/cnxk/hw/tim.h:36:
+#define TIM_LF_FR_RN_PTP	   (0x040)

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#104: FILE: drivers/common/cnxk/hw/tim.h:37:
+#define TIM_LF_FR_RN_TENNS	   (0x050)

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#105: FILE: drivers/common/cnxk/hw/tim.h:38:
+#define TIM_LF_FR_RN_SYNCE	   (0x060)

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#106: FILE: drivers/common/cnxk/hw/tim.h:39:
+#define TIM_LF_FR_RN_BTS	   (0x070)

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#220: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:192:
+	tim_ring->tck_int = round((double)rcfg->timer_tick_ns /

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#228: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:205:
+	tim_ring->base = roc_tim_lf_base_get(&dev->tim, tim_ring->ring_id);

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#228: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:205:
+	tim_ring->base = roc_tim_lf_base_get(&dev->tim, tim_ring->ring_id);

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#228: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:205:
+	tim_ring->base = roc_tim_lf_base_get(&dev->tim, tim_ring->ring_id);

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#228: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:205:
+	tim_ring->base = roc_tim_lf_base_get(&dev->tim, tim_ring->ring_id);

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#229: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:206:
+	tim_ring->tbase = cnxk_tim_get_tick_base(clk_src, tim_ring->base);

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#229: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:206:
+	tim_ring->tbase = cnxk_tim_get_tick_base(clk_src, tim_ring->base);

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#229: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:206:
+	tim_ring->tbase = cnxk_tim_get_tick_base(clk_src, tim_ring->base);

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#231: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:208:
+	if (roc_model_is_cn9k() && (tim_ring->clk_src == ROC_TIM_CLK_SRC_GTI))

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#231: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:208:
+	if (roc_model_is_cn9k() && (tim_ring->clk_src == ROC_TIM_CLK_SRC_GTI))

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#232: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:209:
+		tim_ring->tick_fn = cnxk_tim_cntvct;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#232: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:209:
+		tim_ring->tick_fn = cnxk_tim_cntvct;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#234: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:211:
+		tim_ring->tick_fn = cnxk_tim_tick_read;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#234: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:211:
+		tim_ring->tick_fn = cnxk_tim_tick_read;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#287: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:324:
+	if (roc_model_is_cn9k() && (tim_ring->clk_src == ROC_TIM_CLK_SRC_GTI)) {

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#287: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:324:
+	if (roc_model_is_cn9k() && (tim_ring->clk_src == ROC_TIM_CLK_SRC_GTI)) {

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#290: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:327:
+		start_diff = cnxk_tim_cntvct(tim_ring->tbase) -

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#290: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:327:
+		start_diff = cnxk_tim_cntvct(tim_ring->tbase) -

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#291: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:328:
+			     cnxk_tim_tick_read(tim_ring->tbase);

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#291: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:328:
+			     cnxk_tim_tick_read(tim_ring->tbase);

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#292: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:329:
+		tim_ring->ring_start_cyc += start_diff;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#303: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:357:
+		tim_ring->tick_fn(tim_ring->tbase) - tim_ring->ring_start_cyc;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#303: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:357:
+		tim_ring->tick_fn(tim_ring->tbase) - tim_ring->ring_start_cyc;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#303: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:357:
+		tim_ring->tick_fn(tim_ring->tbase) - tim_ring->ring_start_cyc;

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#316: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:27:
+#define CNXK_TIM_RING_DEF_CHUNK_SZ  (256)

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#324: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:34:
+#define CNXK_TIM_MAX_POOL_CACHE_SZ  (16)

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#366: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:174:
+cnxk_tim_cntvct(uint64_t base __rte_unused)

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#380: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:192:
+cnxk_tim_cntvct(uint64_t base __rte_unused)

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#389: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:205:
+cnxk_tim_tick_read(uint64_t tick_base)

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#402: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:231:
+cnxk_tim_get_tick_base(enum roc_tim_clk_src clk_src, uintptr_t base)

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#402: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:231:
+cnxk_tim_get_tick_base(enum roc_tim_clk_src clk_src, uintptr_t base)

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#405: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:234:
+	case ROC_TIM_CLK_SRC_GTI:

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#406: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:235:
+		return base + TIM_LF_FR_RN_GTI;

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#407: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:236:
+	case ROC_TIM_CLK_SRC_GPIO:

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#408: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:237:
+		return base + TIM_LF_FR_RN_GPIOS;

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#409: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:238:
+	case ROC_TIM_CLK_SRC_10NS:

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#410: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:239:
+		return base + TIM_LF_FR_RN_TENNS;

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#411: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:240:
+	case ROC_TIM_CLK_SRC_PTP:

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#412: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:241:
+		return base + TIM_LF_FR_RN_PTP;

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#413: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:242:
+	case ROC_TIM_CLK_SRC_SYNCE:

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#414: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:243:
+		return base + TIM_LF_FR_RN_SYNCE;

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#415: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:244:
+	case ROC_TIM_CLK_SRC_BTS:

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#416: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:245:
+		return base + TIM_LF_FR_RN_BTS;

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#418: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:247:
+		return ROC_TIM_CLK_SRC_INVALID;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#478: FILE: drivers/event/cnxk/cnxk_tim_worker.h:135:
+		tim_ring->tick_fn(tim_ring->tbase) - tim_ring->ring_start_cyc;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#478: FILE: drivers/event/cnxk/cnxk_tim_worker.h:135:
+		tim_ring->tick_fn(tim_ring->tbase) - tim_ring->ring_start_cyc;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#478: FILE: drivers/event/cnxk/cnxk_tim_worker.h:135:
+		tim_ring->tick_fn(tim_ring->tbase) - tim_ring->ring_start_cyc;

total: 0 errors, 54 warnings, 351 lines checked

       reply	other threads:[~2022-07-19 11:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220719111125.8276-4-pbhagavatula@marvell.com>
2022-07-19 11:12 ` checkpatch [this message]
2022-07-19 12:18 ` |SUCCESS| " 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=20220719111253.C54C01231C5@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).