dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Ramalingam C <ramalingam.c@intel.com>
Cc: intel-gfx@lists.freedesktop.org, alexander.usyskin@intel.com,
	dri-devel@lists.freedesktop.org, kbuild-all@01.org,
	tomas.winkler@intel.com
Subject: Re: [PATCH v5 16/40] drm/i915: Implement HDCP2.2 repeater authentication
Date: Wed, 27 Jun 2018 22:23:45 +0800	[thread overview]
Message-ID: <201806272024.2CyDziJr%fengguang.wu@intel.com> (raw)
In-Reply-To: <1530088829-11730-17-git-send-email-ramalingam.c@intel.com>

Hi Ramalingam,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on v4.18-rc2 next-20180627]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Ramalingam-C/drm-i915-Implement-HDCP2-2/20180627-174219
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
reproduce:
        # apt-get install sparse
        make ARCH=x86_64 allmodconfig
        make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

   drivers/gpu/drm/i915/i915_drv.h:3674:16: sparse: expression using sizeof(void)
>> drivers/gpu/drm/i915/intel_hdcp.c:1451:30: sparse: incorrect type in assignment (different base types) @@    expected restricted __be16 [assigned] [usertype] k @@    got e] k @@
   drivers/gpu/drm/i915/intel_hdcp.c:1451:30:    expected restricted __be16 [assigned] [usertype] k
   drivers/gpu/drm/i915/intel_hdcp.c:1451:30:    got int
   drivers/gpu/drm/i915/intel_hdcp.c:1890:6: sparse: symbol 'is_hdcp2_supported' was not declared. Should it be static?

vim +1451 drivers/gpu/drm/i915/intel_hdcp.c

  1432	
  1433	static
  1434	int hdcp2_propagate_stream_management_info(struct intel_connector *connector)
  1435	{
  1436		struct intel_digital_port *intel_dig_port = conn_to_dig_port(connector);
  1437		struct intel_hdcp *hdcp = &connector->hdcp;
  1438		union {
  1439			struct hdcp2_rep_stream_manage stream_manage;
  1440			struct hdcp2_rep_stream_ready stream_ready;
  1441		} msgs;
  1442		const struct intel_hdcp_shim *shim = hdcp->hdcp_shim;
  1443		int ret;
  1444	
  1445		/* Prepare RepeaterAuth_Stream_Manage msg */
  1446		msgs.stream_manage.msg_id = HDCP_2_2_REP_STREAM_MANAGE;
  1447		reverse_endianness(msgs.stream_manage.seq_num_m, HDCP_2_2_SEQ_NUM_LEN,
  1448				   (u8 *)&hdcp->seq_num_m);
  1449	
  1450		/* K no of streams is fixed as 1. Stored as big-endian. */
> 1451		msgs.stream_manage.k = __swab16(1);
  1452	
  1453		/* For HDMI this is forced to be 0x0. For DP SST also this is 0x0. */
  1454		msgs.stream_manage.streams[0].stream_id = 0;
  1455		msgs.stream_manage.streams[0].stream_type = hdcp->content_type;
  1456	
  1457		/* Send it to Repeater */
  1458		ret = shim->write_2_2_msg(intel_dig_port, &msgs.stream_manage,
  1459					  sizeof(msgs.stream_manage));
  1460		if (ret < 0)
  1461			return ret;
  1462	
  1463		ret = shim->read_2_2_msg(intel_dig_port, HDCP_2_2_REP_STREAM_READY,
  1464					 &msgs.stream_ready, sizeof(msgs.stream_ready));
  1465		if (ret < 0)
  1466			return ret;
  1467	
  1468		hdcp->mei_data.seq_num_m = hdcp->seq_num_m;
  1469		hdcp->mei_data.streams[0].stream_type = hdcp->content_type;
  1470	
  1471		ret = hdcp2_verify_mprime(connector, &msgs.stream_ready);
  1472		if (ret < 0)
  1473			return ret;
  1474	
  1475		hdcp->seq_num_m++;
  1476	
  1477		if (hdcp->seq_num_m > HDCP_2_2_SEQ_NUM_MAX) {
  1478			DRM_DEBUG_KMS("seq_num_m roll over.\n");
  1479			return -1;
  1480		}
  1481	
  1482		return 0;
  1483	}
  1484	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-06-27 14:23 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-27  8:39 [PATCH v5 00/40] drm/i915: Implement HDCP2.2 Ramalingam C
2018-06-27  8:39 ` [PATCH v5 01/40] drm: hdcp2.2 authentication msg definitions Ramalingam C
2018-07-09 20:21   ` Sean Paul
2018-07-11 17:57     ` C, Ramalingam
2018-07-11 19:08       ` Sean Paul
2018-07-12  3:52         ` [Intel-gfx] " C, Ramalingam
2018-06-27  8:39 ` [PATCH v5 02/40] drm: HDMI and DP specific HDCP2.2 defines Ramalingam C
2018-07-09 20:23   ` Sean Paul
2018-07-11 17:59     ` C, Ramalingam
2018-06-27  8:39 ` [PATCH v5 03/40] mei: bus: whitelist hdcp client Ramalingam C
2018-06-27  8:39 ` [PATCH v5 04/40] linux/mei: Header for mei_hdcp driver interface Ramalingam C
2018-06-27  8:39 ` [PATCH v5 05/40] drm/i915: wrapping all hdcp var into intel_hdcp Ramalingam C
2018-07-09 20:30   ` Sean Paul
2018-07-11 18:06     ` C, Ramalingam
2018-06-27  8:39 ` [PATCH v5 06/40] drm/i915: Define HDCP2.2 related variables Ramalingam C
2018-07-09 20:31   ` Sean Paul
2018-07-12 14:33     ` Ramalingam C
2018-06-27  8:39 ` [PATCH v5 07/40] drm/i915: Define Intel HDCP2.2 registers Ramalingam C
2018-07-09 20:31   ` Sean Paul
2018-06-27  8:39 ` [PATCH v5 08/40] drm/i915: Initialize HDCP2.2 and its MEI interface Ramalingam C
2018-06-28 11:41   ` [Intel-gfx] " Dan Carpenter
2018-06-27  8:39 ` [PATCH v5 09/40] drm/i915: Schedule hdcp_check_link in _intel_hdcp_enable Ramalingam C
2018-07-09 20:34   ` Sean Paul
2018-07-11 19:07     ` C, Ramalingam
2018-07-11 21:05       ` Sean Paul
2018-07-12  3:49         ` C, Ramalingam
2018-06-27  8:39 ` [PATCH v5 10/40] drm/i915: Pullout the bksv read and validation Ramalingam C
2018-07-09 20:35   ` [Intel-gfx] " Sean Paul
2018-06-27  8:40 ` [PATCH v5 11/40] drm/i915: Enable superior HDCP ver that is capable Ramalingam C
2018-07-09 20:44   ` Sean Paul
2018-07-12 14:30     ` Ramalingam C
2018-06-27  8:40 ` [PATCH v5 12/40] drm/i915: Enable HDCP1.4 incase of HDCP2.2 failure Ramalingam C
2018-07-09 20:44   ` Sean Paul
2018-07-12 14:31     ` [Intel-gfx] " Ramalingam C
2018-06-27  8:40 ` [PATCH v5 13/40] drm/i915: Implement HDCP2.2 Enable and Disable Ramalingam C
2018-07-09 20:48   ` [Intel-gfx] " Sean Paul
2018-07-12 14:41     ` Ramalingam C
2018-06-27  8:40 ` [PATCH v5 14/40] drm/i915: Enable and Disable HDCP2.2 port encryption Ramalingam C
2018-06-27  8:40 ` [PATCH v5 15/40] drm/i915: Implement HDCP2.2 receiver authentication Ramalingam C
2018-06-27  8:40 ` [PATCH v5 16/40] drm/i915: Implement HDCP2.2 repeater authentication Ramalingam C
2018-06-27 14:23   ` kbuild test robot [this message]
2018-06-27  8:40 ` [PATCH v5 17/40] drm/i915: Implement HDCP2.2 link integrity check Ramalingam C
2018-06-27  8:40 ` [PATCH v5 18/40] drm/i915: Handle HDCP2.2 downstream topology change Ramalingam C
2018-06-27  8:40 ` [PATCH v5 19/40] drm/i915: hdcp_check_link only on CP_IRQ Ramalingam C
2018-07-09 20:49   ` Sean Paul
2018-06-27  8:40 ` [PATCH v5 20/40] drm/i915: Check HDCP 1.4 and 2.2 link " Ramalingam C
2018-07-09 20:50   ` Sean Paul
2018-07-12  3:54     ` C, Ramalingam
2018-06-27  8:40 ` [PATCH v5 21/40] drm/i915/gmbus: Increase the Bytes per Rd/Wr Op Ramalingam C
2018-06-27  8:40 ` [PATCH v5 22/40] drm/i915/gmbus: Enable burst read Ramalingam C
2018-06-27  8:40 ` [PATCH v5 23/40] drm/i915: Implement the HDCP2.2 support for DP Ramalingam C
2018-06-27  8:40 ` [PATCH v5 24/40] drm/i915: Implement the HDCP2.2 support for HDMI Ramalingam C
2018-06-27  8:40 ` [PATCH v5 25/40] drm/i915: Add HDCP2.2 support for DP connectors Ramalingam C
2018-06-27  8:40 ` [PATCH v5 26/40] drm/i915: Add HDCP2.2 support for HDMI connectors Ramalingam C
2018-06-27  8:40 ` [PATCH v5 27/40] misc/mei/hdcp: Client driver for HDCP application Ramalingam C
2018-06-27  8:40 ` [PATCH v5 28/40] misc/mei/hdcp: Component framework for I915 Interface Ramalingam C
2018-06-27 14:46   ` kbuild test robot
2018-06-27 14:46   ` [RFC PATCH] misc/mei/hdcp: mei_hdcp_component_registered can be static kbuild test robot
2018-06-27  8:40 ` [PATCH v5 29/40] misc/mei/hdcp: Define ME FW interface for HDCP2.2 Ramalingam C
2018-06-27  8:40 ` [PATCH v5 30/40] misc/mei/hdcp: Initiate Wired HDCP2.2 Tx Session Ramalingam C
2018-06-27  8:40 ` [PATCH v5 31/40] misc/mei/hdcp: Verify Receiver Cert and prepare km Ramalingam C
2018-06-27  8:40 ` [PATCH v5 32/40] misc/mei/hdcp: Verify H_prime Ramalingam C
2018-06-27  8:40 ` [PATCH v5 33/40] misc/mei/hdcp: Store the HDCP Pairing info Ramalingam C
2018-06-27  8:40 ` [PATCH v5 34/40] misc/mei/hdcp: Initiate Locality check Ramalingam C
2018-06-27  8:40 ` [PATCH v5 35/40] misc/mei/hdcp: Verify L_prime Ramalingam C
2018-06-27  8:40 ` [PATCH v5 36/40] misc/mei/hdcp: Prepare Session Key Ramalingam C
2018-06-27  8:40 ` [PATCH v5 37/40] misc/mei/hdcp: Repeater topology verification and ack Ramalingam C
2018-06-27  8:40 ` [PATCH v5 38/40] misc/mei/hdcp: Verify M_prime Ramalingam C
2018-06-27  8:40 ` [PATCH v5 39/40] misc/mei/hdcp: Enabling the HDCP authentication Ramalingam C
2018-06-27  8:40 ` [PATCH v5 40/40] misc/mei/hdcp: Closing wired HDCP2.2 Tx Session Ramalingam C

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=201806272024.2CyDziJr%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=alexander.usyskin@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kbuild-all@01.org \
    --cc=ramalingam.c@intel.com \
    --cc=tomas.winkler@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).