From: kernel test robot <lkp@intel.com>
To: Frank Li <Frank.Li@nxp.com>,
vkoul@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, dmaengine@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
peng.fan@nxp.com, joy.zou@nxp.com, shenwei.wang@nxp.com,
imx@lists.linux.dev
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v1 10/12] dmaengine: fsl-edma: move tcd into struct fsl_dma_chan
Date: Sat, 27 May 2023 19:58:22 +0800 [thread overview]
Message-ID: <202305271951.gmRobs3a-lkp@intel.com> (raw)
In-Reply-To: <20230526143639.1037099-11-Frank.Li@nxp.com>
Hi Frank,
kernel test robot noticed the following build warnings:
[auto build test WARNING on vkoul-dmaengine/next]
[also build test WARNING on robh/for-next linus/master v6.4-rc3 next-20230525]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Frank-Li/dmaengine-fsl-edma-clean-up-EXPORT_SYMBOL_GPL-in-fsl-edma-common-c/20230526-224442
base: https://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine.git next
patch link: https://lore.kernel.org/r/20230526143639.1037099-11-Frank.Li%40nxp.com
patch subject: [PATCH v1 10/12] dmaengine: fsl-edma: move tcd into struct fsl_dma_chan
config: i386-randconfig-s003-20230526 (https://download.01.org/0day-ci/archive/20230527/202305271951.gmRobs3a-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-39-gce1a6720-dirty
# https://github.com/intel-lab-lkp/linux/commit/913c495a6c017a70bd6d7a518a9edbd361212985
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Frank-Li/dmaengine-fsl-edma-clean-up-EXPORT_SYMBOL_GPL-in-fsl-edma-common-c/20230526-224442
git checkout 913c495a6c017a70bd6d7a518a9edbd361212985
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 olddefconfig
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash drivers/dma/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202305271951.gmRobs3a-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/dma/fsl-edma-common.c:367:9: sparse: sparse: cast from restricted __le32
drivers/dma/fsl-edma-common.c:367:9: sparse: sparse: cast from restricted __le32
drivers/dma/fsl-edma-common.c:368:9: sparse: sparse: cast from restricted __le32
drivers/dma/fsl-edma-common.c:368:9: sparse: sparse: cast from restricted __le32
drivers/dma/fsl-edma-common.c:370:9: sparse: sparse: cast from restricted __le16
drivers/dma/fsl-edma-common.c:370:9: sparse: sparse: cast from restricted __le16
drivers/dma/fsl-edma-common.c:371:9: sparse: sparse: incorrect type in argument 2 (different base types) @@ expected unsigned short [usertype] val @@ got restricted __le16 [usertype] soff @@
drivers/dma/fsl-edma-common.c:371:9: sparse: expected unsigned short [usertype] val
drivers/dma/fsl-edma-common.c:371:9: sparse: got restricted __le16 [usertype] soff
>> drivers/dma/fsl-edma-common.c:371:9: sparse: sparse: incorrect type in argument 2 (different base types) @@ expected unsigned int [usertype] val @@ got restricted __le16 [usertype] soff @@
drivers/dma/fsl-edma-common.c:371:9: sparse: expected unsigned int [usertype] val
drivers/dma/fsl-edma-common.c:371:9: sparse: got restricted __le16 [usertype] soff
drivers/dma/fsl-edma-common.c:373:9: sparse: sparse: cast from restricted __le32
drivers/dma/fsl-edma-common.c:373:9: sparse: sparse: cast from restricted __le32
drivers/dma/fsl-edma-common.c:374:9: sparse: sparse: cast from restricted __le32
drivers/dma/fsl-edma-common.c:374:9: sparse: sparse: cast from restricted __le32
drivers/dma/fsl-edma-common.c:376:9: sparse: sparse: cast from restricted __le16
drivers/dma/fsl-edma-common.c:376:9: sparse: sparse: cast from restricted __le16
drivers/dma/fsl-edma-common.c:377:9: sparse: sparse: cast from restricted __le16
drivers/dma/fsl-edma-common.c:377:9: sparse: sparse: cast from restricted __le16
drivers/dma/fsl-edma-common.c:378:9: sparse: sparse: cast from restricted __le16
drivers/dma/fsl-edma-common.c:378:9: sparse: sparse: cast from restricted __le16
drivers/dma/fsl-edma-common.c:380:9: sparse: sparse: cast from restricted __le32
drivers/dma/fsl-edma-common.c:380:9: sparse: sparse: cast from restricted __le32
drivers/dma/fsl-edma-common.c:388:9: sparse: sparse: cast from restricted __le16
drivers/dma/fsl-edma-common.c:388:9: sparse: sparse: cast from restricted __le16
vim +371 drivers/dma/fsl-edma-common.c
353
354 static void fsl_edma_set_tcd_regs(struct fsl_edma_chan *fsl_chan,
355 struct fsl_edma_hw_tcd *tcd)
356 {
357 u16 csr = 0;
358
359 /*
360 * TCD parameters are stored in struct fsl_edma_hw_tcd in little
361 * endian format. However, we need to load the TCD registers in
362 * big- or little-endian obeying the eDMA engine model endian,
363 * and this is performed from specific edma_write functions
364 */
365 edma_write_tcdreg(fsl_chan, 0, csr);
366
367 edma_write_tcdreg(fsl_chan, (s32)tcd->saddr, saddr);
368 edma_write_tcdreg(fsl_chan, (s32)tcd->daddr, daddr);
369
370 edma_write_tcdreg(fsl_chan, (s16)tcd->attr, attr);
> 371 edma_write_tcdreg(fsl_chan, tcd->soff, soff);
372
373 edma_write_tcdreg(fsl_chan, (s32)tcd->nbytes, nbytes);
374 edma_write_tcdreg(fsl_chan, (s32)tcd->slast, slast);
375
376 edma_write_tcdreg(fsl_chan, (s16)tcd->citer, citer);
377 edma_write_tcdreg(fsl_chan, (s16)tcd->biter, biter);
378 edma_write_tcdreg(fsl_chan, (s16)tcd->doff, doff);
379
380 edma_write_tcdreg(fsl_chan, (s32)tcd->dlast_sga, dlast_sga);
381
382 if (fsl_chan->is_sw) {
383 csr = le16_to_cpu(tcd->csr);
384 csr |= EDMA_TCD_CSR_START;
385 tcd->csr = cpu_to_le16(csr);
386 }
387
388 edma_write_tcdreg(fsl_chan, (s16)tcd->csr, csr);
389 }
390
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-05-27 11:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 14:36 [PATCH v1 00/12] dmaengine: edma: add freescale edma v3 support Frank Li
2023-05-26 14:36 ` [PATCH v1 01/12] dmaengine: fsl-edma: clean up EXPORT_SYMBOL_GPL in fsl-edma-common.c Frank Li
2023-05-26 14:36 ` [PATCH v1 02/12] dmaengine: fsl-edma: clean up fsl_edma_irq_exit() Frank Li
2023-05-26 14:36 ` [PATCH v1 03/12] dmaengine: fsl-edma: transition from bool fields to bitmask flags in drvdata Frank Li
2023-05-26 14:36 ` [PATCH v1 04/12] dmaengine: fsl-edma: remove v3 from enum edma_version Frank Li
2023-05-26 14:36 ` [PATCH v1 05/12] dmaengine: fsl-edma: move common IRQ handler to common.c Frank Li
2023-05-26 14:36 ` [PATCH v1 06/12] dmaengine: fsl-edma: simply ATTR_DSIZE and ATTR_SSIZE by using ffs() Frank Li
2023-05-26 14:36 ` [PATCH v1 07/12] dmaengine: fsl-edma: refactor using devm_clk_get_enabled Frank Li
2023-05-26 14:36 ` [PATCH v1 08/12] dmaengine: fsl-edma: move clearing of register interrupt into setup_irq function Frank Li
2023-05-26 14:36 ` [PATCH v1 09/12] dmaengine: fsl-edma: refactor chan_name setup and safety Frank Li
2023-05-26 14:36 ` [PATCH v1 10/12] dmaengine: fsl-edma: move tcd into struct fsl_dma_chan Frank Li
2023-05-27 11:58 ` kernel test robot [this message]
2023-05-26 14:36 ` [PATCH v1 11/12] dmaengine: fsl-edma: integrate v3 support Frank Li
2023-05-27 18:06 ` kernel test robot
2023-05-26 14:36 ` [PATCH v1 12/12] dt-bindings: fsl-dma: fsl-edma: add edma3 compatible string Frank Li
2023-05-26 15:07 ` Rob Herring
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=202305271951.gmRobs3a-lkp@intel.com \
--to=lkp@intel.com \
--cc=Frank.Li@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=joy.zou@nxp.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=shenwei.wang@nxp.com \
--cc=vkoul@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.