From: kernel test robot <lkp@intel.com>
To: Dominik Kaszewski <dominik.kaszewski@amd.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Alex Deucher <alexander.deucher@amd.com>,
Alvin Lee <alvin.lee2@amd.com>, Roman Li <roman.li@amd.com>
Subject: drivers/gpu/drm/amd/amdgpu/../display/dc/dc_fused_io.c:103:56: error: invalid use of undefined type 'struct gpio'
Date: Fri, 06 Mar 2026 14:05:48 +0800 [thread overview]
Message-ID: <202603061343.CyA71vlH-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 5ee8dbf54602dc340d6235b1d6aa17c0f283f48c
commit: ce801e5d6c1bac228bf10f75e8bede4285c58282 drm/amd/display: HDCP Locality check using DMUB Fused IO
date: 11 months ago
config: mips-randconfig-r072-20260306 (https://download.01.org/0day-ci/archive/20260306/202603061343.CyA71vlH-lkp@intel.com/config)
compiler: mips-linux-gcc (GCC) 10.5.0
smatch: v0.5.0-9004-gb810ac53
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260306/202603061343.CyA71vlH-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/202603061343.CyA71vlH-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_fused_io.c: In function 'dm_atomic_write_poll_read_i2c':
>> drivers/gpu/drm/amd/amdgpu/../display/dc/dc_fused_io.c:103:56: error: invalid use of undefined type 'struct gpio'
103 | const uint32_t ddc_line = link->ddc->ddc_pin->pin_data->en;
| ^~
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_fused_io.c: In function 'dm_atomic_write_poll_read_aux':
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_fused_io.c:130:56: error: invalid use of undefined type 'struct gpio'
130 | const uint32_t ddc_line = link->ddc->ddc_pin->pin_data->en;
| ^~
vim +103 drivers/gpu/drm/amd/amdgpu/../display/dc/dc_fused_io.c
90
91 bool dm_atomic_write_poll_read_i2c(
92 struct dc_link *link,
93 const struct mod_hdcp_atomic_op_i2c *write,
94 const struct mod_hdcp_atomic_op_i2c *poll,
95 struct mod_hdcp_atomic_op_i2c *read,
96 uint32_t poll_timeout_us,
97 uint8_t poll_mask_msb
98 )
99 {
100 if (!link)
101 return false;
102
> 103 const uint32_t ddc_line = link->ddc->ddc_pin->pin_data->en;
104 union dmub_rb_cmd commands[3] = { 0 };
105 const bool converted = op_i2c_convert(&commands[0], write, FUSED_REQUEST_WRITE, ddc_line)
106 && op_i2c_convert(&commands[1], poll, FUSED_REQUEST_POLL, ddc_line)
107 && op_i2c_convert(&commands[2], read, FUSED_REQUEST_READ, ddc_line);
108
109 if (!converted)
110 return false;
111
112 const bool result = atomic_write_poll_read(link, commands, poll_timeout_us, poll_mask_msb);
113
114 memcpy(read->data, commands[0].fused_io.request.buffer, read->size);
115 return result;
116 }
117
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-06 6:06 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=202603061343.CyA71vlH-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexander.deucher@amd.com \
--cc=alvin.lee2@amd.com \
--cc=dominik.kaszewski@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=roman.li@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