Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Anshuman Gupta <anshuman.gupta@intel.com>,
	dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: Sean Paul <seanpaul@chromium.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Maxime Ripard <mripard@kernel.org>
Subject: Re: [Intel-gfx] [RFC] drm/hdcp: Max MST content streams
Date: Tue, 20 Oct 2020 13:17:42 +0300	[thread overview]
Message-ID: <87zh4h8am1.fsf@intel.com> (raw)
In-Reply-To: <5fb7a376-d520-97e0-54cd-6174019ce1d1@linux.intel.com>

On Tue, 20 Oct 2020, Maarten Lankhorst <maarten.lankhorst@linux.intel.com> wrote:
> Op 20-10-2020 om 11:42 schreef Jani Nikula:
>> On Mon, 19 Oct 2020, Anshuman Gupta <anshuman.gupta@intel.com> wrote:
>>> Let's define Maximum MST content streams up to four
>>> generically which can be supported by modern display
>>> controllers.
>>>
>>> Cc: Sean Paul <seanpaul@chromium.org>
>>> Cc: Ramalingam C <ramalingam.c@intel.com>
>>> Signed-off-by: Anshuman Gupta <anshuman.gupta@intel.com>
>> Hey drm-misc maintainers,
>>
>> I'd like to get an ack to merge this via drm-intel as part of [1].
>>
>> Thanks,
>> Jani.
>>
>>
>>
>> [1] http://lore.kernel.org/r/20201014045252.13608-1-anshuman.gupta@intel.com
>>
>>
>>
>>> ---
>>>  include/drm/drm_hdcp.h | 8 ++++----
>>>  1 file changed, 4 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/include/drm/drm_hdcp.h b/include/drm/drm_hdcp.h
>>> index fe58dbb46962..ac22c246542a 100644
>>> --- a/include/drm/drm_hdcp.h
>>> +++ b/include/drm/drm_hdcp.h
>>> @@ -101,11 +101,11 @@
>>>  
>>>  /* Following Macros take a byte at a time for bit(s) masking */
>>>  /*
>>> - * TODO: This has to be changed for DP MST, as multiple stream on
>>> - * same port is possible.
>>> - * For HDCP2.2 on HDMI and DP SST this value is always 1.
>>> + * TODO: HDCP_2_2_MAX_CONTENT_STREAMS_CNT is based upon actual
>>> + * H/W MST streams capacity.
>>> + * This required to be moved out to platform specific header.
>>>   */
>>> -#define HDCP_2_2_MAX_CONTENT_STREAMS_CNT	1
>>> +#define HDCP_2_2_MAX_CONTENT_STREAMS_CNT	4
>>>  #define HDCP_2_2_TXCAP_MASK_LEN			2
>>>  #define HDCP_2_2_RXCAPS_LEN			3
>>>  #define HDCP_2_2_RX_REPEATER(x)			((x) & BIT(0))
>
> Well since it's such a small change..
>
> Acked-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>

Thanks.

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2020-10-20 10:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19  7:12 [Intel-gfx] [RFC] drm/hdcp: Max MST content streams Anshuman Gupta
2020-10-19  8:14 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-10-19  9:45 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-10-20  9:42 ` [Intel-gfx] [RFC] " Jani Nikula
2020-10-20  9:47   ` Maarten Lankhorst
2020-10-20 10:17     ` Jani Nikula [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=87zh4h8am1.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=seanpaul@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