mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Yongbang Shi <shiyongbang@huawei.com>,
	xinliang.liu@linaro.org, tiantao6@hisilicon.com,
	maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	tzimmermann@suse.de, airlied@gmail.com, daniel@ffwll.ch,
	kong.kongxinwei@hisilicon.com, dmitry.baryshkov@oss.qualcomm.com
Cc: oe-kbuild-all@lists.linux.dev, liangjian010@huawei.com,
	chenjianmin@huawei.com, fengsheng5@huawei.com,
	shiyongbang@huawei.com, libaihan@huawei.com,
	shenjian15@huawei.com, shaojijie@huawei.com,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 drm-dp 1/4] drm/hisilicon/hibmc: fix dp probabilistical detect errors after HPD irq
Date: Wed, 24 Sep 2025 17:08:23 +0800	[thread overview]
Message-ID: <202509241625.o4mNleVb-lkp@intel.com> (raw)
In-Reply-To: <20250923130411.2522339-2-shiyongbang@huawei.com>

Hi Yongbang,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on linus/master v6.17-rc7 next-20250923]
[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#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Yongbang-Shi/drm-hisilicon-hibmc-fix-dp-probabilistical-detect-errors-after-HPD-irq/20250923-211652
base:   git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link:    https://lore.kernel.org/r/20250923130411.2522339-2-shiyongbang%40huawei.com
patch subject: [PATCH v7 drm-dp 1/4] drm/hisilicon/hibmc: fix dp probabilistical detect errors after HPD irq
config: s390-randconfig-001-20250924 (https://download.01.org/0day-ci/archive/20250924/202509241625.o4mNleVb-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250924/202509241625.o4mNleVb-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202509241625.o4mNleVb-lkp@intel.com/

All warnings (new ones prefixed by >>):

   drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_dp.c: In function 'hibmc_dp_detect':
>> drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_dp.c:61:18: warning: array subscript 128 is above array bounds of 'u8[15]' {aka 'unsigned char[15]'} [-Warray-bounds]
         dp_dev->dpcd[DP_DOWNSTREAM_PORT_0] & DP_DS_PORT_HPD) {
         ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~


vim +61 drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_dp.c

    34	
    35	static int hibmc_dp_detect(struct drm_connector *connector,
    36				   struct drm_modeset_acquire_ctx *ctx, bool force)
    37	{
    38		struct hibmc_dp *dp = to_hibmc_dp(connector);
    39		struct hibmc_dp_dev *dp_dev = dp->dp_dev;
    40		int ret;
    41	
    42		if (dp->irq_status) {
    43			if (dp_dev->hpd_status != HIBMC_HPD_IN)
    44				return connector_status_disconnected;
    45		}
    46	
    47		ret = drm_dp_read_dpcd_caps(dp_dev->aux, dp_dev->dpcd);
    48		if (ret)
    49			return connector_status_disconnected;
    50	
    51		dp_dev->is_branch = drm_dp_is_branch(dp_dev->dpcd);
    52	
    53		ret = drm_dp_read_desc(dp_dev->aux, &dp_dev->desc, dp_dev->is_branch);
    54		if (ret)
    55			return connector_status_disconnected;
    56	
    57		if (!dp_dev->is_branch)
    58			return connector_status_connected;
    59	
    60		if (drm_dp_read_sink_count_cap(connector, dp_dev->dpcd, &dp_dev->desc) &&
  > 61		    dp_dev->dpcd[DP_DOWNSTREAM_PORT_0] & DP_DS_PORT_HPD) {
    62			ret = drm_dp_read_sink_count(dp_dev->aux);
    63			if (ret > 0)
    64				return connector_status_connected;
    65		}
    66	
    67		return connector_status_disconnected;
    68	}
    69	

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

  reply	other threads:[~2025-09-24  9:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-23 13:04 [PATCH v7 drm-dp 0/4] Fix hibmc driver bugs Yongbang Shi
2025-09-23 13:04 ` [PATCH v7 drm-dp 1/4] drm/hisilicon/hibmc: fix dp probabilistical detect errors after HPD irq Yongbang Shi
2025-09-24  9:08   ` kernel test robot [this message]
2025-09-23 13:04 ` [PATCH v7 drm-dp 2/4] drm/hisilicon/hibmc: add dp mode valid check Yongbang Shi
2025-09-23 13:04 ` [PATCH v7 drm-dp 3/4] drm/hisilicon/hibmc: fix no showing problem with loading hibmc manually Yongbang Shi
2025-09-23 13:04 ` [PATCH v7 drm-dp 4/4] drm/hisilicon/hibmc: Adding reset colorbar cfg in dp init Yongbang Shi

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=202509241625.o4mNleVb-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=airlied@gmail.com \
    --cc=chenjianmin@huawei.com \
    --cc=daniel@ffwll.ch \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fengsheng5@huawei.com \
    --cc=kong.kongxinwei@hisilicon.com \
    --cc=liangjian010@huawei.com \
    --cc=libaihan@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=shaojijie@huawei.com \
    --cc=shenjian15@huawei.com \
    --cc=shiyongbang@huawei.com \
    --cc=tiantao6@hisilicon.com \
    --cc=tzimmermann@suse.de \
    --cc=xinliang.liu@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®