From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com,
Guenter Roeck <groeck@google.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [chrome-os:chromeos-6.1 103/106] drivers/media/platform/mediatek/isp/isp_7x/mtk-hcp/mtk-hcp.c:243:24: sparse: sparse: Using plain integer as NULL pointer
Date: Thu, 23 May 2024 11:45:15 +0800 [thread overview]
Message-ID: <202405231125.tVTr30AQ-lkp@intel.com> (raw)
tree: https://chromium.googlesource.com/chromiumos/third_party/kernel chromeos-6.1
head: e0a8432e750018bfe19402216e10553e4261aab7
commit: eba329daee52c5bc6a7d2ee896053b318f90ca50 [103/106] CHROMIUM: media: platform: mediatek: isp: NDD for IMGSYS RED SCP migration
config: arm64-randconfig-r111-20240523 (https://download.01.org/0day-ci/archive/20240523/202405231125.tVTr30AQ-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20240523/202405231125.tVTr30AQ-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/202405231125.tVTr30AQ-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/media/platform/mediatek/isp/isp_7x/mtk-hcp/mtk-hcp.c:243:24: sparse: sparse: Using plain integer as NULL pointer
drivers/media/platform/mediatek/isp/isp_7x/mtk-hcp/mtk-hcp.c:354:72: sparse: sparse: cast truncates bits from constant value (3ffffffff becomes ffffffff)
--
>> drivers/media/platform/mediatek/isp/isp_7x/mtk-ipesys-me/mtk-ipesys-me.c:87:16: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void *reg_va @@ got void [noderef] __iomem * @@
drivers/media/platform/mediatek/isp/isp_7x/mtk-ipesys-me/mtk-ipesys-me.c:87:16: sparse: expected void *reg_va
drivers/media/platform/mediatek/isp/isp_7x/mtk-ipesys-me/mtk-ipesys-me.c:87:16: sparse: got void [noderef] __iomem *
>> drivers/media/platform/mediatek/isp/isp_7x/mtk-ipesys-me/mtk-ipesys-me.c:95:25: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void volatile [noderef] __iomem *addr @@ got void *reg_va @@
drivers/media/platform/mediatek/isp/isp_7x/mtk-ipesys-me/mtk-ipesys-me.c:95:25: sparse: expected void volatile [noderef] __iomem *addr
drivers/media/platform/mediatek/isp/isp_7x/mtk-ipesys-me/mtk-ipesys-me.c:95:25: sparse: got void *reg_va
drivers/media/platform/mediatek/isp/isp_7x/mtk-ipesys-me/mtk-ipesys-me.c:102:33: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void volatile [noderef] __iomem *addr @@ got void *reg_va @@
drivers/media/platform/mediatek/isp/isp_7x/mtk-ipesys-me/mtk-ipesys-me.c:102:33: sparse: expected void volatile [noderef] __iomem *addr
drivers/media/platform/mediatek/isp/isp_7x/mtk-ipesys-me/mtk-ipesys-me.c:102:33: sparse: got void *reg_va
drivers/media/platform/mediatek/isp/isp_7x/mtk-ipesys-me/mtk-ipesys-me.c:109:33: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void volatile [noderef] __iomem *addr @@ got void *reg_va @@
drivers/media/platform/mediatek/isp/isp_7x/mtk-ipesys-me/mtk-ipesys-me.c:109:33: sparse: expected void volatile [noderef] __iomem *addr
drivers/media/platform/mediatek/isp/isp_7x/mtk-ipesys-me/mtk-ipesys-me.c:109:33: sparse: got void *reg_va
drivers/media/platform/mediatek/isp/isp_7x/mtk-ipesys-me/mtk-ipesys-me.c:115:17: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void volatile [noderef] __iomem *addr @@ got void *reg_va @@
drivers/media/platform/mediatek/isp/isp_7x/mtk-ipesys-me/mtk-ipesys-me.c:115:17: sparse: expected void volatile [noderef] __iomem *addr
drivers/media/platform/mediatek/isp/isp_7x/mtk-ipesys-me/mtk-ipesys-me.c:115:17: sparse: got void *reg_va
vim +243 drivers/media/platform/mediatek/isp/isp_7x/mtk-hcp/mtk-hcp.c
235
236 void *mtk_hcp_get_reserve_mem_virt(struct platform_device *pdev, unsigned int id)
237 {
238 struct mtk_hcp *hcp_dev = platform_get_drvdata(pdev);
239 void *buffer;
240
241 if ((id < 0) || (id >= NUMS_MEM_ID)) {
242 pr_info("[HCP] no reserve memory for %d", id);
> 243 return 0;
244 } else {
245 if (!hcp_dev->data->get_reserve_mem_virt) {
246 dev_info(&pdev->dev, "%s: not supported\n", __func__);
247 return NULL;
248 }
249
250 buffer = hcp_dev->data->get_reserve_mem_virt(id);
251 if (!buffer)
252 dev_info(&pdev->dev, "%s: get_reserve_mem_virt is null for id:%u\n", __func__, id);
253
254 return buffer;
255 }
256 }
257 EXPORT_SYMBOL(mtk_hcp_get_reserve_mem_virt);
258
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-05-23 3:45 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=202405231125.tVTr30AQ-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=groeck@google.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.