From: <Hermes.Wu@ite.com.tw>
To: <dmitry.baryshkov@linaro.org>
Cc: <treapking@chromium.org>, <Kenneth.Hung@ite.com.tw>,
<andrzej.hajda@intel.com>, <neil.armstrong@linaro.org>,
<rfoss@kernel.org>, <Laurent.pinchart@ideasonboard.com>,
<jonas@kwiboo.se>, <jernej.skrabec@gmail.com>,
<maarten.lankhorst@linux.intel.com>, <mripard@kernel.org>,
<tzimmermann@suse.de>, <airlied@gmail.com>, <simona@ffwll.ch>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v3 2/3] drm/bridge: it6505: HDCP CTS fail on repeater items
Date: Mon, 23 Sep 2024 10:45:49 +0000 [thread overview]
Message-ID: <a0a8f862018b4c9aa689672551e7a492@ite.com.tw> (raw)
In-Reply-To: <4viir5prnuvpp76npblwmdrwlttm5daumvdnocipdsn6geyxvf@2yfcytjb3ono>
>On Mon, Sep 23, 2024 at 05:48:28PM GMT, Hermes Wu wrote:
>> From: Hermes Wu <Hermes.wu@ite.com.tw>
>>
>> Changes in v3:
>> -add detials about fail item and changes.
>>
>>
>> Fix HDCP CTS fail items on UNIGRAF DRP-100
>>
>> DUT must Support 127 devices.
>> DUT must check BSTATUS when receive CP_IRQ.
>> DUT must enable encryption when R0' is ready.
>> DUT must retry V' check 3 times.
>> it6505 must read DRP-100 KSV FIFO by FIFO mode.
>> it6505 should restart HDCP within 5s if KSV not ready.
>
>Still not readable.
>
>English text, please. Split the patch to fix one issue at a time.
>Describe the _reason_ for the change. Annotate fixes with Fixes tags.
>
with fixes tag include drm/bridge like this ? => "Fixes: drm/bridge: it6505: HDCP CTS fail 1B-xx"
About the reason about bug fixes.
for example, the 1B-01 device count.
will this readable?
" When connect to HDCP repeater, it6505 must support 127 downstream devices. "
And this will be only one change in a patch?
>>
>> Signed-off-by: Hermes Wu <Hermes.wu@ite.com.tw>
>> ---
>> drivers/gpu/drm/bridge/ite-it6505.c | 112 ++++++++++++++++++----------
>> 1 file changed, 74 insertions(+), 38 deletions(-)
>
>--
>With best wishes
>Dmitry
BR,
Hermes
next prev parent reply other threads:[~2024-09-23 10:45 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 [this message]
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
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=a0a8f862018b4c9aa689672551e7a492@ite.com.tw \
--to=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=dmitry.baryshkov@linaro.org \
--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=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