From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: [xlnx:master 10/28] drivers/media/i2c/adv7511-v4l2.c:431 adv7511_set_rgb_quantization_mode() warn: ignoring unreachable code.
Date: Sat, 07 Aug 2021 01:23:49 +0800 [thread overview]
Message-ID: <202108070136.m4TM7BbK-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4654 bytes --]
CC: kbuild-all(a)lists.01.org
CC: linux-arm-kernel(a)lists.infradead.org
TO: Quanyang Wang <quanyang.wang@windriver.com>
CC: Michal Simek <monstr@monstr.eu>
Hi Quanyang,
First bad commit (maybe != root cause):
tree: https://github.com/Xilinx/linux-xlnx master
head: 42359bc57bbfee6dfb31a9bad31374c3927f280d
commit: bd76b5963aee700d5e6ff0cd29834bfdaf05532e [10/28] media: adv7511-v4l2: fix compile error
:::::: branch date: 2 weeks ago
:::::: commit date: 3 weeks ago
config: nios2-randconfig-m031-20210804 (attached as .config)
compiler: nios2-linux-gcc (GCC) 10.3.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
smatch warnings:
drivers/media/i2c/adv7511-v4l2.c:431 adv7511_set_rgb_quantization_mode() warn: ignoring unreachable code.
vim +431 drivers/media/i2c/adv7511-v4l2.c
c2644339194bd7 drivers/media/i2c/adv7511-v4l2.c Radhey Shyam Pandey 2014-01-15 429
0a25a012519463 drivers/media/i2c/adv7511.c Hans Verkuil 2016-06-28 430 /* Only makes sense for RGB formats */
0a25a012519463 drivers/media/i2c/adv7511.c Hans Verkuil 2016-06-28 @431 if (state->fmt_code != MEDIA_BUS_FMT_RGB888_1X24) {
0a25a012519463 drivers/media/i2c/adv7511.c Hans Verkuil 2016-06-28 432 /* so just keep quantization */
0a25a012519463 drivers/media/i2c/adv7511.c Hans Verkuil 2016-06-28 433 adv7511_csc_rgb_full2limit(sd, false);
0a25a012519463 drivers/media/i2c/adv7511.c Hans Verkuil 2016-06-28 434 return;
0a25a012519463 drivers/media/i2c/adv7511.c Hans Verkuil 2016-06-28 435 }
0a25a012519463 drivers/media/i2c/adv7511.c Hans Verkuil 2016-06-28 436
0a25a012519463 drivers/media/i2c/adv7511.c Hans Verkuil 2016-06-28 437 switch (ctrl->val) {
0a25a012519463 drivers/media/i2c/adv7511.c Hans Verkuil 2016-06-28 438 case V4L2_DV_RGB_RANGE_AUTO:
0a25a012519463 drivers/media/i2c/adv7511.c Hans Verkuil 2016-06-28 439 /* automatic */
680fee04a227d6 drivers/media/i2c/adv7511.c Hans Verkuil 2015-03-20 440 if (state->dv_timings.bt.flags & V4L2_DV_FL_IS_CE_VIDEO) {
680fee04a227d6 drivers/media/i2c/adv7511.c Hans Verkuil 2015-03-20 441 /* CE format, RGB limited range (16-235) */
5a544cce2177fe drivers/media/i2c/adv7511.c Hans Verkuil 2013-08-23 442 adv7511_csc_rgb_full2limit(sd, true);
5a544cce2177fe drivers/media/i2c/adv7511.c Hans Verkuil 2013-08-23 443 } else {
680fee04a227d6 drivers/media/i2c/adv7511.c Hans Verkuil 2015-03-20 444 /* not CE format, RGB full range (0-255) */
5a544cce2177fe drivers/media/i2c/adv7511.c Hans Verkuil 2013-08-23 445 adv7511_csc_rgb_full2limit(sd, false);
5a544cce2177fe drivers/media/i2c/adv7511.c Hans Verkuil 2013-08-23 446 }
5a544cce2177fe drivers/media/i2c/adv7511.c Hans Verkuil 2013-08-23 447 break;
5a544cce2177fe drivers/media/i2c/adv7511.c Hans Verkuil 2013-08-23 448 case V4L2_DV_RGB_RANGE_LIMITED:
5a544cce2177fe drivers/media/i2c/adv7511.c Hans Verkuil 2013-08-23 449 /* RGB limited range (16-235) */
5a544cce2177fe drivers/media/i2c/adv7511.c Hans Verkuil 2013-08-23 450 adv7511_csc_rgb_full2limit(sd, true);
5a544cce2177fe drivers/media/i2c/adv7511.c Hans Verkuil 2013-08-23 451 break;
5a544cce2177fe drivers/media/i2c/adv7511.c Hans Verkuil 2013-08-23 452 case V4L2_DV_RGB_RANGE_FULL:
5a544cce2177fe drivers/media/i2c/adv7511.c Hans Verkuil 2013-08-23 453 /* RGB full range (0-255) */
5a544cce2177fe drivers/media/i2c/adv7511.c Hans Verkuil 2013-08-23 454 adv7511_csc_rgb_full2limit(sd, false);
5a544cce2177fe drivers/media/i2c/adv7511.c Hans Verkuil 2013-08-23 455 break;
5a544cce2177fe drivers/media/i2c/adv7511.c Hans Verkuil 2013-08-23 456 }
5a544cce2177fe drivers/media/i2c/adv7511.c Hans Verkuil 2013-08-23 457 }
5a544cce2177fe drivers/media/i2c/adv7511.c Hans Verkuil 2013-08-23 458
:::::: The code at line 431 was first introduced by commit
:::::: 0a25a0125194639507cf24319d02f5de63d182b5 [media] adv7511: fix quantization range handling
:::::: TO: Hans Verkuil <hans.verkuil@cisco.com>
:::::: CC: Mauro Carvalho Chehab <mchehab@s-opensource.com>
---
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: 31293 bytes --]
reply other threads:[~2021-08-06 17:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202108070136.m4TM7BbK-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild@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.