All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Lee Shawn C <shawn.c.lee@intel.com>, intel-gfx@lists.freedesktop.org
Cc: kbuild-all@lists.01.org, jani.nikula@intel.com,
	ville.syrjala@linux.intel.com, vandita.kulkarni@intel.com,
	cooper.chiou@intel.com, william.tseng@intel.com,
	Lee Shawn C <shawn.c.lee@intel.com>,
	Jani Nikula <jani.nikula@linux.intel.com>
Subject: Re: [Intel-gfx] [v4 7/7] drm/i915/dsi: Send proper brightness value via MIPI DCS command
Date: Fri, 13 Aug 2021 07:22:21 +0800	[thread overview]
Message-ID: <202108130733.1ZyRtPlW-lkp@intel.com> (raw)
In-Reply-To: <20210812154237.13911-8-shawn.c.lee@intel.com>

[-- Attachment #1: Type: text/plain, Size: 2564 bytes --]

Hi Lee,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on drm-tip/drm-tip v5.14-rc5 next-20210812]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Lee-Shawn-C/MIPI-DSI-driver-enhancements/20210812-234252
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
config: i386-randconfig-s002-20210812 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.3-348-gf0e6938b-dirty
        # https://github.com/0day-ci/linux/commit/ba1a887b66f9314179885cc890152e2a257eac89
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Lee-Shawn-C/MIPI-DSI-driver-enhancements/20210812-234252
        git checkout ba1a887b66f9314179885cc890152e2a257eac89
        # save the attached .config to linux build tree
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=i386 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/i915/display/intel_dsi_dcs_backlight.c:69:20: sparse: sparse: incorrect type in initializer (different base types) @@     expected unsigned short [usertype] data @@     got restricted __be16 [usertype] @@
   drivers/gpu/drm/i915/display/intel_dsi_dcs_backlight.c:69:20: sparse:     expected unsigned short [usertype] data
   drivers/gpu/drm/i915/display/intel_dsi_dcs_backlight.c:69:20: sparse:     got restricted __be16 [usertype]

vim +69 drivers/gpu/drm/i915/display/intel_dsi_dcs_backlight.c

    64	
    65	static void dcs_set_backlight(const struct drm_connector_state *conn_state, u32 level)
    66	{
    67		struct intel_dsi *intel_dsi = enc_to_intel_dsi(to_intel_encoder(conn_state->best_encoder));
    68		struct mipi_dsi_device *dsi_device;
  > 69		u16 data = cpu_to_be16(level);
    70		enum port port;
    71	
    72		for_each_dsi_port(port, intel_dsi->dcs_backlight_ports) {
    73			dsi_device = intel_dsi->dsi_hosts[port]->device;
    74			mipi_dsi_dcs_write(dsi_device, MIPI_DCS_SET_DISPLAY_BRIGHTNESS,
    75					   &data, sizeof(data));
    76		}
    77	}
    78	

---
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: 35596 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [Intel-gfx] [v4 7/7] drm/i915/dsi: Send proper brightness value via MIPI DCS command
Date: Fri, 13 Aug 2021 07:22:21 +0800	[thread overview]
Message-ID: <202108130733.1ZyRtPlW-lkp@intel.com> (raw)
In-Reply-To: <20210812154237.13911-8-shawn.c.lee@intel.com>

[-- Attachment #1: Type: text/plain, Size: 2620 bytes --]

Hi Lee,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on drm-tip/drm-tip v5.14-rc5 next-20210812]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Lee-Shawn-C/MIPI-DSI-driver-enhancements/20210812-234252
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
config: i386-randconfig-s002-20210812 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.3-348-gf0e6938b-dirty
        # https://github.com/0day-ci/linux/commit/ba1a887b66f9314179885cc890152e2a257eac89
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Lee-Shawn-C/MIPI-DSI-driver-enhancements/20210812-234252
        git checkout ba1a887b66f9314179885cc890152e2a257eac89
        # save the attached .config to linux build tree
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=i386 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>


sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/i915/display/intel_dsi_dcs_backlight.c:69:20: sparse: sparse: incorrect type in initializer (different base types) @@     expected unsigned short [usertype] data @@     got restricted __be16 [usertype] @@
   drivers/gpu/drm/i915/display/intel_dsi_dcs_backlight.c:69:20: sparse:     expected unsigned short [usertype] data
   drivers/gpu/drm/i915/display/intel_dsi_dcs_backlight.c:69:20: sparse:     got restricted __be16 [usertype]

vim +69 drivers/gpu/drm/i915/display/intel_dsi_dcs_backlight.c

    64	
    65	static void dcs_set_backlight(const struct drm_connector_state *conn_state, u32 level)
    66	{
    67		struct intel_dsi *intel_dsi = enc_to_intel_dsi(to_intel_encoder(conn_state->best_encoder));
    68		struct mipi_dsi_device *dsi_device;
  > 69		u16 data = cpu_to_be16(level);
    70		enum port port;
    71	
    72		for_each_dsi_port(port, intel_dsi->dcs_backlight_ports) {
    73			dsi_device = intel_dsi->dsi_hosts[port]->device;
    74			mipi_dsi_dcs_write(dsi_device, MIPI_DCS_SET_DISPLAY_BRIGHTNESS,
    75					   &data, sizeof(data));
    76		}
    77	}
    78	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 35596 bytes --]

  reply	other threads:[~2021-08-12 23:23 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-12 15:42 [Intel-gfx] [v4 0/7] MIPI DSI driver enhancements Lee Shawn C
2021-08-12 15:42 ` [Intel-gfx] [v4 1/7] drm/i915/dsi: send correct gpio_number on gen11 platform Lee Shawn C
2021-08-12 15:42 ` [Intel-gfx] [v4 2/7] drm/i915/jsl: program DSI panel GPIOs Lee Shawn C
2021-08-23 12:06   ` Jani Nikula
2021-08-12 15:42 ` [Intel-gfx] [v4 3/7] drm/i915/dsi: wait for header and payload credit available Lee Shawn C
2021-08-26  5:54   ` Kulkarni, Vandita
2021-08-12 15:42 ` [Intel-gfx] [v4 4/7] drm/i915/dsi: refine send MIPI DCS command sequence Lee Shawn C
2021-08-23  9:45   ` Kulkarni, Vandita
2021-08-12 15:42 ` [Intel-gfx] [v4 5/7] drm/i915: Get proper min cdclk if vDSC enabled Lee Shawn C
2021-08-23 12:19   ` Kulkarni, Vandita
2021-08-12 15:42 ` [Intel-gfx] [v4 6/7] drm/i915/dsi: Retrieve max brightness level from VBT Lee Shawn C
2021-08-23  8:46   ` Kulkarni, Vandita
2021-08-23  9:03     ` Lee, Shawn C
2021-08-23 12:10       ` Kulkarni, Vandita
2021-08-24 14:00   ` [Intel-gfx] [PATCH] " Lee Shawn C
2021-08-24 14:33     ` Jani Nikula
2021-08-24 15:53       ` Lee, Shawn C
2021-08-12 15:42 ` [Intel-gfx] [v4 7/7] drm/i915/dsi: Send proper brightness value via MIPI DCS command Lee Shawn C
2021-08-12 23:22   ` kernel test robot [this message]
2021-08-12 23:22     ` kernel test robot
2021-08-13  2:46   ` [Intel-gfx] [v4] " Lee Shawn C
2021-08-18 11:10     ` Jani Nikula
2021-08-18 14:58       ` Lee, Shawn C
2021-08-19 11:16     ` [Intel-gfx] [v4] drm/i915/dsi: Read/write " Lee Shawn C
2021-08-12 20:56 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for MIPI DSI driver enhancements (rev5) Patchwork
2021-08-12 20:57 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-08-12 21:26 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-08-13  2:29 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-08-13  2:56 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for MIPI DSI driver enhancements (rev6) Patchwork
2021-08-13  2:58 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-08-13  3:24 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-08-13  7:56 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-08-19 11:45 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for MIPI DSI driver enhancements (rev7) Patchwork
2021-08-19 11:46 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-08-19 12:09 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-08-19 13:41 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-08-24 19:11 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for MIPI DSI driver enhancements (rev8) Patchwork
2021-08-24 19:12 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-08-24 19:41 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-08-25  1:22 ` [Intel-gfx] ✓ 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=202108130733.1ZyRtPlW-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cooper.chiou@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=jani.nikula@linux.intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=shawn.c.lee@intel.com \
    --cc=vandita.kulkarni@intel.com \
    --cc=ville.syrjala@linux.intel.com \
    --cc=william.tseng@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 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.