DisplayPort requires per-segment link training when LTTPR are switched
to non-transparent mode, starting with LTTPR closest to the source.
Only when each segment is trained individually, source can link train
to sink.
Implement per-segment link traning when LTTPR(s) are detected, to
support extern
el.org/all/20250310211039.29843-1-alex.vinars...@gmail.com/
Aleksandrs Vinarskis (4):
drm/msm/dp: Fix support of LTTPR initialization
drm/msm/dp: Account for LTTPRs capabilities
drm/msm/dp: Prepare for link training per-segment for LTTPRs
drm/msm/dp: Introduce link training per-segment for
On Thu, 8 May 2025 at 00:08, Abhinav Kumar wrote:
>
> Hi Alex
>
>
> On 5/7/2025 3:01 PM, Aleksandrs Vinarskis wrote:
> > On Tue, 6 May 2025 at 01:41, Abhinav Kumar
> > wrote:
> >>
> >> Hi Alex
> >>
> >> On 5/4/2025 3:06 PM, Aleksandrs Vinarskis wrote:
> >>> On Sun, 4 May 2025 at 05:02, Abhinav K
Hi Alex
On 5/7/2025 3:01 PM, Aleksandrs Vinarskis wrote:
On Tue, 6 May 2025 at 01:41, Abhinav Kumar wrote:
Hi Alex
On 5/4/2025 3:06 PM, Aleksandrs Vinarskis wrote:
On Sun, 4 May 2025 at 05:02, Abhinav Kumar wrote:
Hi Alex
Thanks for the response.
My updates below. I also had one quest
On Tue, 6 May 2025 at 01:41, Abhinav Kumar wrote:
>
> Hi Alex
>
> On 5/4/2025 3:06 PM, Aleksandrs Vinarskis wrote:
> > On Sun, 4 May 2025 at 05:02, Abhinav Kumar
> > wrote:
> >>
> >> Hi Alex
> >>
> >> Thanks for the response.
> >>
> >> My updates below. I also had one question for Abel below.
>
Hi Alex
On 5/4/2025 3:06 PM, Aleksandrs Vinarskis wrote:
On Sun, 4 May 2025 at 05:02, Abhinav Kumar wrote:
Hi Alex
Thanks for the response.
My updates below. I also had one question for Abel below.
Thanks
Abhinav
On 5/1/2025 8:56 AM, Aleksandrs Vinarskis wrote:
On Thu, 1 May 2025 at 04:
On Mon, 5 May 2025 at 00:06, Aleksandrs Vinarskis
wrote:
>
> On Sun, 4 May 2025 at 05:02, Abhinav Kumar wrote:
> >
> > Hi Alex
> >
> > Thanks for the response.
> >
> > My updates below. I also had one question for Abel below.
> >
> > Thanks
> >
> > Abhinav
> >
> > On 5/1/2025 8:56 AM, Aleksandrs
On Sun, 4 May 2025 at 05:02, Abhinav Kumar wrote:
>
> Hi Alex
>
> Thanks for the response.
>
> My updates below. I also had one question for Abel below.
>
> Thanks
>
> Abhinav
>
> On 5/1/2025 8:56 AM, Aleksandrs Vinarskis wrote:
> > On Thu, 1 May 2025 at 04:11, Abhinav Kumar
> > wrote:
> >>
> >>
Hi Alex
Thanks for the response.
My updates below. I also had one question for Abel below.
Thanks
Abhinav
On 5/1/2025 8:56 AM, Aleksandrs Vinarskis wrote:
On Thu, 1 May 2025 at 04:11, Abhinav Kumar wrote:
On 4/29/2025 5:09 PM, Aleksandrs Vinarskis wrote:
DisplayPort requires per-segmen
On Thu, 1 May 2025 at 04:11, Abhinav Kumar wrote:
>
>
>
> On 4/29/2025 5:09 PM, Aleksandrs Vinarskis wrote:
> > DisplayPort requires per-segment link training when LTTPR are switched
> > to non-transparent mode, starting with LTTPR closest to the source.
> > Only when each segment is trained indiv
On 4/29/2025 5:09 PM, Aleksandrs Vinarskis wrote:
DisplayPort requires per-segment link training when LTTPR are switched
to non-transparent mode, starting with LTTPR closest to the source.
Only when each segment is trained individually, source can link train
to sink.
Implement per-segment lin
DisplayPort requires per-segment link training when LTTPR are switched
to non-transparent mode, starting with LTTPR closest to the source.
Only when each segment is trained individually, source can link train
to sink.
Implement per-segment link traning when LTTPR(s) are detected, to
support extern
ms on Xorg.
- Link to v1:
https://lore.kernel.org/all/20250310211039.29843-1-alex.vinars...@gmail.com/
Aleksandrs Vinarskis (4):
drm/msm/dp: Fix support of LTTPR initialization
drm/msm/dp: Account for LTTPRs capabilities
drm/msm/dp: Prepare for link training per-segment for LTTPRs
drm/msm/dp: I
On Tue, Apr 29, 2025 at 12:57:16PM +0200, Aleksandrs Vinarskis wrote:
> On Tue, 29 Apr 2025 at 10:03, Johan Hovold wrote:
> >
> > On Tue, Apr 29, 2025 at 10:50:55AM +0300, Abel Vesa wrote:
> > > On 25-04-29 09:23:46, Johan Hovold wrote:
> > > > On Mon, Apr 28, 2025 at 05:17:21PM +0300, Abel Vesa w
On Tue, Apr 29, 2025 at 12:57:16PM +0200, Aleksandrs Vinarskis wrote:
> On Tue, 29 Apr 2025 at 10:03, Johan Hovold wrote:
> > On Tue, Apr 29, 2025 at 10:50:55AM +0300, Abel Vesa wrote:
> > > On 25-04-29 09:23:46, Johan Hovold wrote:
> > > > But this is the crux; does any off-board LTTPRs in trans
On Tue, 29 Apr 2025 at 10:03, Johan Hovold wrote:
>
> On Tue, Apr 29, 2025 at 10:50:55AM +0300, Abel Vesa wrote:
> > On 25-04-29 09:23:46, Johan Hovold wrote:
> > > On Mon, Apr 28, 2025 at 05:17:21PM +0300, Abel Vesa wrote:
> > > > On 25-04-28 14:47:04, Johan Hovold wrote:
> > > > > On Mon, Apr 28
On Tue, Apr 29, 2025 at 10:50:55AM +0300, Abel Vesa wrote:
> On 25-04-29 09:23:46, Johan Hovold wrote:
> > On Mon, Apr 28, 2025 at 05:17:21PM +0300, Abel Vesa wrote:
> > > On 25-04-28 14:47:04, Johan Hovold wrote:
> > > > On Mon, Apr 28, 2025 at 11:06:39AM +0200, Aleksandrs Vinarskis wrote:
> > > >
On 25-04-29 09:23:46, Johan Hovold wrote:
> On Mon, Apr 28, 2025 at 05:17:21PM +0300, Abel Vesa wrote:
> > On 25-04-28 14:47:04, Johan Hovold wrote:
> > > On Mon, Apr 28, 2025 at 11:06:39AM +0200, Aleksandrs Vinarskis wrote:
> > > > On Mon, 28 Apr 2025 at 09:45, Johan Hovold wrote:
> > > > > On Th
On Tue, 29 Apr 2025 at 08:52, Abel Vesa wrote:
>
> On 25-04-28 20:23:45, Aleksandrs Vinarskis wrote:
> > On Mon, 28 Apr 2025 at 16:17, Abel Vesa 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
On Mon, Apr 28, 2025 at 05:17:21PM +0300, Abel Vesa wrote:
> On 25-04-28 14:47:04, Johan Hovold wrote:
> > On Mon, Apr 28, 2025 at 11:06:39AM +0200, Aleksandrs Vinarskis wrote:
> > > On Mon, 28 Apr 2025 at 09:45, Johan Hovold wrote:
> > > > On Thu, Apr 17, 2025 at 04:10:31AM +0200, Aleksandrs Vina
On 25-04-28 20:23:45, Aleksandrs Vinarskis wrote:
> On Mon, 28 Apr 2025 at 16:17, Abel Vesa 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 th
On Wed, Apr 16, 2025 at 7:13 PM Aleksandrs Vinarskis
wrote:
>
> DisplayPort requires per-segment link training when LTTPR are switched
> to non-transparent mode, starting with LTTPR closest to the source.
> Only when each segment is trained individually, source can link train
> to sink.
>
> Implem
On Mon, 28 Apr 2025 at 16:17, Abel Vesa wrote:
>
> On 25-04-28 14:47:04, Johan Hovold wrote:
> > On Mon, Apr 28, 2025 at 11:06:39AM +0200, Aleksandrs Vinarskis wrote:
> > > On Mon, 28 Apr 2025 at 09:45, Johan Hovold wrote:
> > > > On Thu, Apr 17, 2025 at 04:10:31AM +0200, Aleksandrs Vinarskis wro
On 25-04-28 14:47:04, Johan Hovold wrote:
> On Mon, Apr 28, 2025 at 11:06:39AM +0200, Aleksandrs Vinarskis wrote:
> > On Mon, 28 Apr 2025 at 09:45, Johan Hovold wrote:
> > > On Thu, Apr 17, 2025 at 04:10:31AM +0200, Aleksandrs Vinarskis wrote:
> > > > Recently added Initial LTTPR support in msm/dp
On Mon, Apr 28, 2025 at 11:06:39AM +0200, Aleksandrs Vinarskis wrote:
> On Mon, 28 Apr 2025 at 09:45, Johan Hovold wrote:
> > On Thu, Apr 17, 2025 at 04:10:31AM +0200, Aleksandrs Vinarskis wrote:
> > > Recently added Initial LTTPR support in msm/dp has configured LTTPR(s)
> > > to non-transparent
DP altmode still
> works on my X13s and T14s (while not using any docks):
>
> Tested-by: Johan Hovold
Thanks,
Alex
>
> > Aleksandrs Vinarskis (4):
> > drm/msm/dp: Fix support of LTTPR initialization
> > drm/msm/dp: Account for LTTPRs capabilities
> > drm/msm/dp: Prepare for link training per-segment for LTTPRs
> > drm/msm/dp: Introduce link training per-segment for LTTPRs
>
> Johan
on my X13s and T14s (while not using any docks):
Tested-by: Johan Hovold
> Aleksandrs Vinarskis (4):
> drm/msm/dp: Fix support of LTTPR initialization
> drm/msm/dp: Account for LTTPRs capabilities
> drm/msm/dp: Prepare for link training per-segment for LTTPRs
> drm/msm/dp: Introduce link training per-segment for LTTPRs
Johan
On Thu, Apr 17, 2025 at 04:10:35AM +0200, Aleksandrs Vinarskis wrote:
> DisplayPort requires per-segment link training when LTTPR are switched
> to non-transparent mode, starting with LTTPR closest to the source.
> Only when each segment is trained individually, source can link train
> to sink.
>
2:
> > https://lore.kernel.org/all/20250311234109.136510-1-alex.vinars...@gmail.com/
> >
> > Changes in v2:
> > - Picked up Abel's R-b tags
> > - Fixed typo as per Abel, fixed readability as per Johan
> > - Updated cover and commit message on mailink iss
34109.136510-1-alex.vinars...@gmail.com/
>
> Changes in v2:
> - Picked up Abel's R-b tags
> - Fixed typo as per Abel, fixed readability as per Johan
> - Updated cover and commit message on mailink issue which appears to be
> specific to Gnome+Wayland. No problems on Xorg.
> - L
310211039.29843-1-alex.vinars...@gmail.com/
Aleksandrs Vinarskis (4):
drm/msm/dp: Fix support of LTTPR initialization
drm/msm/dp: Account for LTTPRs capabilities
drm/msm/dp: Prepare for link training per-segment for LTTPRs
drm/msm/dp: Introduce link training per-segment
DisplayPort requires per-segment link training when LTTPR are switched
to non-transparent mode, starting with LTTPR closest to the source.
Only when each segment is trained individually, source can link train
to sink.
Implement per-segment link traning when LTTPR(s) are detected, to
support extern
On 09/04/2025 01:29, Aleksandrs Vinarskis wrote:
On Tue, 1 Apr 2025 at 02:55, Dmitry Baryshkov
wrote:
On Wed, Mar 12, 2025 at 12:38:04AM +0100, Aleksandrs Vinarskis wrote:
DisplayPort requires per-segment link training when LTTPR are switched
to non-transparent mode, starting with LTTPR close
On Tue, 1 Apr 2025 at 02:55, Dmitry Baryshkov
wrote:
>
> On Wed, Mar 12, 2025 at 12:38:04AM +0100, Aleksandrs Vinarskis wrote:
> > DisplayPort requires per-segment link training when LTTPR are switched
> > to non-transparent mode, starting with LTTPR closest to the source.
> > Only when each segme
On Wed, Mar 12, 2025 at 12:38:04AM +0100, Aleksandrs Vinarskis wrote:
> DisplayPort requires per-segment link training when LTTPR are switched
> to non-transparent mode, starting with LTTPR closest to the source.
> Only when each segment is trained individually, source can link train
> to sink.
>
On 3/12/25 22:16, Stefan Schmidt wrote:
Hello Aleksandrs,
On Wed, 12 Mar 2025 at 00:41, Aleksandrs Vinarskis
wrote:
Recently added Initial LTTPR support in msm/dp has configured LTTPR(s)
to non-transparent mode to enable video output on X1E-based devices
that come with LTTPR on the motherb
> -Original Message-
> From: Aleksandrs Vinarskis
> Sent: Wednesday, March 12, 2025 1:38 AM
> Subject: [PATCH v2 0/2] drm/msm/dp: Introduce link training per-segment for
> LTTPRs
>
> Recently added Initial LTTPR support in msm/dp has configured LTTPR(s) to
>
Hello Aleksandrs,
On Wed, 12 Mar 2025 at 00:41, Aleksandrs Vinarskis
wrote:
>
> Recently added Initial LTTPR support in msm/dp has configured LTTPR(s)
> to non-transparent mode to enable video output on X1E-based devices
> that come with LTTPR on the motherboards. However, video would not work
>
DisplayPort requires per-segment link training when LTTPR are switched
to non-transparent mode, starting with LTTPR closest to the source.
Only when each segment is trained individually, source can link train
to sink.
Implement per-segment link traning when LTTPR(s) are detected, to
support extern
g.
- Link to v1:
https://lore.kernel.org/all/20250310211039.29843-1-alex.vinars...@gmail.com/
---
Aleksandrs Vinarskis (2):
drm/msm/dp: Fix support of LTTPR handling
drm/msm/dp: Introduce link training per-segment for LTTPRs
drivers/gpu/drm/msm/dp/dp_ctrl.c| 137 +++---
On 25-03-10 22:05:52, Aleksandrs Vinarskis wrote:
> DisplayPort requires per-segment link training when LTTPR are switched
> to non-transparent mode, starting with LTTPR closest to the source.
> Only when each segment is trained individually, source can link train
> to sink.
>
> Implement per-segm
Hi Aleksandrs,
Just a drive-by comment.
On Mon, Mar 10, 2025 at 10:05:52PM +0100, Aleksandrs Vinarskis wrote:
> @@ -1084,10 +1091,13 @@ static int msm_dp_ctrl_update_vx_px(struct
> msm_dp_ctrl_private *ctrl)
> }
>
> static bool msm_dp_ctrl_train_pattern_set(struct msm_dp_ctrl_private *ctrl,
DisplayPort requires per-segment link training when LTTPR are switched
to non-transparent mode, starting with LTTPR closest to the source.
Only when each segment is trained individually, source can link train
to sink.
Implement per-segment link traning when LTTPR(s) are detected, to
support extern
driver.
[1] https://lore.kernel.org/all/20250226231436.16138-2-alex.vinars...@gmail.com/
Aleksandrs Vinarskis (2):
drm/msm/dp: Fix support of LTTPR handling
drm/msm/dp: Introduce link training per-segment for LTTPRs
drivers/gpu/drm/msm/dp/dp_ctrl.c| 136 +++-
drivers/gpu/d
44 matches
Mail list logo
