From: kernel test robot <lkp@intel.com>
To: Shravan Kumar Ramani <shravankr@nvidia.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Hans de Goede <hdegoede@redhat.com>,
Vadim Pasternak <vadimp@nvidia.com>,
David Thompson <davthompson@nvidia.com>
Subject: drivers/platform/mellanox/mlxbf-pmc.c:1172:14: sparse: sparse: incorrect type in assignment (different address spaces)
Date: Sat, 19 Oct 2024 16:42:09 +0800 [thread overview]
Message-ID: <202410191601.5pf9Y9Iw-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 3d5ad2d4eca337e80f38df77de89614aa5aaceb9
commit: 423c3361855c1e81f1cb91728a2ac5ddfd2cbf16 platform/mellanox: mlxbf-pmc: Add support for BlueField-3
date: 1 year, 1 month ago
config: arm64-randconfig-r133-20241018 (https://download.01.org/0day-ci/archive/20241019/202410191601.5pf9Y9Iw-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 14.1.0
reproduce: (https://download.01.org/0day-ci/archive/20241019/202410191601.5pf9Y9Iw-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/202410191601.5pf9Y9Iw-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/platform/mellanox/mlxbf-pmc.c:1172:14: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void *addr @@ got void [noderef] __iomem * @@
drivers/platform/mellanox/mlxbf-pmc.c:1172:14: sparse: expected void *addr
drivers/platform/mellanox/mlxbf-pmc.c:1172:14: sparse: got void [noderef] __iomem *
>> drivers/platform/mellanox/mlxbf-pmc.c:1174:31: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void [noderef] __iomem *addr @@ got void *addr @@
drivers/platform/mellanox/mlxbf-pmc.c:1174:31: sparse: expected void [noderef] __iomem *addr
drivers/platform/mellanox/mlxbf-pmc.c:1174:31: sparse: got void *addr
drivers/platform/mellanox/mlxbf-pmc.c:1186:32: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void [noderef] __iomem *addr @@ got void *addr @@
drivers/platform/mellanox/mlxbf-pmc.c:1186:32: sparse: expected void [noderef] __iomem *addr
drivers/platform/mellanox/mlxbf-pmc.c:1186:32: sparse: got void *addr
drivers/platform/mellanox/mlxbf-pmc.c:1194:14: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void *addr @@ got void [noderef] __iomem * @@
drivers/platform/mellanox/mlxbf-pmc.c:1194:14: sparse: expected void *addr
drivers/platform/mellanox/mlxbf-pmc.c:1194:14: sparse: got void [noderef] __iomem *
drivers/platform/mellanox/mlxbf-pmc.c:1198:32: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void [noderef] __iomem *addr @@ got void *addr @@
drivers/platform/mellanox/mlxbf-pmc.c:1198:32: sparse: expected void [noderef] __iomem *addr
drivers/platform/mellanox/mlxbf-pmc.c:1198:32: sparse: got void *addr
drivers/platform/mellanox/mlxbf-pmc.c:1415:14: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void *addr @@ got void [noderef] __iomem * @@
drivers/platform/mellanox/mlxbf-pmc.c:1415:14: sparse: expected void *addr
drivers/platform/mellanox/mlxbf-pmc.c:1415:14: sparse: got void [noderef] __iomem *
drivers/platform/mellanox/mlxbf-pmc.c:1417:31: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void [noderef] __iomem *addr @@ got void *addr @@
drivers/platform/mellanox/mlxbf-pmc.c:1417:31: sparse: expected void [noderef] __iomem *addr
drivers/platform/mellanox/mlxbf-pmc.c:1417:31: sparse: got void *addr
drivers/platform/mellanox/mlxbf-pmc.c: note: in included file (through include/linux/mmzone.h, include/linux/gfp.h, include/linux/slab.h, ...):
include/linux/page-flags.h:242:46: sparse: sparse: self-comparison always evaluates to false
vim +1172 drivers/platform/mellanox/mlxbf-pmc.c
1163
1164 /* Method to handle crspace counter programming */
1165 static int mlxbf_pmc_program_crspace_counter(int blk_num, uint32_t cnt_num,
1166 uint32_t evt)
1167 {
1168 uint32_t word;
1169 void *addr;
1170 int ret;
1171
> 1172 addr = pmc->block[blk_num].mmio_base +
1173 (rounddown(cnt_num, 2) * MLXBF_PMC_CRSPACE_PERFSEL_SZ);
> 1174 ret = mlxbf_pmc_readl(addr, &word);
1175 if (ret)
1176 return ret;
1177
1178 if (cnt_num % 2) {
1179 word &= ~MLXBF_PMC_CRSPACE_PERFSEL1;
1180 word |= FIELD_PREP(MLXBF_PMC_CRSPACE_PERFSEL1, evt);
1181 } else {
1182 word &= ~MLXBF_PMC_CRSPACE_PERFSEL0;
1183 word |= FIELD_PREP(MLXBF_PMC_CRSPACE_PERFSEL0, evt);
1184 }
1185
1186 return mlxbf_pmc_write(addr, MLXBF_PMC_WRITE_REG_32, word);
1187 }
1188
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-10-19 8:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-19 8:42 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-12 11:11 drivers/platform/mellanox/mlxbf-pmc.c:1172:14: sparse: sparse: incorrect type in assignment (different address spaces) kernel test robot
2023-12-14 11:24 kernel test robot
2023-12-04 14:12 kernel test robot
2023-11-16 19:37 kernel test robot
2023-11-16 16:40 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=202410191601.5pf9Y9Iw-lkp@intel.com \
--to=lkp@intel.com \
--cc=davthompson@nvidia.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=shravankr@nvidia.com \
--cc=vadimp@nvidia.com \
/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.