From: kernel test robot <lkp@intel.com>
To: Liu Ying <victor.liu@nxp.com>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Dmitry Baryshkov <lumag@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, Liu Ying <victor.liu@nxp.com>
Subject: Re: [PATCH] drm/bridge: ite-it6263: Support HDMI vendor specific infoframe
Date: Sat, 6 Sep 2025 05:50:28 +0800 [thread overview]
Message-ID: <202509060506.8qlqQKQi-lkp@intel.com> (raw)
In-Reply-To: <20250904-it6263-vendor-specific-infoframe-v1-1-6efe6545b634@nxp.com>
Hi Liu,
kernel test robot noticed the following build errors:
[auto build test ERROR on 4ac65880ebca1b68495bd8704263b26c050ac010]
url: https://github.com/intel-lab-lkp/linux/commits/Liu-Ying/drm-bridge-ite-it6263-Support-HDMI-vendor-specific-infoframe/20250904-171143
base: 4ac65880ebca1b68495bd8704263b26c050ac010
patch link: https://lore.kernel.org/r/20250904-it6263-vendor-specific-infoframe-v1-1-6efe6545b634%40nxp.com
patch subject: [PATCH] drm/bridge: ite-it6263: Support HDMI vendor specific infoframe
config: xtensa-randconfig-002-20250906 (https://download.01.org/0day-ci/archive/20250906/202509060506.8qlqQKQi-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 10.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250906/202509060506.8qlqQKQi-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/202509060506.8qlqQKQi-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/bridge/ite-it6263.c: In function 'it6263_hdmi_write_infoframe':
>> drivers/gpu/drm/bridge/ite-it6263.c:810:3: error: a label can only be part of a statement and a declaration is not a statement
810 | const char zero_bulk[HDMI_PKT_HB_PB_CHUNK_SIZE] = { };
| ^~~~~
vim +810 drivers/gpu/drm/bridge/ite-it6263.c
782
783 static int it6263_hdmi_write_infoframe(struct drm_bridge *bridge,
784 enum hdmi_infoframe_type type,
785 const u8 *buffer, size_t len)
786 {
787 struct it6263 *it = bridge_to_it6263(bridge);
788 struct regmap *regmap = it->hdmi_regmap;
789
790 switch (type) {
791 case HDMI_INFOFRAME_TYPE_AVI:
792 /* write the first AVI infoframe data byte chunk(DB1-DB5) */
793 regmap_bulk_write(regmap, HDMI_REG_AVI_DB1,
794 &buffer[HDMI_INFOFRAME_HEADER_SIZE],
795 HDMI_AVI_DB_CHUNK1_SIZE);
796
797 /* write the second AVI infoframe data byte chunk(DB6-DB13) */
798 regmap_bulk_write(regmap, HDMI_REG_AVI_DB6,
799 &buffer[HDMI_INFOFRAME_HEADER_SIZE +
800 HDMI_AVI_DB_CHUNK1_SIZE],
801 HDMI_AVI_DB_CHUNK2_SIZE);
802
803 /* write checksum */
804 regmap_write(regmap, HDMI_REG_AVI_CSUM, buffer[3]);
805
806 regmap_write(regmap, HDMI_REG_AVI_INFOFRM_CTRL,
807 ENABLE_PKT | REPEAT_PKT);
808 break;
809 case HDMI_INFOFRAME_TYPE_VENDOR:
> 810 const char zero_bulk[HDMI_PKT_HB_PB_CHUNK_SIZE] = { };
811
812 /* clear NULL packet registers due to undefined default value */
813 regmap_bulk_write(regmap, HDMI_REG_PKT_HB(0),
814 zero_bulk, sizeof(zero_bulk));
815
816 /* write header and payload */
817 regmap_bulk_write(regmap, HDMI_REG_PKT_HB(0), buffer, len);
818
819 regmap_write(regmap, HDMI_REG_PKT_NULL_CTRL,
820 ENABLE_PKT | REPEAT_PKT);
821 break;
822 default:
823 dev_dbg(it->dev, "unsupported HDMI infoframe 0x%x\n", type);
824 }
825
826 return 0;
827 }
828
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-09-05 21:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 9:10 Liu Ying
2025-09-04 22:40 ` Dmitry Baryshkov
2025-09-05 5:46 ` Liu Ying
2025-09-05 14:31 ` Dmitry Baryshkov
2025-09-08 5:38 ` Liu Ying
2025-09-05 21:08 ` kernel test robot
2025-09-05 21:50 ` kernel test robot [this message]
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=202509060506.8qlqQKQi-lkp@intel.com \
--to=lkp@intel.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rfoss@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=victor.liu@nxp.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
all inboxes | Powered by JetHome®