From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [Intel-gfx] [RFC-v2 5/9] drm/i915/dsi: Add check for periodic command mode
Date: Wed, 13 Nov 2019 04:51:08 +0800 [thread overview]
Message-ID: <201911130444.9WvN95ka%lkp@intel.com> (raw)
In-Reply-To: <20191111111029.9126-6-vandita.kulkarni@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2773 bytes --]
Hi Vandita,
[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on drm-intel/for-linux-next]
[cannot apply to v5.4-rc7 next-20191112]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Vandita-Kulkarni/Add-support-for-mipi-dsi-cmd-mode/20191113-022822
base: git://anongit.freedesktop.org/drm-intel for-linux-next
config: i386-defconfig (attached as .config)
compiler: gcc-7 (Debian 7.4.0-14) 7.4.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/gpu/drm/i915/display/icl_dsi.c: In function 'gen11_dsi_get_config':
>> drivers/gpu/drm/i915/display/icl_dsi.c:1325:14: error: 'struct intel_crtc_state' has no member named 'hw'
pipe_config->hw.adjusted_mode.private_flags |=
^~
drivers/gpu/drm/i915/display/icl_dsi.c: In function 'gen11_dsi_compute_config':
drivers/gpu/drm/i915/display/icl_dsi.c:1358:13: error: 'struct intel_crtc_state' has no member named 'hw'
pipe_config->hw.adjusted_mode.private_flags &=
^~
vim +1325 drivers/gpu/drm/i915/display/icl_dsi.c
1304
1305 static void gen11_dsi_get_config(struct intel_encoder *encoder,
1306 struct intel_crtc_state *pipe_config)
1307 {
1308 struct drm_i915_private *dev_priv = to_i915(encoder->base.dev);
1309 struct intel_crtc *crtc = to_intel_crtc(pipe_config->base.crtc);
1310 struct intel_dsi *intel_dsi = enc_to_intel_dsi(&encoder->base);
1311
1312 /* FIXME: adapt icl_ddi_clock_get() for DSI and use that? */
1313 pipe_config->port_clock =
1314 cnl_calc_wrpll_link(dev_priv, &pipe_config->dpll_hw_state);
1315
1316 pipe_config->base.adjusted_mode.crtc_clock = intel_dsi->pclk;
1317 if (intel_dsi->dual_link)
1318 pipe_config->base.adjusted_mode.crtc_clock *= 2;
1319
1320 gen11_dsi_get_timings(encoder, pipe_config);
1321 pipe_config->output_types |= BIT(INTEL_OUTPUT_DSI);
1322 pipe_config->pipe_bpp = bdw_get_pipemisc_bpp(crtc);
1323
1324 if (gen11_dsi_is_periodic_cmd_mode(dev_priv, intel_dsi))
> 1325 pipe_config->hw.adjusted_mode.private_flags |=
1326 I915_MODE_FLAG_DSI_PERIODIC_CMD_MODE;
1327 }
1328
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org Intel Corporation
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 28187 bytes --]
next prev parent reply other threads:[~2019-11-12 20:51 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 11:10 [RFC-v2 0/9] Add support for mipi dsi cmd mode Vandita Kulkarni
2019-11-11 11:10 ` [Intel-gfx] " Vandita Kulkarni
2019-11-11 11:10 ` [RFC-v2 1/9] drm/i915/dsi: Define command mode registers Vandita Kulkarni
2019-11-11 11:10 ` [Intel-gfx] " Vandita Kulkarni
2019-11-12 16:25 ` Jani Nikula
2019-11-12 16:25 ` [Intel-gfx] " Jani Nikula
2019-11-11 11:10 ` [RFC-v2 2/9] drm/i915/dsi: Configure transcoder operation for command mode Vandita Kulkarni
2019-11-11 11:10 ` [Intel-gfx] " Vandita Kulkarni
2019-11-12 16:23 ` Jani Nikula
2019-11-12 16:23 ` [Intel-gfx] " Jani Nikula
2019-11-11 11:10 ` [RFC-v2 3/9] drm/i915/dsi: Add vblank calculation " Vandita Kulkarni
2019-11-11 11:10 ` [Intel-gfx] " Vandita Kulkarni
2019-11-11 11:10 ` [RFC-v2 4/9] drm/i915/dsi: Add cmd mode flags in display mode private flags Vandita Kulkarni
2019-11-11 11:10 ` [Intel-gfx] " Vandita Kulkarni
2019-11-12 16:27 ` Jani Nikula
2019-11-12 16:27 ` [Intel-gfx] " Jani Nikula
2019-11-11 11:10 ` [RFC-v2 5/9] drm/i915/dsi: Add check for periodic command mode Vandita Kulkarni
2019-11-11 11:10 ` [Intel-gfx] " Vandita Kulkarni
2019-11-12 20:51 ` kbuild test robot [this message]
2019-11-11 11:10 ` [RFC-v2 6/9] drm/i915/dsi: Use private flags to indicate TE in cmd mode Vandita Kulkarni
2019-11-11 11:10 ` [Intel-gfx] " Vandita Kulkarni
2019-11-11 11:10 ` [RFC-v2 7/9] drm/i915/dsi: Configure TE interrupt for " Vandita Kulkarni
2019-11-11 11:10 ` [Intel-gfx] " Vandita Kulkarni
2019-11-12 14:59 ` Jani Nikula
2019-11-12 14:59 ` [Intel-gfx] " Jani Nikula
2019-11-11 11:10 ` [RFC-v2 8/9] drm/i915/dsi: Add TE handler for dsi " Vandita Kulkarni
2019-11-11 11:10 ` [Intel-gfx] " Vandita Kulkarni
2019-11-12 15:10 ` Jani Nikula
2019-11-12 15:10 ` [Intel-gfx] " Jani Nikula
2019-11-11 11:10 ` [RFC-v2 9/9] drm/i915/dsi: Initiate fame request in " Vandita Kulkarni
2019-11-11 11:10 ` [Intel-gfx] " Vandita Kulkarni
2019-11-12 21:43 ` kbuild test robot
2019-11-11 17:20 ` ✗ Fi.CI.CHECKPATCH: warning for Add support for mipi dsi " Patchwork
2019-11-11 17:20 ` [Intel-gfx] " Patchwork
2019-11-11 17:23 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-11-11 17:23 ` [Intel-gfx] " Patchwork
2019-11-11 17:53 ` ✓ Fi.CI.BAT: success " Patchwork
2019-11-11 17:53 ` [Intel-gfx] " Patchwork
2019-11-12 5:52 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-11-12 5:52 ` [Intel-gfx] " Patchwork
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=201911130444.9WvN95ka%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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.