From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [agd5f:amd-staging-drm-next 2266/2288] drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_optc.c:139:6: warning: no previous prototype for 'optc1_set_vupdate_keepout'
Date: Thu, 08 Apr 2021 09:16:31 +0800 [thread overview]
Message-ID: <202104080925.HbufQmay-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2675 bytes --]
tree: https://gitlab.freedesktop.org/agd5f/linux.git amd-staging-drm-next
head: 879e45ca7271a08b28ac346df8335e4ca5e380ea
commit: c170829c6bbace112f71ec14988b00b80176a41d [2266/2288] drm/amd/display: Move vupdate keepout programming from DCN20 to DCN10
config: i386-randconfig-r021-20210407 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
git remote add agd5f https://gitlab.freedesktop.org/agd5f/linux.git
git fetch --no-tags agd5f amd-staging-drm-next
git checkout c170829c6bbace112f71ec14988b00b80176a41d
# 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 warnings (new ones prefixed by >>):
>> drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_optc.c:139:6: warning: no previous prototype for 'optc1_set_vupdate_keepout' [-Wmissing-prototypes]
139 | void optc1_set_vupdate_keepout(struct timing_generator *optc,
| ^~~~~~~~~~~~~~~~~~~~~~~~~
drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_optc.c:879:6: warning: no previous prototype for 'optc1_setup_manual_trigger' [-Wmissing-prototypes]
879 | void optc1_setup_manual_trigger(struct timing_generator *optc)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_optc.c:897:6: warning: no previous prototype for 'optc1_program_manual_trigger' [-Wmissing-prototypes]
897 | void optc1_program_manual_trigger(struct timing_generator *optc)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/optc1_set_vupdate_keepout +139 drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_optc.c
133
134 /**
135 * Vupdate keepout can be set to a window to block the update lock for that pipe from changing.
136 * Start offset begins with vstartup and goes for x number of clocks,
137 * end offset starts from end of vupdate to x number of clocks.
138 */
> 139 void optc1_set_vupdate_keepout(struct timing_generator *optc,
140 struct vupdate_keepout_params *params)
141 {
142 struct optc *optc1 = DCN10TG_FROM_TG(optc);
143
144 REG_SET_3(OTG_VUPDATE_KEEPOUT, 0,
145 MASTER_UPDATE_LOCK_VUPDATE_KEEPOUT_START_OFFSET, params->start_offset,
146 MASTER_UPDATE_LOCK_VUPDATE_KEEPOUT_END_OFFSET, params->end_offset,
147 OTG_MASTER_UPDATE_LOCK_VUPDATE_KEEPOUT_EN, params->enable);
148 }
149
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 31322 bytes --]
reply other threads:[~2021-04-08 1:16 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=202104080925.HbufQmay-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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.