Re: (subset) [PATCH v2] drm/msm/dp: account for widebus and yuv420 during mode validation

2025-02-17 Thread Abhinav Kumar
On Thu, 06 Feb 2025 11:46:36 -0800, Abhinav Kumar wrote: > Widebus allows the DP controller to operate in 2 pixel per clock mode. > The mode validation logic validates the mode->clock against the max > DP pixel clock. However the max DP pixel clock limit assumes widebus > is already enabled. Adju

Re: [PATCH v2] drm/msm/dp: account for widebus and yuv420 during mode validation

2025-02-09 Thread Dale Whinham
On 06/02/2025 19:46, Abhinav Kumar wrote: Widebus allows the DP controller to operate in 2 pixel per clock mode. The mode validation logic validates the mode->clock against the max DP pixel clock. However the max DP pixel clock limit assumes widebus is already enabled. Adjust the mode validation

Re: [PATCH v2] drm/msm/dp: account for widebus and yuv420 during mode validation

2025-02-06 Thread Dmitry Baryshkov
On Thu, Feb 06, 2025 at 11:46:36AM -0800, Abhinav Kumar wrote: > Widebus allows the DP controller to operate in 2 pixel per clock mode. > The mode validation logic validates the mode->clock against the max > DP pixel clock. However the max DP pixel clock limit assumes widebus > is already enabled.

[PATCH v2] drm/msm/dp: account for widebus and yuv420 during mode validation

2025-02-06 Thread Abhinav Kumar
Widebus allows the DP controller to operate in 2 pixel per clock mode. The mode validation logic validates the mode->clock against the max DP pixel clock. However the max DP pixel clock limit assumes widebus is already enabled. Adjust the mode validation logic to only compare the adjusted pixel clo