[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <161056927774.3661239.6186577459996584479@swboyd.mtv.corp.google.com>
Date: Wed, 13 Jan 2021 12:21:17 -0800
From: Stephen Boyd <swboyd@...omium.org>
To: khsieh@...eaurora.org
Cc: dri-devel@...ts.freedesktop.org, robdclark@...il.com,
sean@...rly.run, tanmay@...eaurora.org, abhinavk@...eaurora.org,
aravindh@...eaurora.org, airlied@...ux.ie, daniel@...ll.ch,
linux-arm-msm@...r.kernel.org, freedreno@...ts.freedesktop.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] drm/msm/dp: postpone irq_hpd event during connection pending state
Quoting khsieh@...eaurora.org (2021-01-13 09:44:24)
> On 2021-01-11 11:55, Stephen Boyd wrote:
> > Quoting Kuogee Hsieh (2021-01-07 12:30:24)
> >> irq_hpd event can only be executed at connected state. Therefore
> >> irq_hpd event should be postponed if it happened at connection
> >> pending state. This patch also make sure both link rate and lane
> >
> > Why does it happen at connection pending state?
> plug in need two state to complete it.
> advance to connection pending state once link training completed and
> sent uevent notification to frame work.
> transition to connected state after frame work provided resolution
> timing and start transmit video panel.
> Therefore irq_hpd should not be handled if it occurred before connected
> state.
> >
> >> are valid before start link training.
> >
> > Can this part about link rate and lane being valid be split off into
> > another patch?
> >
> ok, i will spilt this patch into two.
> I will merge irq_hpd event part into 2nd patch (drm/msm/dp: unplug
> interrupt missed after irq_hpd handler).
It looks like Rob already picked this patch up
https://gitlab.freedesktop.org/drm/msm/-/commit/2b5f09cadfc576817c0450e01d454f750909b103
Powered by blists - more mailing lists