[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aBB3ElgEoCF6yYNY@linaro.org>
Date: Tue, 29 Apr 2025 09:52:02 +0300
From: Abel Vesa <abel.vesa@...aro.org>
To: Aleksandrs Vinarskis <alex.vinarskis@...il.com>
Cc: Johan Hovold <johan@...nel.org>, Dmitry Baryshkov <lumag@...nel.org>,
linux-arm-msm@...r.kernel.org, dri-devel@...ts.freedesktop.org,
freedreno@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
dmitry.baryshkov@....qualcomm.com, Rob Clark <robdclark@...il.com>,
Abhinav Kumar <quic_abhinavk@...cinc.com>,
Sean Paul <sean@...rly.run>,
Marijn Suijten <marijn.suijten@...ainline.org>,
David Airlie <airlied@...il.com>, Simona Vetter <simona@...ll.ch>,
laurentiu.tudor1@...l.com
Subject: Re: drm/msm/dp: Introduce link training per-segment for LTTPRs
On 25-04-28 20:23:45, Aleksandrs Vinarskis wrote:
> On Mon, 28 Apr 2025 at 16:17, Abel Vesa <abel.vesa@...aro.org> wrote:
> >
> > The change itself makes sense though and I think makes sense to be marked as a fix.
>
> Just to confirm, you mean to mark as fix only the 1st patch, correct?
> Since it's obvious now that the currently present partial LTTPR
> support did not break anything that used to work.
Well, the way I see it, the LTTPR support is broken on some specific
docks, even if it works in most cases. And since this fix improves
the already working cases and fixes broken ones, yes, add the Fixes tag
to the 1st patch only.
I'd even send that first patch separately to ease the merging, but that's
probably just me.
>
> Thanks,
> Alex
>
Abel
Powered by blists - more mailing lists