From: kernel test robot <lkp@intel.com>
To: Victor Lu <victorchengchi.lu@amd.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Alex Deucher <alexander.deucher@amd.com>,
Zhigang Luo <zhigang.luo@amd.com>
Subject: [linux-next:master 2339/10848] drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:576: warning: Function parameter or member 'xcc_id' not described in 'amdgpu_mm_wreg_mmio_rlc'
Date: Thu, 17 Aug 2023 15:11:19 +0800 [thread overview]
Message-ID: <202308171555.5mSXBst8-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 47762f08697484cf0c2f2904b8c52375ed26c8cb
commit: 8ed49dd1d3a7448744d57e1da2062b074cba2e49 [2339/10848] drm/amdgpu: Add RLCG interface driver implementation for gfx v9.4.3 (v3)
config: arc-randconfig-r013-20230817 (https://download.01.org/0day-ci/archive/20230817/202308171555.5mSXBst8-lkp@intel.com/config)
compiler: arceb-elf-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230817/202308171555.5mSXBst8-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/202308171555.5mSXBst8-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:576: warning: Function parameter or member 'xcc_id' not described in 'amdgpu_mm_wreg_mmio_rlc'
vim +576 drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
47ed4e1c93a6c7 Ken Wang 2017-07-04 563
03f2abb07e54b3 Yann Dirson 2021-12-14 564 /**
4cc9f86f851847 Tom St Denis 2022-01-07 565 * amdgpu_mm_wreg_mmio_rlc - write register either with direct/indirect mmio or with RLC path if in range
2e0cc4d48b91a8 Monk Liu 2020-03-10 566 *
71579346991927 Rajneesh Bhardwaj 2022-02-10 567 * @adev: amdgpu_device pointer
71579346991927 Rajneesh Bhardwaj 2022-02-10 568 * @reg: mmio/rlc register
71579346991927 Rajneesh Bhardwaj 2022-02-10 569 * @v: value to write
71579346991927 Rajneesh Bhardwaj 2022-02-10 570 *
71579346991927 Rajneesh Bhardwaj 2022-02-10 571 * this function is invoked only for the debugfs register access
03f2abb07e54b3 Yann Dirson 2021-12-14 572 */
f7ee1874b06cfd Hawking Zhang 2020-09-18 573 void amdgpu_mm_wreg_mmio_rlc(struct amdgpu_device *adev,
8ed49dd1d3a744 Victor Lu 2023-06-16 574 uint32_t reg, uint32_t v,
8ed49dd1d3a744 Victor Lu 2023-06-16 575 uint32_t xcc_id)
2e0cc4d48b91a8 Monk Liu 2020-03-10 @576 {
56b53c0b5aa5de Dennis Li 2021-03-10 577 if (amdgpu_device_skip_hw_access(adev))
bf36b52e781d74 Andrey Grodzovsky 2020-07-29 578 return;
bf36b52e781d74 Andrey Grodzovsky 2020-07-29 579
2e0cc4d48b91a8 Monk Liu 2020-03-10 580 if (amdgpu_sriov_fullaccess(adev) &&
2e0cc4d48b91a8 Monk Liu 2020-03-10 581 adev->gfx.rlc.funcs &&
2e0cc4d48b91a8 Monk Liu 2020-03-10 582 adev->gfx.rlc.funcs->is_rlcg_access_range) {
2e0cc4d48b91a8 Monk Liu 2020-03-10 583 if (adev->gfx.rlc.funcs->is_rlcg_access_range(adev, reg))
8ed49dd1d3a744 Victor Lu 2023-06-16 584 return amdgpu_sriov_wreg(adev, reg, v, 0, 0, xcc_id);
4cc9f86f851847 Tom St Denis 2022-01-07 585 } else if ((reg * 4) >= adev->rmmio_size) {
4cc9f86f851847 Tom St Denis 2022-01-07 586 adev->pcie_wreg(adev, reg * 4, v);
f7ee1874b06cfd Hawking Zhang 2020-09-18 587 } else {
f7ee1874b06cfd Hawking Zhang 2020-09-18 588 writel(v, ((void __iomem *)adev->rmmio) + (reg * 4));
47ed4e1c93a6c7 Ken Wang 2017-07-04 589 }
d38ceaf99ed015 Alex Deucher 2015-04-20 590 }
d38ceaf99ed015 Alex Deucher 2015-04-20 591
:::::: The code at line 576 was first introduced by commit
:::::: 2e0cc4d48b91a856a34027b093306c01c45d3a38 drm/amdgpu: revise RLCG access path
:::::: TO: Monk Liu <Monk.Liu@amd.com>
:::::: CC: Alex Deucher <alexander.deucher@amd.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-08-17 7:13 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=202308171555.5mSXBst8-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexander.deucher@amd.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=victorchengchi.lu@amd.com \
--cc=zhigang.luo@amd.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).