From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:incoming-android15-6.6-desktop-chromeos 498/498] drivers/remoteproc/mediatek_apusys/mtk_apu_hw_logger.c:310:10: warning: returning 'int' from a function with return type 'struct mtk_apu_hw_logger *' makes pointer from integer without a cast
Date: Fri, 28 Mar 2025 08:56:16 +0800 [thread overview]
Message-ID: <202503280822.VoMCynL1-lkp@intel.com> (raw)
Hi Karl,
First bad commit (maybe != root cause):
tree: https://android.googlesource.com/kernel/common incoming-android15-6.6-desktop-chromeos
head: 971c23c737d79895eb40ddbbed5817f6ee6ea162
commit: 6861d60ceacc0798de74530b42a39ef0c801434e [498/498] CHROMIUM: remoteproc: mediatek: Enable APU rproc building
config: arm-randconfig-004-20250328 (https://download.01.org/0day-ci/archive/20250328/202503280822.VoMCynL1-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250328/202503280822.VoMCynL1-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/202503280822.VoMCynL1-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/remoteproc/mediatek_apusys/mtk_apu_config.c: In function 'mtk_apu_config_setup':
>> drivers/remoteproc/mediatek_apusys/mtk_apu_config.c:120:19: warning: assignment to 'uint64_t' {aka 'long long unsigned int'} from 'void *' makes integer from pointer without a cast [-Wint-conversion]
mdla_rv_mem->buf = mdla_buf;
^
--
In file included from drivers/remoteproc/mediatek_apusys/mtk_apu_hw_logger.c:11:
drivers/remoteproc/mediatek_apusys/mtk_apu_hw_logger.c: In function 'ioread32_atf':
drivers/remoteproc/mediatek_apusys/mtk_apu_hw_logger.c:132:45: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
dev_err(dev, "Not support addr: 0x%llx", (unsigned long long)addr[i]);
^
include/linux/dev_printk.h:110:23: note: in definition of macro 'dev_printk_index_wrap'
_p_func(dev, fmt, ##__VA_ARGS__); \
^~~~~~~~~~~
drivers/remoteproc/mediatek_apusys/mtk_apu_hw_logger.c:132:4: note: in expansion of macro 'dev_err'
dev_err(dev, "Not support addr: 0x%llx", (unsigned long long)addr[i]);
^~~~~~~
drivers/remoteproc/mediatek_apusys/mtk_apu_hw_logger.c: In function 'get_mtk_apu_hw_logger_device':
>> drivers/remoteproc/mediatek_apusys/mtk_apu_hw_logger.c:310:10: warning: returning 'int' from a function with return type 'struct mtk_apu_hw_logger *' makes pointer from integer without a cast [-Wint-conversion]
return -EPROBE_DEFER;
^
drivers/remoteproc/mediatek_apusys/mtk_apu_hw_logger.c:313:10: warning: returning 'int' from a function with return type 'struct mtk_apu_hw_logger *' makes pointer from integer without a cast [-Wint-conversion]
return -EINVAL;
^
vim +310 drivers/remoteproc/mediatek_apusys/mtk_apu_hw_logger.c
1516d6dc338235 Karl Li 2025-01-02 295
1516d6dc338235 Karl Li 2025-01-02 296 static struct platform_driver hw_logger_driver;
1516d6dc338235 Karl Li 2025-01-02 297 struct mtk_apu_hw_logger *get_mtk_apu_hw_logger_device(struct device_node *hw_logger_np)
1516d6dc338235 Karl Li 2025-01-02 298 {
1516d6dc338235 Karl Li 2025-01-02 299 struct platform_device *pdev;
1516d6dc338235 Karl Li 2025-01-02 300 struct device *dev;
1516d6dc338235 Karl Li 2025-01-02 301 struct mtk_apu_hw_logger *hw_logger_data;
1516d6dc338235 Karl Li 2025-01-02 302
1516d6dc338235 Karl Li 2025-01-02 303 pdev = of_find_device_by_node(hw_logger_np);
1516d6dc338235 Karl Li 2025-01-02 304 if (!pdev)
1516d6dc338235 Karl Li 2025-01-02 305 return ERR_PTR(-ENODEV);
1516d6dc338235 Karl Li 2025-01-02 306
1516d6dc338235 Karl Li 2025-01-02 307 dev = &pdev->dev;
1516d6dc338235 Karl Li 2025-01-02 308
1516d6dc338235 Karl Li 2025-01-02 309 if (!dev->driver)
1516d6dc338235 Karl Li 2025-01-02 @310 return -EPROBE_DEFER;
1516d6dc338235 Karl Li 2025-01-02 311
1516d6dc338235 Karl Li 2025-01-02 312 if (dev->driver != &hw_logger_driver.driver)
1516d6dc338235 Karl Li 2025-01-02 313 return -EINVAL;
1516d6dc338235 Karl Li 2025-01-02 314
1516d6dc338235 Karl Li 2025-01-02 315 hw_logger_data = dev_get_drvdata(dev);
1516d6dc338235 Karl Li 2025-01-02 316 put_device(dev);
1516d6dc338235 Karl Li 2025-01-02 317
1516d6dc338235 Karl Li 2025-01-02 318 return hw_logger_data;
1516d6dc338235 Karl Li 2025-01-02 319 }
1516d6dc338235 Karl Li 2025-01-02 320
:::::: The code at line 310 was first introduced by commit
:::::: 1516d6dc33823500488342fce50de7ad8c838abf CHROMIUM: remoteproc: mediatek: Add APU hw_logger
:::::: TO: Karl Li <karl.li@mediatek.corp-partner.google.com>
:::::: CC: Hubert Mazur <hmazur@google.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-03-28 0:57 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=202503280822.VoMCynL1-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.