From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android14-kiwi-6.1 7/7] drivers/mailbox/pcc.c:295:27: sparse: sparse: incorrect type in argument 1 (different base types)
Date: Sat, 28 Mar 2026 16:11:21 +0800 [thread overview]
Message-ID: <202603281659.lBbVpJSa-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android14-kiwi-6.1
head: d5b66ad86ec150afc5182b585139072bf0a60683
commit: 84c351bc07a99d470dd91696b991a30b39db01f0 [7/7] mailbox: pcc: Check before sending MCTP PCC response ACK
config: x86_64-randconfig-r112-20260324 (https://download.01.org/0day-ci/archive/20260328/202603281659.lBbVpJSa-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260328/202603281659.lBbVpJSa-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/202603281659.lBbVpJSa-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/mailbox/pcc.c:295:27: sparse: sparse: incorrect type in argument 1 (different base types) @@ expected restricted __le32 const [usertype] *p @@ got unsigned int * @@
drivers/mailbox/pcc.c:295:27: sparse: expected restricted __le32 const [usertype] *p
drivers/mailbox/pcc.c:295:27: sparse: got unsigned int *
vim +295 drivers/mailbox/pcc.c
271
272 static void check_and_ack(struct pcc_chan_info *pchan, struct mbox_chan *chan)
273 {
274 struct acpi_pcct_ext_pcc_shared_memory pcc_hdr;
275
276 if (pchan->type != ACPI_PCCT_TYPE_EXT_PCC_SLAVE_SUBSPACE)
277 return;
278 /* If the memory region has not been mapped, we cannot
279 * determine if we need to send the message, but we still
280 * need to set the cmd_update flag before returning.
281 */
282 if (pchan->chan.shmem == NULL) {
283 pcc_chan_reg_read_modify_write(&pchan->cmd_update);
284 return;
285 }
286 memcpy_fromio(&pcc_hdr, pchan->chan.shmem,
287 sizeof(struct acpi_pcct_ext_pcc_shared_memory));
288 /*
289 * The PCC slave subspace channel needs to set the command complete bit
290 * after processing message. If the PCC_ACK_FLAG is set, it should also
291 * ring the doorbell.
292 *
293 * The PCC master subspace channel clears chan_in_use to free channel.
294 */
> 295 if (le32_to_cpup(&pcc_hdr.flags) & PCC_ACK_FLAG_MASK)
296 pcc_send_data(chan, NULL);
297 else
298 pcc_chan_reg_read_modify_write(&pchan->cmd_update);
299 }
300
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-28 8:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202603281659.lBbVpJSa-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.