From: kbuild test robot <lkp@intel.com>
To: Uma Shankar <uma.shankar@intel.com>
Cc: intel-gfx@lists.freedesktop.org, ville.syrjala@intel.com,
kbuild-all@01.org, dri-devel@lists.freedesktop.org,
maarten.lankhorst@intel.com
Subject: Re: [v4 07/12] drm: Enable HDR infoframe support
Date: Wed, 9 Jan 2019 10:19:45 +0800 [thread overview]
Message-ID: <201901091002.ywUmxns7%fengguang.wu@intel.com> (raw)
In-Reply-To: <1546938687-27306-8-git-send-email-uma.shankar@intel.com>
[-- Attachment #1: Type: text/plain, Size: 4811 bytes --]
Hi Uma,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.0-rc1 next-20190108]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Uma-Shankar/Add-HDR-Metadata-Parsing-and-handling-in-DRM-layer/20190109-051130
config: arm64-allyesconfig (attached as .config)
compiler: aarch64-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=7.2.0 make.cross ARCH=arm64
All warnings (new ones prefixed by >>):
drivers/gpu//drm/mediatek/mtk_hdmi.c: In function 'mtk_hdmi_hw_send_info_frame':
>> drivers/gpu//drm/mediatek/mtk_hdmi.c:327:2: warning: enumeration value 'HDMI_INFOFRAME_TYPE_DRM' not handled in switch [-Wswitch]
switch (frame_type) {
^~~~~~
vim +/HDMI_INFOFRAME_TYPE_DRM +327 drivers/gpu//drm/mediatek/mtk_hdmi.c
8f83f268 Jie Qiu 2016-01-04 300
8f83f268 Jie Qiu 2016-01-04 301 static void mtk_hdmi_hw_send_info_frame(struct mtk_hdmi *hdmi, u8 *buffer,
8f83f268 Jie Qiu 2016-01-04 302 u8 len)
8f83f268 Jie Qiu 2016-01-04 303 {
8f83f268 Jie Qiu 2016-01-04 304 u32 ctrl_reg = GRL_CTRL;
8f83f268 Jie Qiu 2016-01-04 305 int i;
8f83f268 Jie Qiu 2016-01-04 306 u8 *frame_data;
8f83f268 Jie Qiu 2016-01-04 307 enum hdmi_infoframe_type frame_type;
8f83f268 Jie Qiu 2016-01-04 308 u8 frame_ver;
8f83f268 Jie Qiu 2016-01-04 309 u8 frame_len;
8f83f268 Jie Qiu 2016-01-04 310 u8 checksum;
8f83f268 Jie Qiu 2016-01-04 311 int ctrl_frame_en = 0;
8f83f268 Jie Qiu 2016-01-04 312
8f83f268 Jie Qiu 2016-01-04 313 frame_type = *buffer;
8f83f268 Jie Qiu 2016-01-04 314 buffer += 1;
8f83f268 Jie Qiu 2016-01-04 315 frame_ver = *buffer;
8f83f268 Jie Qiu 2016-01-04 316 buffer += 1;
8f83f268 Jie Qiu 2016-01-04 317 frame_len = *buffer;
8f83f268 Jie Qiu 2016-01-04 318 buffer += 1;
8f83f268 Jie Qiu 2016-01-04 319 checksum = *buffer;
8f83f268 Jie Qiu 2016-01-04 320 buffer += 1;
8f83f268 Jie Qiu 2016-01-04 321 frame_data = buffer;
8f83f268 Jie Qiu 2016-01-04 322
8f83f268 Jie Qiu 2016-01-04 323 dev_dbg(hdmi->dev,
8f83f268 Jie Qiu 2016-01-04 324 "frame_type:0x%x,frame_ver:0x%x,frame_len:0x%x,checksum:0x%x\n",
8f83f268 Jie Qiu 2016-01-04 325 frame_type, frame_ver, frame_len, checksum);
8f83f268 Jie Qiu 2016-01-04 326
8f83f268 Jie Qiu 2016-01-04 @327 switch (frame_type) {
8f83f268 Jie Qiu 2016-01-04 328 case HDMI_INFOFRAME_TYPE_AVI:
8f83f268 Jie Qiu 2016-01-04 329 ctrl_frame_en = CTRL_AVI_EN;
8f83f268 Jie Qiu 2016-01-04 330 ctrl_reg = GRL_CTRL;
8f83f268 Jie Qiu 2016-01-04 331 break;
8f83f268 Jie Qiu 2016-01-04 332 case HDMI_INFOFRAME_TYPE_SPD:
8f83f268 Jie Qiu 2016-01-04 333 ctrl_frame_en = CTRL_SPD_EN;
8f83f268 Jie Qiu 2016-01-04 334 ctrl_reg = GRL_CTRL;
8f83f268 Jie Qiu 2016-01-04 335 break;
8f83f268 Jie Qiu 2016-01-04 336 case HDMI_INFOFRAME_TYPE_AUDIO:
8f83f268 Jie Qiu 2016-01-04 337 ctrl_frame_en = CTRL_AUDIO_EN;
8f83f268 Jie Qiu 2016-01-04 338 ctrl_reg = GRL_CTRL;
8f83f268 Jie Qiu 2016-01-04 339 break;
8f83f268 Jie Qiu 2016-01-04 340 case HDMI_INFOFRAME_TYPE_VENDOR:
8f83f268 Jie Qiu 2016-01-04 341 ctrl_frame_en = VS_EN;
8f83f268 Jie Qiu 2016-01-04 342 ctrl_reg = GRL_ACP_ISRC_CTRL;
8f83f268 Jie Qiu 2016-01-04 343 break;
8f83f268 Jie Qiu 2016-01-04 344 }
8f83f268 Jie Qiu 2016-01-04 345 mtk_hdmi_clear_bits(hdmi, ctrl_reg, ctrl_frame_en);
8f83f268 Jie Qiu 2016-01-04 346 mtk_hdmi_write(hdmi, GRL_INFOFRM_TYPE, frame_type);
8f83f268 Jie Qiu 2016-01-04 347 mtk_hdmi_write(hdmi, GRL_INFOFRM_VER, frame_ver);
8f83f268 Jie Qiu 2016-01-04 348 mtk_hdmi_write(hdmi, GRL_INFOFRM_LNG, frame_len);
8f83f268 Jie Qiu 2016-01-04 349
8f83f268 Jie Qiu 2016-01-04 350 mtk_hdmi_write(hdmi, GRL_IFM_PORT, checksum);
8f83f268 Jie Qiu 2016-01-04 351 for (i = 0; i < frame_len; i++)
8f83f268 Jie Qiu 2016-01-04 352 mtk_hdmi_write(hdmi, GRL_IFM_PORT, frame_data[i]);
8f83f268 Jie Qiu 2016-01-04 353
8f83f268 Jie Qiu 2016-01-04 354 mtk_hdmi_set_bits(hdmi, ctrl_reg, ctrl_frame_en);
8f83f268 Jie Qiu 2016-01-04 355 }
8f83f268 Jie Qiu 2016-01-04 356
:::::: The code at line 327 was first introduced by commit
:::::: 8f83f26891e12570780dcfc8ae376b655915ff6d drm/mediatek: Add HDMI support
:::::: TO: Jie Qiu <jie.qiu@mediatek.com>
:::::: CC: Philipp Zabel <p.zabel@pengutronix.de>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 63180 bytes --]
[-- Attachment #3: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-01-09 2:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 9:11 [v4 00/12] Add HDR Metadata Parsing and handling in DRM layer Uma Shankar
2019-01-08 9:11 ` [v4 01/12] drm: Add HDR source metadata property Uma Shankar
2019-01-09 0:51 ` [Intel-gfx] " kbuild test robot
2019-01-10 11:03 ` Liviu Dudau
2019-01-08 9:11 ` [v4 02/12] drm: Parse HDR metadata info from EDID Uma Shankar
2019-01-08 9:11 ` [v4 03/12] drm: Parse Colorimetry data block " Uma Shankar
2019-01-09 2:57 ` [Intel-gfx] " kbuild test robot
2019-01-08 9:11 ` [v4 04/12] drm/i915: Attach HDR metadata property to connector Uma Shankar
2019-01-08 9:11 ` [v4 05/12] drm: Add HDR capability field to plane structure Uma Shankar
2019-01-09 5:09 ` kbuild test robot
2019-01-10 10:47 ` Liviu Dudau
2019-01-10 11:45 ` Shankar, Uma
2019-01-08 9:11 ` [v4 06/12] drm: Implement HDR output metadata set and get property handling Uma Shankar
2019-01-08 9:11 ` [v4 07/12] drm: Enable HDR infoframe support Uma Shankar
2019-01-09 2:19 ` kbuild test robot [this message]
2019-01-09 7:19 ` kbuild test robot
2019-01-08 9:11 ` [v4 08/12] drm/i915: Write HDR infoframe and send to panel Uma Shankar
2019-01-08 9:11 ` [v4 09/12] drm/i915: [DO NOT MERGE] hack for glk board outputs Uma Shankar
2019-01-08 9:11 ` [v4 10/12] drm/i915: Add HLG EOTF Uma Shankar
2019-01-08 19:45 ` Matt Roper
2019-01-09 12:08 ` Shankar, Uma
2019-01-08 9:11 ` [v4 11/12] drm/i915: Enable infoframes on GLK+ for HDR Uma Shankar
2019-01-08 9:11 ` [v4 12/12] drm/i915:Enabled Modeset when HDR Infoframe changes Uma Shankar
2019-01-08 10:23 ` ✗ Fi.CI.CHECKPATCH: warning for Add HDR Metadata Parsing and handling in DRM layer (rev4) Patchwork
2019-01-08 10:29 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-01-08 10:41 ` ✓ Fi.CI.BAT: success " Patchwork
2019-01-08 14:08 ` ✓ Fi.CI.IGT: " 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=201901091002.ywUmxns7%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kbuild-all@01.org \
--cc=maarten.lankhorst@intel.com \
--cc=uma.shankar@intel.com \
--cc=ville.syrjala@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