From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com,
Guenter Roeck <groeck@google.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [chrome-os:chromeos-5.10 56/65] drivers/gpu/drm/i915/pxp/intel_pxp_tee.c:212:6: warning: no previous prototype for 'intel_pxp_tee_end_one_fw_session'
Date: Wed, 22 Feb 2023 09:55:04 +0800 [thread overview]
Message-ID: <202302220926.IMAvSF5z-lkp@intel.com> (raw)
tree: https://chromium.googlesource.com/chromiumos/third_party/kernel chromeos-5.10
head: 3895b42e3e85433fec5339d2d937b4c57b1e0855
commit: 5b63195fa9e6028cdef57d18f19853bad0d33d03 [56/65] CHROMIUM: drm/i915/pxp: Mutisession version for Invalidate all PXP fw sessions during teardown
config: i386-randconfig-r033-20230220 (https://download.01.org/0day-ci/archive/20230222/202302220926.IMAvSF5z-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
reproduce (this is a W=1 build):
git remote add chrome-os https://chromium.googlesource.com/chromiumos/third_party/kernel
git fetch --no-tags chrome-os chromeos-5.10
git checkout 5b63195fa9e6028cdef57d18f19853bad0d33d03
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=i386 olddefconfig
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash drivers/gpu/drm/i915/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202302220926.IMAvSF5z-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/i915/pxp/intel_pxp_tee.c:212:6: warning: no previous prototype for 'intel_pxp_tee_end_one_fw_session' [-Wmissing-prototypes]
212 | void intel_pxp_tee_end_one_fw_session(struct intel_pxp *pxp, u32 session_id, bool is_alive)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/intel_pxp_tee_end_one_fw_session +212 drivers/gpu/drm/i915/pxp/intel_pxp_tee.c
211
> 212 void intel_pxp_tee_end_one_fw_session(struct intel_pxp *pxp, u32 session_id, bool is_alive)
213 {
214 struct drm_i915_private *i915 = pxp_to_gt(pxp)->i915;
215 struct pxp_inv_stream_key_in msg_in = {0};
216 struct pxp_inv_stream_key_out msg_out = {0};
217 int ret, trials = 0;
218
219 try_again:
220 memset(&msg_in, 0, sizeof(msg_in));
221 memset(&msg_out, 0, sizeof(msg_out));
222 msg_in.header.api_version = PXP_TEE_APIVER;
223 msg_in.header.command_id = PXP_TEE_INVALIDATE_STREAM_KEY;
224 msg_in.header.buffer_len = sizeof(msg_in) - sizeof(msg_in.header);
225
226 msg_in.header.extdata = FIELD_PREP(PXP_CMDHDR_EXTDATA_SESSION_VALID, 1);
227 msg_in.header.extdata |= FIELD_PREP(PXP_CMDHDR_EXTDATA_APP_TYPE, 0);
228 msg_in.header.extdata |= FIELD_PREP(PXP_CMDHDR_EXTDATA_SESSION_ID, session_id);
229
230 ret = intel_pxp_tee_io_message(pxp,
231 &msg_in, sizeof(msg_in),
232 &msg_out, sizeof(msg_out),
233 NULL);
234
235 /* Cleanup coherency between GT and Firmware is critical, so try again if it fails */
236 if ((ret || msg_out.header.status != 0x0) && ++trials < 3)
237 goto try_again;
238
239 if (ret)
240 drm_err(&i915->drm, "Failed to send tee msg for inv-stream-key-%d, ret=[%d]\n",
241 session_id, ret);
242 else if (msg_out.header.status != 0x0 && is_alive)
243 drm_warn(&i915->drm, "PXP firmware failed inv-stream-key-%d with status 0x%08x\n",
244 session_id, msg_out.header.status);
245 }
246
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-02-22 1: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=202302220926.IMAvSF5z-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=groeck@google.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 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.