linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Peichen Huang <PeiChen.Huang@amd.com>
Cc: oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>,
	Alex Deucher <alexander.deucher@amd.com>,
	Cruise Hung <cruise.hung@amd.com>,
	George Shen <george.shen@amd.com>,
	Meenakshikumar Somasundaram <meenakshikumar.somasundaram@amd.com>,
	Alex Hung <alex.hung@amd.com>
Subject: [linux-next:master 12160/12393] drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:5768: warning: Function parameter or struct member 'tps' not described in 'dc_process_dmub_dpia_set_tps_notification'
Date: Wed, 18 Sep 2024 17:54:50 +0800	[thread overview]
Message-ID: <202409181703.IBSWVJgA-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   55bcd2e0d04c1171d382badef1def1fd04ef66c5
commit: fbeaa2f6f9b432a689e7d7e6b71459500338b8f5 [12160/12393] drm/amd/display: Restructure dpia link training
config: parisc-randconfig-001-20240127 (https://download.01.org/0day-ci/archive/20240918/202409181703.IBSWVJgA-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 13.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240918/202409181703.IBSWVJgA-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/202409181703.IBSWVJgA-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:5768: warning: Function parameter or struct member 'tps' not described in 'dc_process_dmub_dpia_set_tps_notification'
>> drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:5768: warning: Excess function parameter 'ts' description in 'dc_process_dmub_dpia_set_tps_notification'


vim +5768 drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c

  5757	
  5758	/**
  5759	 * dc_process_dmub_dpia_set_tps_notification - Submits tps notification
  5760	 *
  5761	 * @dc: [in] dc structure
  5762	 * @link_index: [in] link index
  5763	 * @ts: [in] request tps
  5764	 *
  5765	 * Submits set_tps_notification command to dmub via inbox message
  5766	 */
  5767	void dc_process_dmub_dpia_set_tps_notification(const struct dc *dc, uint32_t link_index, uint8_t tps)
> 5768	{
  5769		union dmub_rb_cmd cmd = {0};
  5770	
  5771		cmd.set_tps_notification.header.type = DMUB_CMD__DPIA;
  5772		cmd.set_tps_notification.header.sub_type = DMUB_CMD__DPIA_SET_TPS_NOTIFICATION;
  5773		cmd.set_tps_notification.tps_notification.instance = dc->links[link_index]->ddc_hw_inst;
  5774		cmd.set_tps_notification.tps_notification.tps = tps;
  5775	
  5776		dc_wake_and_execute_dmub_cmd(dc->ctx, &cmd, DM_DMUB_WAIT_TYPE_WAIT);
  5777	}
  5778	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


                 reply	other threads:[~2024-09-18  9:55 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=202409181703.IBSWVJgA-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=PeiChen.Huang@amd.com \
    --cc=alex.hung@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=cruise.hung@amd.com \
    --cc=george.shen@amd.com \
    --cc=linux-mm@kvack.org \
    --cc=meenakshikumar.somasundaram@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox