public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "CK Hu (胡俊光)" <ck.hu@mediatek.com>
To: "seanpaul@chromium.org" <seanpaul@chromium.org>,
	"dianders@chromium.org" <dianders@chromium.org>,
	"hsinyi@chromium.org" <hsinyi@chromium.org>
Cc: "dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"tzimmermann@suse.de" <tzimmermann@suse.de>,
	"airlied@linux.ie" <airlied@linux.ie>
Subject: Re: [PATCH] drm_bridge: register content protect property
Date: Wed, 2 Nov 2022 05:37:53 +0000	[thread overview]
Message-ID: <fa5cb82c422c5774130e88da9bc19943291cd754.camel@mediatek.com> (raw)
In-Reply-To: <20221011101850.200455-1-hsinyi@chromium.org>

Hi, Hsin-Yi:

On Tue, 2022-10-11 at 18:18 +0800, Hsin-Yi Wang wrote:
> Some bridges are able to update HDCP status from userspace requests
> if
> they support HDCP.
> 
> HDCP property is the same as other connector properties that need to
> be
> created after the connecter is initialized and before the connector
> is
> registered.

So this is anx7625 support HDCP, right?
All connector with anx7625 has this problem, so I think this should be
done in drm core not in each SoC driver.

Regards,
CK

> 
> Signed-off-by: Hsin-Yi Wang <hsinyi@chromium.org>
> ---
>  drivers/gpu/drm/drm_bridge_connector.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/gpu/drm/drm_bridge_connector.c
> b/drivers/gpu/drm/drm_bridge_connector.c
> index 1c7d936523df5..a3b9ef8dc3f0b 100644
> --- a/drivers/gpu/drm/drm_bridge_connector.c
> +++ b/drivers/gpu/drm/drm_bridge_connector.c
> @@ -7,6 +7,7 @@
>  #include <linux/module.h>
>  #include <linux/slab.h>
>  
> +#include <drm/display/drm_hdcp_helper.h>
>  #include <drm/drm_atomic_state_helper.h>
>  #include <drm/drm_bridge.h>
>  #include <drm/drm_bridge_connector.h>
> @@ -398,6 +399,8 @@ struct drm_connector
> *drm_bridge_connector_init(struct drm_device *drm,
>  	if (panel_bridge)
>  		drm_panel_bridge_set_orientation(connector,
> panel_bridge);
>  
> +	drm_connector_attach_content_protection_property(connector,
> true);
> +
>  	return connector;
>  }
>  EXPORT_SYMBOL_GPL(drm_bridge_connector_init);

  parent reply	other threads:[~2022-11-02  5:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11 10:18 [PATCH] drm_bridge: register content protect property Hsin-Yi Wang
2022-10-11 16:03 ` kernel test robot
2022-10-11 17:35 ` kernel test robot
2022-11-02  5:37 ` CK Hu (胡俊光) [this message]
2022-11-03  5:46   ` CK Hu (胡俊光)

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=fa5cb82c422c5774130e88da9bc19943291cd754.camel@mediatek.com \
    --to=ck.hu@mediatek.com \
    --cc=airlied@linux.ie \
    --cc=dianders@chromium.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hsinyi@chromium.org \
    --cc=linux-kernel@vger.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