From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android16-6.12-desktop 2/2] drivers/gpu/drm/xe/xe_work_period.c:454: warning: Function parameter or struct member 'xe' not described in 'xe_work_period_suspend'
Date: Wed, 3 Dec 2025 12:52:32 +0800 [thread overview]
Message-ID: <202512031226.Kyipeejr-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android16-6.12-desktop
head: db0c22e7c787ae43e1961147bbefee206bb885ee
commit: c1b1ceb28458b92550c1e06b11f7d5b05bb36be8 [2/2] ANDROID: drm/xe: Add gpu_work_period tracepoint
config: i386-allmodconfig (https://download.01.org/0day-ci/archive/20251203/202512031226.Kyipeejr-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251203/202512031226.Kyipeejr-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/202512031226.Kyipeejr-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/xe/xe_work_period.c:454: warning: Function parameter or struct member 'xe' not described in 'xe_work_period_suspend'
>> drivers/gpu/drm/xe/xe_work_period.c:474: warning: Function parameter or struct member 'xe' not described in 'xe_work_period_resume'
>> drivers/gpu/drm/xe/xe_work_period.c:500: warning: Function parameter or struct member 'xe' not described in 'xe_work_period_init'
>> drivers/gpu/drm/xe/xe_work_period.c:515: warning: Function parameter or struct member 'xe' not described in 'xe_work_period_fini'
vim +454 drivers/gpu/drm/xe/xe_work_period.c
442
443 /**
444 * xe_work_period_suspend() - cancel all pending @xe_user workers
445 * @xe - the xe device
446 *
447 * Normally called during system suspend handlers or during @xe_device cleanup.
448 *
449 * Context: Process context. May take xe->work_period.lock if worker holds the
450 * last ref for its @xe_user.
451 * Return: void
452 */
453 void xe_work_period_suspend(struct xe_device *xe)
> 454 {
455 struct xe_user *user = NULL;
456 unsigned long i = 0;
457
458 xa_for_each(&xe->work_period.users, i, user) {
459 if (cancel_delayed_work_sync(&user->delay_work))
460 xe_user_put(user);
461 }
462 }
463
464 /**
465 * xe_work_period_resume() - schedule all previously suspended @xe_user workers
466 * @xe - the xe device
467 *
468 * Normally called during system resume handlers.
469 *
470 * Context: Process context.
471 * Return: void
472 */
473 void xe_work_period_resume(struct xe_device *xe)
> 474 {
475 struct xe_user *user = NULL;
476 unsigned long i = 0;
477
478 /* no need to lock because schedule_next_work() atomically checks the
479 * validity of each user and acquires its own ref. If a user is dropped
480 * between reaching it in this iterator and attempting to get a ref, it
481 * can be safely excluded from rescheduling since there are no other
482 * remaining reference holders.
483 */
484 xa_for_each(&xe->work_period.users, i, user) {
485 user->last_timestamp_ns = ktime_get_raw_ns();
486 schedule_next_work(user);
487 }
488 }
489
490 /**
491 * xe_work_period_init() - setup work period reporting
492 * @xe - the xe device
493 *
494 * Normally called during @xe_device setup.
495 *
496 * Context: Any context.
497 * Return: void
498 */
499 void xe_work_period_init(struct xe_device *xe)
> 500 {
501 mutex_init(&xe->work_period.lock);
502 xa_init_flags(&xe->work_period.users, XA_FLAGS_ALLOC1);
503 }
504
505 /**
506 * xe_work_period_fini() - cleanup work period reporting
507 * @xe - the xe device
508 *
509 * Normally called during @xe_device cleanup.
510 *
511 * Context: Process context.
512 * Return: void
513 */
514 void xe_work_period_fini(struct xe_device *xe)
> 515 {
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-12-03 4:53 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=202512031226.Kyipeejr-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.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.