From: kernel test robot <lkp@intel.com>
To: Peng Ma <peng.ma@nxp.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Vinod Koul <vkoul@kernel.org>
Subject: drivers/dma/fsl-dpaa2-qdma/dpaa2-qdma.c:183:18: sparse: sparse: incorrect type in assignment (different base types)
Date: Tue, 19 Dec 2023 05:10:17 +0800 [thread overview]
Message-ID: <202312190533.Lbc18dxc-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 2cf4f94d8e8646803f8fb0facf134b0cd7fb691a
commit: 7fdf9b05c73b79c4d9a85b5a9905efa10ee482a6 dmaengine: fsl-dpaa2-qdma: Add NXP dpaa2 qDMA controller driver for Layerscape SoCs
date: 4 years, 2 months ago
config: arm64-randconfig-r112-20231117 (https://download.01.org/0day-ci/archive/20231219/202312190533.Lbc18dxc-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20231219/202312190533.Lbc18dxc-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202312190533.Lbc18dxc-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/dma/fsl-dpaa2-qdma/dpaa2-qdma.c:183:18: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned int [usertype] cmd @@ got restricted __le32 [usertype] @@
drivers/dma/fsl-dpaa2-qdma/dpaa2-qdma.c:183:18: sparse: expected unsigned int [usertype] cmd
drivers/dma/fsl-dpaa2-qdma/dpaa2-qdma.c:183:18: sparse: got restricted __le32 [usertype]
drivers/dma/fsl-dpaa2-qdma/dpaa2-qdma.c:188:26: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned int [usertype] cmd @@ got restricted __le32 [usertype] @@
drivers/dma/fsl-dpaa2-qdma/dpaa2-qdma.c:188:26: sparse: expected unsigned int [usertype] cmd
drivers/dma/fsl-dpaa2-qdma/dpaa2-qdma.c:188:26: sparse: got restricted __le32 [usertype]
drivers/dma/fsl-dpaa2-qdma/dpaa2-qdma.c:190:26: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned int [usertype] cmd @@ got restricted __le32 [usertype] @@
drivers/dma/fsl-dpaa2-qdma/dpaa2-qdma.c:190:26: sparse: expected unsigned int [usertype] cmd
drivers/dma/fsl-dpaa2-qdma/dpaa2-qdma.c:190:26: sparse: got restricted __le32 [usertype]
--
>> drivers/dma/fsl-dpaa2-qdma/dpdmai.c:81:24: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __le64 [usertype] @@ got restricted __le32 [usertype] @@
drivers/dma/fsl-dpaa2-qdma/dpdmai.c:81:24: sparse: expected restricted __le64 [usertype]
drivers/dma/fsl-dpaa2-qdma/dpdmai.c:81:24: sparse: got restricted __le32 [usertype]
>> drivers/dma/fsl-dpaa2-qdma/dpdmai.c:148:9: sparse: sparse: invalid assignment: |=
>> drivers/dma/fsl-dpaa2-qdma/dpdmai.c:148:9: sparse: left side has type restricted __le64
>> drivers/dma/fsl-dpaa2-qdma/dpdmai.c:148:9: sparse: right side has type unsigned long long
>> drivers/dma/fsl-dpaa2-qdma/dpdmai.c:148:9: sparse: sparse: invalid assignment: |=
>> drivers/dma/fsl-dpaa2-qdma/dpdmai.c:148:9: sparse: left side has type restricted __le64
>> drivers/dma/fsl-dpaa2-qdma/dpdmai.c:148:9: sparse: right side has type unsigned long long
vim +183 drivers/dma/fsl-dpaa2-qdma/dpaa2-qdma.c
170
171 /* first frame list for descriptor buffer */
172 static void
173 dpaa2_qdma_populate_first_framel(struct dpaa2_fl_entry *f_list,
174 struct dpaa2_qdma_comp *dpaa2_comp,
175 bool wrt_changed)
176 {
177 struct dpaa2_qdma_sd_d *sdd;
178
179 sdd = dpaa2_comp->desc_virt_addr;
180 memset(sdd, 0, 2 * (sizeof(*sdd)));
181
182 /* source descriptor CMD */
> 183 sdd->cmd = cpu_to_le32(QDMA_SD_CMD_RDTTYPE_COHERENT);
184 sdd++;
185
186 /* dest descriptor CMD */
187 if (wrt_changed)
188 sdd->cmd = cpu_to_le32(LX2160_QDMA_DD_CMD_WRTTYPE_COHERENT);
189 else
190 sdd->cmd = cpu_to_le32(QDMA_DD_CMD_WRTTYPE_COHERENT);
191
192 memset(f_list, 0, sizeof(struct dpaa2_fl_entry));
193
194 /* first frame list to source descriptor */
195 dpaa2_fl_set_addr(f_list, dpaa2_comp->desc_bus_addr);
196 dpaa2_fl_set_len(f_list, 0x20);
197 dpaa2_fl_set_format(f_list, QDMA_FL_FMT_SBF | QDMA_FL_SL_LONG);
198
199 /* bypass memory translation */
200 if (smmu_disable)
201 f_list->bpid = cpu_to_le16(QDMA_FL_BMT_ENABLE);
202 }
203
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-12-18 21:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 21:10 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-19 17:16 drivers/dma/fsl-dpaa2-qdma/dpaa2-qdma.c:183:18: sparse: sparse: incorrect type in assignment (different base types) kernel test robot
2020-08-27 0:12 kernel test robot
2020-08-27 0:12 ` kernel test robot
2020-07-08 13:14 kernel test robot
2020-07-08 13:14 ` kernel test 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=202312190533.Lbc18dxc-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peng.ma@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.