From: kernel test robot <lkp@intel.com>
To: Wenjing Liu <wenjing.liu@amd.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Infrastructure <z1.linuxinfra@amd.com>
Subject: [agd5f:amd-staging-drm-next 1664/1667] drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:4376: warning: Function parameter or member 'new_context' not described in 'commit_minimal_transition_state_in_dc_update'
Date: Sat, 16 Mar 2024 11:18:33 +0800 [thread overview]
Message-ID: <202403161131.dxq4D80e-lkp@intel.com> (raw)
tree: https://gitlab.freedesktop.org/agd5f/linux.git amd-staging-drm-next
head: 499a0313b53b2f712b4d60a5fe6fa38c52ebac8a
commit: 06653fc227525895ce25ab45c7ae652bd1359027 [1664/1667] drm/amd/display: Implement update_planes_and_stream_v3 sequence
config: loongarch-defconfig (https://download.01.org/0day-ci/archive/20240316/202403161131.dxq4D80e-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240316/202403161131.dxq4D80e-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/202403161131.dxq4D80e-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:4376: warning: Function parameter or member 'new_context' not described in 'commit_minimal_transition_state_in_dc_update'
>> drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:4376: warning: Function parameter or member 'srf_updates' not described in 'commit_minimal_transition_state_in_dc_update'
>> drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:4376: warning: Function parameter or member 'surface_count' not described in 'commit_minimal_transition_state_in_dc_update'
>> drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:4376: warning: Excess function parameter 'context' description in 'commit_minimal_transition_state_in_dc_update'
vim +4376 drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c
4353
4354 /**
4355 * commit_minimal_transition_state_in_dc_update - Commit a minimal state based
4356 * on current or new context
4357 *
4358 * @dc: DC structure, used to get the current state
4359 * @context: New context
4360 * @stream: Stream getting the update for the flip
4361 *
4362 * The function takes in current state and new state and determine a minimal
4363 * transition state as the intermediate step which could make the transition
4364 * between current and new states seamless. If found, it will commit the minimal
4365 * transition state and update current state to this minimal transition state
4366 * and return true, if not, it will return false.
4367 *
4368 * Return:
4369 * Return True if the minimal transition succeeded, false otherwise
4370 */
4371 static bool commit_minimal_transition_state_in_dc_update(struct dc *dc,
4372 struct dc_state *new_context,
4373 struct dc_stream_state *stream,
4374 struct dc_surface_update *srf_updates,
4375 int surface_count)
> 4376 {
4377 bool success = commit_minimal_transition_based_on_new_context(
4378 dc, new_context, stream, srf_updates,
4379 surface_count);
4380 if (!success)
4381 success = commit_minimal_transition_based_on_current_context(dc,
4382 new_context, stream);
4383 if (!success)
4384 DC_LOG_ERROR("Fail to commit a seamless minimal transition state between current and new states.\nThis pipe topology update is non-seamless!\n");
4385 return success;
4386 }
4387
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-03-16 3:19 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=202403161131.dxq4D80e-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wenjing.liu@amd.com \
--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.