|WARNING| pw142535 [PATCH 09/30] dma/dpaa2: add short FD support

automatic DPDK test reports
 help / color / mirror / Atom feed

From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Gagandeep Singh <g.singh@nxp.com>
Subject: |WARNING| pw142535 [PATCH 09/30] dma/dpaa2: add short FD support
Date: Fri, 19 Jul 2024 12:04:12 +0200 (CEST)	[thread overview]
Message-ID: <20240719100412.02241127EE2@dpdk.org> (raw)
In-Reply-To: <20240719100126.1150373-9-g.singh@nxp.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#103: 
performance than FLE.

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#104: 
1) Save index context in FD att field for short and FLE(NonSG).

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#106: 
3) Force 48 bits address for source address and fle according to spec.

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#132: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:547:
+	} else if (fle[DPAA2_QDMA_SRC_FLE].word4.fmt !=

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#132: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:547:
+	} else if (fle[DPAA2_QDMA_SRC_FLE].word4.fmt !=

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#166: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:640:
+	dpaa2_qdma_fd_set_addr(fd, fle_iova);

WARNING:TYPO_SPELLING: 'ser' may be misspelled - perhaps 'set'?
#185: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:696:
+	struct dpaa2_qdma_rbp *rbp, int ser)

WARNING:TYPO_SPELLING: 'ser' may be misspelled - perhaps 'set'?
#195: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:706:
+	fd->simple_pci.ser = ser;

WARNING:TYPO_SPELLING: 'ser' may be misspelled - perhaps 'set'?
#195: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:706:
+	fd->simple_pci.ser = ser;

WARNING:TYPO_SPELLING: 'ser' may be misspelled - perhaps 'set'?
#196: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:707:
+	if (ser)

WARNING:TYPO_SPELLING: 'SER' may be misspelled - perhaps 'SET'?
#197: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:708:
+		fd->simple.frc |= QDMA_SER_CTX;

WARNING:TYPO_SPELLING: 'ser' may be misspelled - perhaps 'set'?
#228: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:739:
+	uint32_t len, struct qbman_fd *fd, int ser)

WARNING:TYPO_SPELLING: 'ser' may be misspelled - perhaps 'set'?
#238: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:749:
+	fd->simple_ddr.ser = ser;

WARNING:TYPO_SPELLING: 'ser' may be misspelled - perhaps 'set'?
#238: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:749:
+	fd->simple_ddr.ser = ser;

WARNING:TYPO_SPELLING: 'ser' may be misspelled - perhaps 'set'?
#239: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:750:
+	if (ser)

WARNING:TYPO_SPELLING: 'SER' may be misspelled - perhaps 'SET'?
#240: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:751:
+		fd->simple.frc |= QDMA_SER_CTX;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#317: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:820:
+	struct qdma_cntx_fle_sdd *fle_sdd = NULL;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#317: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:820:
+	struct qdma_cntx_fle_sdd *fle_sdd = NULL;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#318: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:821:
+	rte_iova_t fle_iova, sdd_iova;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#327: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:828:
+		fle_sdd = qdma_vq->cntx_fle_sdd[qdma_vq->slient_idx];

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#327: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:828:
+		fle_sdd = qdma_vq->cntx_fle_sdd[qdma_vq->slient_idx];

WARNING:TYPO_SPELLING: 'slient' may be misspelled - perhaps 'silent'?
#327: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:828:
+		fle_sdd = qdma_vq->cntx_fle_sdd[qdma_vq->slient_idx];

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#331: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:831:
+			(void **)&fle_sdd);

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#348: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:837:
+	fle = fle_sdd->fle;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#348: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:837:
+	fle = fle_sdd->fle;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#348: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:837:
+	fle = fle_sdd->fle;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#349: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:838:
+	fle_iova = (uint64_t)fle - qdma_vq->fle_iova2va_offset;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#349: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:838:
+	fle_iova = (uint64_t)fle - qdma_vq->fle_iova2va_offset;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#349: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:838:
+	fle_iova = (uint64_t)fle - qdma_vq->fle_iova2va_offset;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#352: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:840:
+	dpaa2_qdma_fd_set_addr(fd, fle_iova);

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#355: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:842:
+	DPAA2_SET_FD_FLC(fd, (uint64_t)fle);

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#360: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:846:
+			fle_sdd_pre_populate(fle_sdd,

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#360: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:846:
+			fle_sdd_pre_populate(fle_sdd,

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#375: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:853:
+		sdd = fle_sdd->sdd;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#376: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:854:
+		sdd_iova = (uint64_t)sdd - qdma_vq->fle_iova2va_offset;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#384: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:861:
+		dpaa2_qdma_long_fmt_dump(fle);

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#430: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:904:
+	uint16_t *free_space, uint16_t *fle_elem_nb)

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#436: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:910:
+	struct qdma_cntx_fle_sdd *fle_sdd;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#436: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:910:
+	struct qdma_cntx_fle_sdd *fle_sdd;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#451: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:925:
+		fle_sdd = (void *)DPAA2_GET_FD_FLC(fd);

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#452: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:926:
+		qdma_vq->fle_elem[*fle_elem_nb] = fle_sdd;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#452: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:926:
+		qdma_vq->fle_elem[*fle_elem_nb] = fle_sdd;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#452: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:926:
+		qdma_vq->fle_elem[*fle_elem_nb] = fle_sdd;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#453: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:927:
+		(*fle_elem_nb)++;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#462: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:936:
+		fle_sdd = (void *)DPAA2_GET_FD_FLC(fd);

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#463: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:937:
+		qdma_vq->fle_elem[*fle_elem_nb] = fle_sdd;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#463: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:937:
+		qdma_vq->fle_elem[*fle_elem_nb] = fle_sdd;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#463: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:937:
+		qdma_vq->fle_elem[*fle_elem_nb] = fle_sdd;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#464: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:938:
+		(*fle_elem_nb)++;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#465: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:939:
+		cntx_sg = container_of(fle_sdd,

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#466: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:940:
+				struct qdma_cntx_sg, fle_sdd);

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#518: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:1072:
+		ret = dpaa2_qdma_dq_fd(fd, qdma_vq, &free_space, &fle_elem_nb);

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#529: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:1098:
+	if (fle_elem_nb > 0) {

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#530: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:1099:
+		rte_mempool_put_bulk(qdma_vq->fle_pool,

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#531: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:1100:
+			qdma_vq->fle_elem, fle_elem_nb);

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#531: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:1100:
+			qdma_vq->fle_elem, fle_elem_nb);

WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#541: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:1335:
+	 * Short FD has higher perf than FLE.

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#563: FILE: drivers/dma/dpaa2/dpaa2_qdma.c:1365:
+				(void **)qdma_dev->vqs[vchan].cntx_fle_sdd,

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#682: FILE: drivers/dma/dpaa2/dpaa2_qdma.h:268:
+	uint64_t fle_iova2va_offset;

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#699: FILE: drivers/dma/dpaa2/dpaa2_qdma.h:290:
+	struct qdma_cntx_fle_sdd *cntx_fle_sdd[DPAA2_QDMA_MAX_DESC];

WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#699: FILE: drivers/dma/dpaa2/dpaa2_qdma.h:290:
+	struct qdma_cntx_fle_sdd *cntx_fle_sdd[DPAA2_QDMA_MAX_DESC];

total: 0 errors, 61 warnings, 581 lines checked

          parent reply	other threads:[~2024-07-19 10:04 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20240719100126.1150373-9-g.singh@nxp.com>]

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=20240719100412.02241127EE2@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=g.singh@nxp.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).