From: kernel test robot <lkp@intel.com>
To: Yunfei Dong <yunfei.dong@mediatek.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org,
Alexandre Courbot <acourbot@chromium.org>,
Hans Verkuil <hverkuil@xs4all.nl>
Subject: mtk_vcodec_fw.c:undefined reference to `scp_ipi_send'
Date: Tue, 3 Nov 2020 14:06:58 +0800 [thread overview]
Message-ID: <202011031454.Py58mDGE-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2558 bytes --]
Hi Yunfei,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: b7cbaf59f62f8ab8f157698f9e31642bff525bd0
commit: c7244811b1c951dca812079d16b17cb241882a80 media: mtk-vcodec: add SCP firmware ops
date: 5 weeks ago
config: i386-randconfig-a012-20201103 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c7244811b1c951dca812079d16b17cb241882a80
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout c7244811b1c951dca812079d16b17cb241882a80
# save the attached .config to linux build tree
make W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
ld: drivers/media/platform/mtk-vcodec/mtk_vcodec_fw.o: in function `mtk_vcodec_scp_ipi_send':
>> mtk_vcodec_fw.c:(.text+0x80): undefined reference to `scp_ipi_send'
ld: drivers/media/platform/mtk-vcodec/mtk_vcodec_fw.o: in function `mtk_vcodec_scp_set_ipi_register':
>> mtk_vcodec_fw.c:(.text+0x90): undefined reference to `scp_ipi_register'
ld: drivers/media/platform/mtk-vcodec/mtk_vcodec_fw.o: in function `mtk_vcodec_vpu_scp_dm_addr':
>> mtk_vcodec_fw.c:(.text+0x9d): undefined reference to `scp_mapping_dm_addr'
ld: drivers/media/platform/mtk-vcodec/mtk_vcodec_fw.o: in function `mtk_vcodec_scp_get_venc_capa':
>> mtk_vcodec_fw.c:(.text+0xaa): undefined reference to `scp_get_venc_hw_capa'
ld: drivers/media/platform/mtk-vcodec/mtk_vcodec_fw.o: in function `mtk_vcodec_scp_get_vdec_capa':
>> mtk_vcodec_fw.c:(.text+0xb7): undefined reference to `scp_get_vdec_hw_capa'
ld: drivers/media/platform/mtk-vcodec/mtk_vcodec_fw.o: in function `mtk_vcodec_scp_load_firmware':
>> mtk_vcodec_fw.c:(.text+0xc4): undefined reference to `scp_get_rproc'
>> ld: mtk_vcodec_fw.c:(.text+0xc9): undefined reference to `rproc_boot'
ld: drivers/media/platform/mtk-vcodec/mtk_vcodec_fw.o: in function `mtk_vcodec_fw_select':
mtk_vcodec_fw.c:(.text+0x183): undefined reference to `scp_get'
ld: drivers/media/platform/mtk-vcodec/mtk_vcodec_fw.o: in function `mtk_vcodec_fw_release':
mtk_vcodec_fw.c:(.text+0x217): undefined reference to `scp_put'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 44699 bytes --]
reply other threads:[~2020-11-03 6:07 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=202011031454.Py58mDGE-lkp@intel.com \
--to=lkp@intel.com \
--cc=acourbot@chromium.org \
--cc=hverkuil@xs4all.nl \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=yunfei.dong@mediatek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).