Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: rodrigo.vivi@intel.com, oe-kbuild-all@lists.linux.dev
Subject: Re: [Intel-gfx] [PATCH] drm/i915/display: Communicate display power demands to pcode more accurately
Date: Mon, 27 Feb 2023 20:20:31 +0800	[thread overview]
Message-ID: <202302272011.1iLXtakR-lkp@intel.com> (raw)
In-Reply-To: <20230227095253.22415-1-stanislav.lisovskiy@intel.com>

Hi Stanislav,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on drm-tip/drm-tip]

url:    https://github.com/intel-lab-lkp/linux/commits/Stanislav-Lisovskiy/drm-i915-display-Communicate-display-power-demands-to-pcode-more-accurately/20230227-175404
base:   git://anongit.freedesktop.org/drm/drm-tip drm-tip
patch link:    https://lore.kernel.org/r/20230227095253.22415-1-stanislav.lisovskiy%40intel.com
patch subject: [Intel-gfx] [PATCH] drm/i915/display: Communicate display power demands to pcode more accurately
config: x86_64-rhel-8.3 (https://download.01.org/0day-ci/archive/20230227/202302272011.1iLXtakR-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
reproduce (this is a W=1 build):
        # https://github.com/intel-lab-lkp/linux/commit/bc4de3b25bbf043f68ef862c45f975b79af938be
        git remote add linux-review https://github.com/intel-lab-lkp/linux
        git fetch --no-tags linux-review Stanislav-Lisovskiy/drm-i915-display-Communicate-display-power-demands-to-pcode-more-accurately/20230227-175404
        git checkout bc4de3b25bbf043f68ef862c45f975b79af938be
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        make W=1 O=build_dir ARCH=x86_64 olddefconfig
        make W=1 O=build_dir ARCH=x86_64 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/202302272011.1iLXtakR-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/i915/display/intel_cdclk.c:3006:6: warning: no previous prototype for 'intel_cdclk_need_serialize' [-Wmissing-prototypes]
    3006 | bool intel_cdclk_need_serialize(struct drm_i915_private *i915,
         |      ^~~~~~~~~~~~~~~~~~~~~~~~~~


vim +/intel_cdclk_need_serialize +3006 drivers/gpu/drm/i915/display/intel_cdclk.c

  3005	
> 3006	bool intel_cdclk_need_serialize(struct drm_i915_private *i915,
  3007					const struct intel_cdclk_state *old_cdclk_state,
  3008					const struct intel_cdclk_state *new_cdclk_state)
  3009	{
  3010		/*
  3011		 * We need to poke hw for gen >= 12, because we notify PCode if
  3012		 * pipe power well count changes.
  3013		 */
  3014		return intel_cdclk_changed(&old_cdclk_state->actual,
  3015					   &new_cdclk_state->actual) ||
  3016		       ((DISPLAY_VER(i915) >= 12 &&
  3017			 hweight8(old_cdclk_state->active_pipes) !=
  3018			 hweight8(new_cdclk_state->active_pipes)));
  3019	}
  3020	

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

  parent reply	other threads:[~2023-02-27 12:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27  9:52 [Intel-gfx] [PATCH] drm/i915/display: Communicate display power demands to pcode more accurately Stanislav Lisovskiy
2023-02-27 10:14 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for " Patchwork
2023-02-27 12:20 ` kernel test robot [this message]
2023-02-27 12:30 ` [Intel-gfx] [PATCH] " kernel test robot
2023-02-27 12:51 ` kernel test robot
  -- strict thread matches above, loose matches on Subject: below --
2023-02-27 13:26 Stanislav Lisovskiy
2023-03-06 18:14 ` Jani Nikula
2023-03-07  9:41   ` Lisovskiy, Stanislav
2023-03-07 10:23     ` Jani Nikula
2023-03-07 11:15       ` Lisovskiy, Stanislav
2023-03-07 11:52         ` Jani Nikula
2023-03-17 10:24 Stanislav Lisovskiy

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=202302272011.1iLXtakR-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rodrigo.vivi@intel.com \
    --cc=stanislav.lisovskiy@intel.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