From: Lyude Paul <lyude@redhat.com>
To: Wayne Lin <Wayne.Lin@amd.com>, dri-devel@lists.freedesktop.org
Cc: eryk.brol@amd.com, qingqing.zhuo@amd.com, stable@vger.kernel.org,
jerry.zuo@amd.com, Nicholas.Kazlauskas@amd.com
Subject: Re: [PATCH 0/2] Set CLEAR_PAYLOAD_ID_TABLE as broadcast request
Date: Wed, 24 Feb 2021 13:06:09 -0500 [thread overview]
Message-ID: <cbb963ec0b2fb93ddbc81f83e5e6eba4264b9a5c.camel@redhat.com> (raw)
In-Reply-To: <20210222040027.23505-1-Wayne.Lin@amd.com>
ooh, nice catches! For the whole series this is:
Reviewed-by: Lyude Paul <lyude@redhat.com>
I will go ahead and push these to drm-misc-next
On Mon, 2021-02-22 at 12:00 +0800, Wayne Lin wrote:
> While testing MST hotplug events on daisy chain monitors, find out
> that CLEAR_PAYLOAD_ID_TABLE is not broadcasted and payload id table
> is not reset. Dig in deeper and find out two parts needed to be fixed.
>
> 1. Link_Count_Total & Link_Count_Remaining of Broadcast message are
> incorrect. Should set lct=1 & lcr=6
> 2. CLEAR_PAYLOAD_ID_TABLE request message is not set as path broadcast
> request message. Should fix this.
>
> Wayne Lin (2):
> drm/dp_mst: Revise broadcast msg lct & lcr
> drm/dp_mst: Set CLEAR_PAYLOAD_ID_TABLE as broadcast
>
> drivers/gpu/drm/drm_dp_mst_topology.c | 14 +++++++++++---
> 1 file changed, 11 insertions(+), 3 deletions(-)
>
> --
> 2.17.1
>
--
Sincerely,
Lyude Paul (she/her)
Software Engineer at Red Hat
Note: I deal with a lot of emails and have a lot of bugs on my plate. If you've
asked me a question, are waiting for a review/merge on a patch, etc. and I
haven't responded in a while, please feel free to send me another email to check
on my status. I don't bite!
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2021-02-24 18:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 4:00 [PATCH 0/2] Set CLEAR_PAYLOAD_ID_TABLE as broadcast request Wayne Lin
2021-02-22 4:00 ` [PATCH 1/2] drm/dp_mst: Revise broadcast msg lct & lcr Wayne Lin
2021-02-22 17:02 ` Ville Syrjälä
2021-02-22 17:09 ` Ville Syrjälä
2021-02-23 5:32 ` Lin, Wayne
2021-02-23 13:26 ` Ville Syrjälä
2021-02-24 9:47 ` Lin, Wayne
2021-02-22 4:00 ` [PATCH 2/2] drm/dp_mst: Set CLEAR_PAYLOAD_ID_TABLE as broadcast Wayne Lin
2021-02-22 17:00 ` Ville Syrjälä
2021-02-23 5:32 ` Lin, Wayne
2021-02-23 13:21 ` Ville Syrjälä
2021-02-24 18:06 ` Lyude Paul [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=cbb963ec0b2fb93ddbc81f83e5e6eba4264b9a5c.camel@redhat.com \
--to=lyude@redhat.com \
--cc=Nicholas.Kazlauskas@amd.com \
--cc=Wayne.Lin@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eryk.brol@amd.com \
--cc=jerry.zuo@amd.com \
--cc=qingqing.zhuo@amd.com \
--cc=stable@vger.kernel.org \
/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