From: kernel test robot <lkp@intel.com>
To: Arunpravin Paneer Selvam <Arunpravin.PaneerSelvam@amd.com>
Cc: oe-kbuild-all@lists.linux.dev,
"Linux Infrastructure" <z1.linuxinfra@amd.com>,
"Christian König" <christian.koenig@amd.com>
Subject: [agd5f:amd-staging-drm-next 1286/1302] drivers/gpu/drm/amd/amdgpu/amdgpu_seq64.c:168: warning: Function parameter or struct member 'gpu_addr' not described in 'amdgpu_seq64_alloc'
Date: Wed, 13 Nov 2024 00:27:03 +0800 [thread overview]
Message-ID: <202411130016.UBjT0j4D-lkp@intel.com> (raw)
tree: https://gitlab.freedesktop.org/agd5f/linux.git amd-staging-drm-next
head: 0bd74ab31ce2ca6e35c9f7f7c9b72bd9c78619ed
commit: 712361d6786e9601fe78fa9a50145e6bc6ab8f11 [1286/1302] drm/amdgpu: Add gpu_addr support to seq64 allocation
config: sparc-allmodconfig (https://download.01.org/0day-ci/archive/20241113/202411130016.UBjT0j4D-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241113/202411130016.UBjT0j4D-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/202411130016.UBjT0j4D-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/amd/amdgpu/amdgpu_seq64.c:168: warning: Function parameter or struct member 'gpu_addr' not described in 'amdgpu_seq64_alloc'
vim +168 drivers/gpu/drm/amd/amdgpu/amdgpu_seq64.c
c8031019dc95e3a Arunpravin Paneer Selvam 2023-10-10 153
c8031019dc95e3a Arunpravin Paneer Selvam 2023-10-10 154 /**
c8031019dc95e3a Arunpravin Paneer Selvam 2023-10-10 155 * amdgpu_seq64_alloc - Allocate a 64 bit memory
c8031019dc95e3a Arunpravin Paneer Selvam 2023-10-10 156 *
c8031019dc95e3a Arunpravin Paneer Selvam 2023-10-10 157 * @adev: amdgpu_device pointer
00a11f977beb752 Arunpravin Paneer Selvam 2024-01-11 158 * @va: VA to access the seq in process address space
00a11f977beb752 Arunpravin Paneer Selvam 2024-01-11 159 * @cpu_addr: CPU address to access the seq
c8031019dc95e3a Arunpravin Paneer Selvam 2023-10-10 160 *
c8031019dc95e3a Arunpravin Paneer Selvam 2023-10-10 161 * Alloc a 64 bit memory from seq64 pool.
c8031019dc95e3a Arunpravin Paneer Selvam 2023-10-10 162 *
c8031019dc95e3a Arunpravin Paneer Selvam 2023-10-10 163 * Returns:
c8031019dc95e3a Arunpravin Paneer Selvam 2023-10-10 164 * 0 on success or a negative error code on failure
c8031019dc95e3a Arunpravin Paneer Selvam 2023-10-10 165 */
712361d6786e960 Arunpravin Paneer Selvam 2024-10-30 166 int amdgpu_seq64_alloc(struct amdgpu_device *adev, u64 *va,
712361d6786e960 Arunpravin Paneer Selvam 2024-10-30 167 u64 *gpu_addr, u64 **cpu_addr)
c8031019dc95e3a Arunpravin Paneer Selvam 2023-10-10 @168 {
c8031019dc95e3a Arunpravin Paneer Selvam 2023-10-10 169 unsigned long bit_pos;
c8031019dc95e3a Arunpravin Paneer Selvam 2023-10-10 170
c8031019dc95e3a Arunpravin Paneer Selvam 2023-10-10 171 bit_pos = find_first_zero_bit(adev->seq64.used, adev->seq64.num_sem);
00a11f977beb752 Arunpravin Paneer Selvam 2024-01-11 172 if (bit_pos >= adev->seq64.num_sem)
00a11f977beb752 Arunpravin Paneer Selvam 2024-01-11 173 return -ENOSPC;
c8031019dc95e3a Arunpravin Paneer Selvam 2023-10-10 174
c8031019dc95e3a Arunpravin Paneer Selvam 2023-10-10 175 __set_bit(bit_pos, adev->seq64.used);
712361d6786e960 Arunpravin Paneer Selvam 2024-10-30 176
00a11f977beb752 Arunpravin Paneer Selvam 2024-01-11 177 *va = bit_pos * sizeof(u64) + amdgpu_seq64_get_va_base(adev);
712361d6786e960 Arunpravin Paneer Selvam 2024-10-30 178
712361d6786e960 Arunpravin Paneer Selvam 2024-10-30 179 if (gpu_addr)
712361d6786e960 Arunpravin Paneer Selvam 2024-10-30 180 *gpu_addr = bit_pos * sizeof(u64) + adev->seq64.gpu_addr;
712361d6786e960 Arunpravin Paneer Selvam 2024-10-30 181
00a11f977beb752 Arunpravin Paneer Selvam 2024-01-11 182 *cpu_addr = bit_pos + adev->seq64.cpu_base_addr;
c8031019dc95e3a Arunpravin Paneer Selvam 2023-10-10 183
c8031019dc95e3a Arunpravin Paneer Selvam 2023-10-10 184 return 0;
c8031019dc95e3a Arunpravin Paneer Selvam 2023-10-10 185 }
c8031019dc95e3a Arunpravin Paneer Selvam 2023-10-10 186
:::::: The code at line 168 was first introduced by commit
:::::: c8031019dc95e3ab7cc0b09f1894c5f52dc0c187 drm/amdgpu: Implement a new 64bit sequence memory driver
:::::: TO: Arunpravin Paneer Selvam <Arunpravin.PaneerSelvam@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:[~2024-11-12 16:27 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=202411130016.UBjT0j4D-lkp@intel.com \
--to=lkp@intel.com \
--cc=Arunpravin.PaneerSelvam@amd.com \
--cc=christian.koenig@amd.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=z1.linuxinfra@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 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.