From: kernel test robot <lkp@intel.com>
To: Hermes Wu <Hermes.Wu@ite.com.tw>, Pin-yen Lin <treapking@chromium.org>
Cc: oe-kbuild-all@lists.linux.dev,
Kenneth Hung <Kenneth.hung@ite.com.tw>,
Hermes Wu <Hermes.wu@ite.com.tw>,
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>,
"open list:DRM DRIVERS" <dri-devel@lists.freedesktop.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/3] drm/bridge: it6505: HDCP CTS fail on repeater items
Date: Tue, 24 Sep 2024 19:01:12 +0800 [thread overview]
Message-ID: <202409241856.OWgR1x3Y-lkp@intel.com> (raw)
In-Reply-To: <20240923094826.13471-3-Hermes.Wu@ite.com.tw>
Hi Hermes,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm/drm-next]
[also build test WARNING on drm-exynos/exynos-drm-next drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-misc/drm-misc-next drm-tip/drm-tip linus/master v6.11 next-20240923]
[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/Hermes-Wu/drm-bridge-it6505-fix-AUX-read-use-aux-fifo/20240923-175041
base: git://anongit.freedesktop.org/drm/drm drm-next
patch link: https://lore.kernel.org/r/20240923094826.13471-3-Hermes.Wu%40ite.com.tw
patch subject: [PATCH v3 2/3] drm/bridge: it6505: HDCP CTS fail on repeater items
config: nios2-randconfig-r073-20240924 (https://download.01.org/0day-ci/archive/20240924/202409241856.OWgR1x3Y-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 14.1.0
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/202409241856.OWgR1x3Y-lkp@intel.com/
smatch warnings:
drivers/gpu/drm/bridge/ite-it6505.c:2027 it6505_setup_sha1_input() warn: inconsistent indenting
vim +2027 drivers/gpu/drm/bridge/ite-it6505.c
b5c84a9edcd418 Allen Chen 2022-01-14 1996
b5c84a9edcd418 Allen Chen 2022-01-14 1997 static int it6505_setup_sha1_input(struct it6505 *it6505, u8 *sha1_input)
b5c84a9edcd418 Allen Chen 2022-01-14 1998 {
d65feac281ab47 Pin-yen Lin 2023-07-18 1999 struct device *dev = it6505->dev;
b5c84a9edcd418 Allen Chen 2022-01-14 2000 u8 binfo[2];
9665163df60e16 Hermes Wu 2024-09-23 2001 int down_stream_count, err, msg_count = 0;
b5c84a9edcd418 Allen Chen 2022-01-14 2002
b5c84a9edcd418 Allen Chen 2022-01-14 2003 err = it6505_get_dpcd(it6505, DP_AUX_HDCP_BINFO, binfo,
b5c84a9edcd418 Allen Chen 2022-01-14 2004 ARRAY_SIZE(binfo));
b5c84a9edcd418 Allen Chen 2022-01-14 2005
b5c84a9edcd418 Allen Chen 2022-01-14 2006 if (err < 0) {
b5c84a9edcd418 Allen Chen 2022-01-14 2007 dev_err(dev, "Read binfo value Fail");
b5c84a9edcd418 Allen Chen 2022-01-14 2008 return err;
b5c84a9edcd418 Allen Chen 2022-01-14 2009 }
b5c84a9edcd418 Allen Chen 2022-01-14 2010
b5c84a9edcd418 Allen Chen 2022-01-14 2011 down_stream_count = binfo[0] & 0x7F;
b5c84a9edcd418 Allen Chen 2022-01-14 2012 DRM_DEV_DEBUG_DRIVER(dev, "binfo:0x%*ph", (int)ARRAY_SIZE(binfo),
b5c84a9edcd418 Allen Chen 2022-01-14 2013 binfo);
b5c84a9edcd418 Allen Chen 2022-01-14 2014
b5c84a9edcd418 Allen Chen 2022-01-14 2015 if ((binfo[0] & BIT(7)) || (binfo[1] & BIT(3))) {
b5c84a9edcd418 Allen Chen 2022-01-14 2016 dev_err(dev, "HDCP max cascade device exceed");
b5c84a9edcd418 Allen Chen 2022-01-14 2017 return 0;
b5c84a9edcd418 Allen Chen 2022-01-14 2018 }
b5c84a9edcd418 Allen Chen 2022-01-14 2019
b5c84a9edcd418 Allen Chen 2022-01-14 2020 if (!down_stream_count ||
b5c84a9edcd418 Allen Chen 2022-01-14 2021 down_stream_count > MAX_HDCP_DOWN_STREAM_COUNT) {
b5c84a9edcd418 Allen Chen 2022-01-14 2022 dev_err(dev, "HDCP down stream count Error %d",
b5c84a9edcd418 Allen Chen 2022-01-14 2023 down_stream_count);
b5c84a9edcd418 Allen Chen 2022-01-14 2024 return 0;
b5c84a9edcd418 Allen Chen 2022-01-14 2025 }
9665163df60e16 Hermes Wu 2024-09-23 2026 err = it6505_get_ksvlist(it6505, sha1_input, down_stream_count * 5);
b5c84a9edcd418 Allen Chen 2022-01-14 @2027 if (err < 0)
b5c84a9edcd418 Allen Chen 2022-01-14 2028 return err;
b5c84a9edcd418 Allen Chen 2022-01-14 2029
9665163df60e16 Hermes Wu 2024-09-23 2030 msg_count += down_stream_count * 5;
b5c84a9edcd418 Allen Chen 2022-01-14 2031
b5c84a9edcd418 Allen Chen 2022-01-14 2032 it6505->hdcp_down_stream_count = down_stream_count;
b5c84a9edcd418 Allen Chen 2022-01-14 2033 sha1_input[msg_count++] = binfo[0];
b5c84a9edcd418 Allen Chen 2022-01-14 2034 sha1_input[msg_count++] = binfo[1];
b5c84a9edcd418 Allen Chen 2022-01-14 2035
b5c84a9edcd418 Allen Chen 2022-01-14 2036 it6505_set_bits(it6505, REG_HDCP_CTRL2, HDCP_EN_M0_READ,
b5c84a9edcd418 Allen Chen 2022-01-14 2037 HDCP_EN_M0_READ);
b5c84a9edcd418 Allen Chen 2022-01-14 2038
b5c84a9edcd418 Allen Chen 2022-01-14 2039 err = regmap_bulk_read(it6505->regmap, REG_M0_0_7,
b5c84a9edcd418 Allen Chen 2022-01-14 2040 sha1_input + msg_count, 8);
b5c84a9edcd418 Allen Chen 2022-01-14 2041
b5c84a9edcd418 Allen Chen 2022-01-14 2042 it6505_set_bits(it6505, REG_HDCP_CTRL2, HDCP_EN_M0_READ, 0x00);
b5c84a9edcd418 Allen Chen 2022-01-14 2043
b5c84a9edcd418 Allen Chen 2022-01-14 2044 if (err < 0) {
b5c84a9edcd418 Allen Chen 2022-01-14 2045 dev_err(dev, " Warning, Read M value Fail");
b5c84a9edcd418 Allen Chen 2022-01-14 2046 return err;
b5c84a9edcd418 Allen Chen 2022-01-14 2047 }
b5c84a9edcd418 Allen Chen 2022-01-14 2048
b5c84a9edcd418 Allen Chen 2022-01-14 2049 msg_count += 8;
b5c84a9edcd418 Allen Chen 2022-01-14 2050
b5c84a9edcd418 Allen Chen 2022-01-14 2051 return msg_count;
b5c84a9edcd418 Allen Chen 2022-01-14 2052 }
b5c84a9edcd418 Allen Chen 2022-01-14 2053
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-09-24 11:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 9:48 [PATCH v3 0/3] drm/bridge: it6505: update dp aux funxtion Hermes Wu
2024-09-23 9:48 ` [PATCH v3 1/3] drm/bridge: it6505: fix AUX read use aux fifo Hermes Wu
2024-09-23 10:07 ` Dmitry Baryshkov
2024-09-23 9:48 ` [PATCH v3 2/3] drm/bridge: it6505: HDCP CTS fail on repeater items Hermes Wu
2024-09-23 10:14 ` Dmitry Baryshkov
2024-09-23 10:45 ` Hermes.Wu
2024-09-23 11:49 ` Dmitry Baryshkov
2024-09-24 2:57 ` Hermes.Wu
2024-09-24 2:59 ` Pin-yen Lin
2024-09-24 11:01 ` kernel test robot [this message]
2024-09-23 9:48 ` [PATCH v3 3/3] drm/bridge: it6505: Add MCCS support Hermes Wu
2024-09-23 12:00 ` Dmitry Baryshkov
2024-09-24 3:52 ` Hermes.Wu
2024-09-24 9:59 ` Dmitry Baryshkov
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=202409241856.OWgR1x3Y-lkp@intel.com \
--to=lkp@intel.com \
--cc=Hermes.Wu@ite.com.tw \
--cc=Kenneth.hung@ite.com.tw \
--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=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=treapking@chromium.org \
--cc=tzimmermann@suse.de \
/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