From: "CK Hu (胡俊光)" <ck.hu@mediatek.com>
To: "Mac Shen (沈俊)" <Mac.Shen@mediatek.com>,
"chunkuang.hu@kernel.org" <chunkuang.hu@kernel.org>,
"Jitao Shi (石记涛)" <jitao.shi@mediatek.com>,
"daniel@ffwll.ch" <daniel@ffwll.ch>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"airlied@gmail.com" <airlied@gmail.com>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Shuijing Li (李水静)" <Shuijing.Li@mediatek.com>
Subject: Re: [PATCH] drm/mediatek/dp: Add the HDCP feature for DisplayPort
Date: Thu, 4 Jan 2024 06:00:03 +0000 [thread overview]
Message-ID: <c645c91387c1056307b2ee303474bb8dd32211bd.camel@mediatek.com> (raw)
In-Reply-To: <20231124085346.26602-1-mac.shen@mediatek.com>
Hi, Mac:
On Fri, 2023-11-24 at 16:53 +0800, mac.shen wrote:
> Add tee client application, HDCP 1.x and 2.x authentication for
> DisplayPort
> to support the HDCP feature.
>
> Signed-off-by: mac.shen <mac.shen@mediatek.com>
> ---
[snip]
> +
> static int mtk_dp_probe(struct platform_device *pdev)
> {
> struct mtk_dp *mtk_dp;
> @@ -2657,6 +2778,16 @@ static int mtk_dp_probe(struct platform_device
> *pdev)
> if (ret)
> return ret;
>
> + INIT_WORK(&mtk_dp->hdcp_work, mtk_dp_hdcp_handle);
> + mtk_dp->hdcp_workqueue = create_workqueue("mtk_dp_hdcp_work");
> + if (!mtk_dp->hdcp_workqueue) {
> + dev_err(mtk_dp->dev, "failed to create hdcp work
> queue");
> + return -ENOMEM;
> + }
> +
> + mtk_dp->hdcp_info.aux = &mtk_dp->aux;
> + mtk_dp->hdcp_info.regs = mtk_dp->regs;
It's not necessary to duplicate aux and regs, so drop this.
Regards,
CK
> +
> mtk_dp->bridge.funcs = &mtk_dp_bridge_funcs;
> mtk_dp->bridge.of_node = dev->of_node;
> mtk_dp->bridge.type = mtk_dp->data->bridge_type;
>
next prev parent reply other threads:[~2024-01-04 6:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231124085346.26602-1-mac.shen@mediatek.com>
2023-11-25 15:17 ` kernel test robot
2023-11-25 16:48 ` kernel test robot
2023-12-01 1:46 ` CK Hu (胡俊光)
2023-12-01 1:59 ` CK Hu (胡俊光)
2023-12-01 2:56 ` CK Hu (胡俊光)
2023-12-01 8:27 ` CK Hu (胡俊光)
2023-12-01 8:52 ` CK Hu (胡俊光)
2023-12-19 1:59 ` CK Hu (胡俊光)
2024-01-04 6:00 ` CK Hu (胡俊光) [this message]
2024-01-04 6:14 ` CK Hu (胡俊光)
2024-01-04 6:46 ` CK Hu (胡俊光)
2024-01-04 7:42 ` CK Hu (胡俊光)
2024-01-04 8:01 ` CK Hu (胡俊光)
2024-01-04 8:56 ` CK Hu (胡俊光)
2024-01-04 9:10 ` CK Hu (胡俊光)
2024-01-04 9:43 ` CK Hu (胡俊光)
2024-01-05 6:10 ` CK Hu (胡俊光)
2024-01-08 6:00 ` 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=c645c91387c1056307b2ee303474bb8dd32211bd.camel@mediatek.com \
--to=ck.hu@mediatek.com \
--cc=Mac.Shen@mediatek.com \
--cc=Shuijing.Li@mediatek.com \
--cc=airlied@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jitao.shi@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=p.zabel@pengutronix.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
all inboxes | Powered by JetHome®