From: kernel test robot <lkp@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
0day robot <lkp@intel.com>,
Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
Subject: drivers/gpu/drm/i915/display/intel_fbc.c:101:18: error: 'i915' undeclared; did you mean 'to_i915'?
Date: Tue, 28 Sep 2021 07:15:05 +0800 [thread overview]
Message-ID: <202109280758.stythBK8-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3585 bytes --]
tree: https://github.com/0day-ci/linux/commits/Ville-Syrjala/drm-i915-fbc-Rework-CFB-stride-size-calculations/20210922-130015
head: 2ae62c15535ddb9b3a5215bc0266dd46e328f38c
commit: cb0b857a450fc222fe722d794cff9fbafc6fb334 drm/i915/fbc: Implement Wa_16011863758 for icl+
date: 6 days ago
config: i386-allyesconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/cb0b857a450fc222fe722d794cff9fbafc6fb334
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Ville-Syrjala/drm-i915-fbc-Rework-CFB-stride-size-calculations/20210922-130015
git checkout cb0b857a450fc222fe722d794cff9fbafc6fb334
# save the attached .config to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from drivers/gpu/drm/i915/display/intel_fbc.c:43:
drivers/gpu/drm/i915/display/intel_fbc.c: In function 'skl_fbc_min_cfb_stride':
>> drivers/gpu/drm/i915/display/intel_fbc.c:101:18: error: 'i915' undeclared (first use in this function); did you mean 'to_i915'?
101 | if (DISPLAY_VER(i915) >= 11)
| ^~~~
drivers/gpu/drm/i915/i915_drv.h:1276:33: note: in definition of macro 'INTEL_INFO'
1276 | #define INTEL_INFO(dev_priv) (&(dev_priv)->__info)
| ^~~~~~~~
drivers/gpu/drm/i915/display/intel_fbc.c:101:6: note: in expansion of macro 'DISPLAY_VER'
101 | if (DISPLAY_VER(i915) >= 11)
| ^~~~~~~~~~~
drivers/gpu/drm/i915/display/intel_fbc.c:101:18: note: each undeclared identifier is reported only once for each function it appears in
101 | if (DISPLAY_VER(i915) >= 11)
| ^~~~
drivers/gpu/drm/i915/i915_drv.h:1276:33: note: in definition of macro 'INTEL_INFO'
1276 | #define INTEL_INFO(dev_priv) (&(dev_priv)->__info)
| ^~~~~~~~
drivers/gpu/drm/i915/display/intel_fbc.c:101:6: note: in expansion of macro 'DISPLAY_VER'
101 | if (DISPLAY_VER(i915) >= 11)
| ^~~~~~~~~~~
vim +101 drivers/gpu/drm/i915/display/intel_fbc.c
85
86 /* minimum acceptable cfb stride in bytes, assuming 1:1 compression limit */
87 static unsigned int skl_fbc_min_cfb_stride(const struct intel_fbc_state_cache *cache)
88 {
89 unsigned int limit = 4; /* 1:4 compression limit is the worst case */
90 unsigned int cpp = 4; /* FBC always 4 bytes per pixel */
91 unsigned int height = 4; /* FBC segment is 4 lines */
92 unsigned int stride;
93
94 /* minimum segment stride we can use */
95 stride = cache->plane.src_w * cpp * height / limit;
96
97 /*
98 * Wa_16011863758: icl+
99 * Avoid some hardware segment address miscalculation.
100 */
> 101 if (DISPLAY_VER(i915) >= 11)
102 stride += 64;
103
104 /*
105 * At least some of the platforms require each 4 line segment to
106 * be 512 byte aligned. Just do it always for simplicity.
107 */
108 stride = ALIGN(stride, 512);
109
110 /* convert back to single line equivalent with 1:1 compression limit */
111 return stride * limit / height;
112 }
113
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 66005 bytes --]
reply other threads:[~2021-09-27 23:15 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=202109280758.stythBK8-lkp@intel.com \
--to=lkp@intel.com \
--cc=juhapekka.heikkila@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ville.syrjala@linux.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