From: Lyude Paul <lyude@redhat.com>
To: "Zuo, Jerry" <Jerry.Zuo@amd.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Cc: "Wentland, Harry" <Harry.Wentland@amd.com>,
"Li, Sun peng (Leo)" <Sunpeng.Li@amd.com>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
"Koenig, Christian" <Christian.Koenig@amd.com>,
"Zhou, David(ChunMing)" <David1.Zhou@amd.com>,
David Airlie <airlied@linux.ie>, "Li, Roman" <Roman.Li@amd.com>,
"S, Shirish" <Shirish.S@amd.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] drm/amd/dm: Don't forget to attach MST encoders
Date: Mon, 19 Nov 2018 13:51:53 -0500 [thread overview]
Message-ID: <6033a16ccbc6e1286b4bfd082f0de9f0d60594b7.camel@redhat.com> (raw)
In-Reply-To: <BY1PR12MB0406C1EC0BCD2F6A295CCE3AE5D80@BY1PR12MB0406.namprd12.prod.outlook.com>
Cool! If it did actually fix those problems, would you mind making sure this
gets Cc'd to stable when it gets pushed upstream?
On Mon, 2018-11-19 at 15:00 +0000, Zuo, Jerry wrote:
> Reviewed-by: Jerry (Fangzhi) Zuo <Jerry.Zuo@amd.com>
>
> The change fixed MST + SST daisy chain and S3 scenarios. The issue shows
> huge delay in MST + SST daisy chain, and soft hang in S3 resume.
>
> The aux sequence is changed by failed iteration search in
> drm_connector_for_each_possible_encoder().
> The failure of searching for the best encoder for the connector due to the
> miss of attached encoder in the process of adding MST connector. The
> iteration search takes time to push drm_dp_send_enum_path_resources() aux
> transaction after the mode probe, and causes conflict to
> drm_dp_mst_i2c_xfer(), leading to the aux transaction timeout.
>
> -----Original Message-----
> From: Lyude Paul <lyude@redhat.com>
> Sent: November 16, 2018 6:25 PM
> To: amd-gfx@lists.freedesktop.org
> Cc: Zuo, Jerry <Jerry.Zuo@amd.com>; Wentland, Harry <Harry.Wentland@amd.com>
> ; Li, Sun peng (Leo) <Sunpeng.Li@amd.com>; Deucher, Alexander <
> Alexander.Deucher@amd.com>; Koenig, Christian <Christian.Koenig@amd.com>;
> Zhou, David(ChunMing) <David1.Zhou@amd.com>; David Airlie <airlied@linux.ie>
> ; Li, Roman <Roman.Li@amd.com>; S, Shirish <Shirish.S@amd.com>; Daniel
> Vetter <daniel.vetter@ffwll.ch>; dri-devel@lists.freedesktop.org;
> linux-kernel@vger.kernel.org
> Subject: [PATCH 1/2] drm/amd/dm: Don't forget to attach MST encoders
>
> Drive-by fix, this is bound to cause problems somewhere.
>
> Signed-off-by: Lyude Paul <lyude@redhat.com>
> Cc: Jerry Zuo <Jerry.Zuo@amd.com>
> ---
> drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_mst_types.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_mst_types.c
> b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_mst_types.c
> index d02c32a1039c..0cca1809fdcd 100644
> --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_mst_types.c
> +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_mst_types.c
> @@ -342,6 +342,8 @@ dm_dp_add_mst_connector(struct drm_dp_mst_topology_mgr
> *mgr,
> master->connector_id);
>
> aconnector->mst_encoder = dm_dp_create_fake_mst_encoder(master);
> + drm_connector_attach_encoder(&aconnector->base,
> + &aconnector->mst_encoder->base);
>
> /*
> * TODO: understand why this one is needed
--
Cheers,
Lyude Paul
next prev parent reply other threads:[~2018-11-19 18:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 23:24 [PATCH 0/2] drm/amd/dm: Misc MST connector fixes Lyude Paul
2018-11-16 23:24 ` [PATCH 1/2] drm/amd/dm: Don't forget to attach MST encoders Lyude Paul
2018-11-19 15:00 ` Zuo, Jerry
2018-11-19 18:51 ` Lyude Paul [this message]
2018-11-19 18:54 ` Zuo, Jerry
2018-11-16 23:24 ` [PATCH 2/2] drm/amd/dm: Understand why attaching path/tile properties are needed Lyude Paul
2018-11-19 19:44 ` Zuo, Jerry
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=6033a16ccbc6e1286b4bfd082f0de9f0d60594b7.camel@redhat.com \
--to=lyude@redhat.com \
--cc=Alexander.Deucher@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=David1.Zhou@amd.com \
--cc=Harry.Wentland@amd.com \
--cc=Jerry.Zuo@amd.com \
--cc=Roman.Li@amd.com \
--cc=Shirish.S@amd.com \
--cc=Sunpeng.Li@amd.com \
--cc=airlied@linux.ie \
--cc=amd-gfx@lists.freedesktop.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®