Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Xiangxu Yin <quic_xiangxuy@quicinc.com>
To: Abhinav Kumar <quic_abhinavk@quicinc.com>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
	"Marijn Suijten" <marijn.suijten@somainline.org>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	Rob Herring <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	"Kuogee Hsieh" <quic_khsieh@quicinc.com>,
	Vinod Koul <vkoul@kernel.org>,
	"Kishon Vijay Abraham I" <kishon@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>, <quic_lliu6@quicinc.com>,
	<quic_fangez@quicinc.com>, <linux-arm-msm@vger.kernel.org>,
	<dri-devel@lists.freedesktop.org>,
	<freedreno@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-phy@lists.infradead.org>,
	<linux-gpio@vger.kernel.org>
Subject: Re: [PATCH 6/8] drm/msm/dp: Add maximum width limitation for modes
Date: Mon, 9 Dec 2024 09:57:33 +0800	[thread overview]
Message-ID: <5cdd9f7a-2c28-4ac2-a4da-304d25efbca3@quicinc.com> (raw)
In-Reply-To: <3e7660b3-934a-4b11-82a3-48137d63ea5d@quicinc.com>



On 12/7/2024 4:13 AM, Abhinav Kumar wrote:
> 
> 
> On 12/3/2024 5:58 AM, Dmitry Baryshkov wrote:
>> On Tue, Dec 03, 2024 at 03:41:53PM +0800, Xiangxu Yin wrote:
>>>
>>>
>>> On 12/2/2024 5:32 PM, Dmitry Baryshkov wrote:
>>>> On Mon, 2 Dec 2024 at 11:05, Xiangxu Yin <quic_xiangxuy@quicinc.com> wrote:
>>>>>
>>>>>
>>>>>
>>>>> On 11/29/2024 9:52 PM, Dmitry Baryshkov wrote:
>>>>>> On Fri, 29 Nov 2024 at 09:59, Xiangxu Yin <quic_xiangxuy@quicinc.com> wrote:
>>>>>>>
>>>>>>> Introduce a maximum width constraint for modes during validation. This
>>>>>>> ensures that the modes are filtered based on hardware capabilities,
>>>>>>> specifically addressing the line buffer limitations of individual pipes.
>>>>>>
>>>>>> This doesn't describe, why this is necessary. What does "buffer
>>>>>> limitations of individual pipes" mean?
>>>>>> If the platforms have hw capabilities like being unable to support 8k
>>>>>> or 10k, it should go to platform data
>>>>>>
>>>>> It's SSPP line buffer limitation for this platform and only support to 2160 mode width.
>>>>> Then, shall I add max_width config to struct msm_dp_desc in next patch? for other platform will set defualt value to ‘DP_MAX_WIDTH 7680'
>>>>
>>>> SSPP line buffer limitations are to be handled in the DPU driver. The
>>>> DP driver shouldn't care about those.
>>>>
>>> Ok, Will drop this part in next patch.
>>
>> If you drop it, what will be left from the patch itself?
>>
> 
> Yes agree with Dmitry, max_width is really not a DP related terminology.
> 
> This patch should be dropped.
> 
> So there were two issues, overall in this series causing this patch:
> 
> 1) In https://patchwork.freedesktop.org/patch/625822/, instead of using VIG_SDM845_MASK, we should be using VIG_SDM845_MASK_SDMA. Without that even 2k will not work, will leave a comment there.
> 
> 2) 4k will still fail. I dont think we can even support 4k on QCS615 but the modes should be filtered out because there is no 3dmux.
> 
> I have submitted https://patchwork.freedesktop.org/patch/627694/ to address this.
> 
> Xiangxu, please let me know if that works for you.
> 
> Thanks
> 
> Abhinav
Thanks for your patchsets,
After apply patch 625822 & 627694,mode filter works correctly on QCS615 platform with both 4k and 2k monitor.
work>>>>>>>
>>>>>>> Signed-off-by: Xiangxu Yin <quic_xiangxuy@quicinc.com>
>>>>>>> ---
>>>>>>>   drivers/gpu/drm/msm/dp/dp_display.c |  3 +++
>>>>>>>   drivers/gpu/drm/msm/dp/dp_display.h |  1 +
>>>>>>>   drivers/gpu/drm/msm/dp/dp_panel.c   | 13 +++++++++++++
>>>>>>>   drivers/gpu/drm/msm/dp/dp_panel.h   |  1 +
>>>>>>>   4 files changed, 18 insertions(+)
>>>>
>>>>
>>>
>>


  reply	other threads:[~2024-12-09  1:58 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-29  7:57 [PATCH 0/8] Add DisplayPort support for QCS615 platform Xiangxu Yin
2024-11-29  7:57 ` [PATCH 1/8] dt-bindings: display/msm: Document DP on QCS615 Xiangxu Yin
2024-11-29  8:11   ` Krzysztof Kozlowski
2024-11-29  7:57 ` [PATCH 2/8] dt-bindings: phy: qcom,msm8998-qmp-usb3-phy: Add DP support for QCS615 Xiangxu Yin
2024-11-29  8:14   ` Krzysztof Kozlowski
2024-11-29  7:57 ` [PATCH 3/8] phy: qcom: qmp-usbc: Add DP phy mode support on QCS615 Xiangxu Yin
2024-11-29  8:18   ` Krzysztof Kozlowski
2024-12-02 10:31     ` Xiangxu Yin
2024-12-02 15:48       ` Dmitry Baryshkov
2024-11-29 12:12   ` kernel test robot
2024-11-29 14:33   ` Dmitry Baryshkov
2024-12-05 13:26     ` Xiangxu Yin
2024-12-05 18:31       ` Dmitry Baryshkov
2024-12-10 15:09         ` Dmitry Baryshkov
2024-12-11  0:46           ` Xiangxu Yin
2024-12-11  9:46             ` Dmitry Baryshkov
2024-12-11 12:50               ` Xiangxu Yin
2024-12-11 19:15                 ` Dmitry Baryshkov
2024-12-18 12:55                   ` Xiangxu Yin
2024-12-19 21:38                     ` Dmitry Baryshkov
2024-12-20  0:01                     ` Dmitry Baryshkov
2025-03-05 10:20                       ` Xiangxu Yin
2025-03-05 21:25                         ` Dmitry Baryshkov
2025-03-21 10:17                           ` Xiangxu Yin
2025-03-21 12:19                             ` Dmitry Baryshkov
2024-11-29  7:57 ` [PATCH 4/8] drm/msm/dp: Add DisplayPort support for QCS615 Xiangxu Yin
2024-11-29 13:54   ` Dmitry Baryshkov
2024-11-29  7:57 ` [PATCH 5/8] drm/msm/dp: Add support for lane mapping configuration Xiangxu Yin
2024-11-29 13:50   ` Dmitry Baryshkov
2024-12-02  8:40     ` Xiangxu Yin
2024-12-02 10:46       ` Dmitry Baryshkov
2024-12-05 11:28         ` Xiangxu Yin
2024-12-05 11:40           ` Dmitry Baryshkov
2024-12-19 10:36             ` Xiangxu Yin
2024-12-19 21:45               ` Dmitry Baryshkov
2025-03-05 10:16                 ` Xiangxu Yin
2025-03-05 21:14                   ` Dmitry Baryshkov
2025-05-19  8:20                     ` Xiangxu Yin
2025-05-19  9:58                       ` Dmitry Baryshkov
2024-11-29  7:57 ` [PATCH 6/8] drm/msm/dp: Add maximum width limitation for modes Xiangxu Yin
2024-11-29 13:52   ` Dmitry Baryshkov
2024-12-02  9:05     ` Xiangxu Yin
2024-12-02  9:32       ` Dmitry Baryshkov
2024-12-03  7:41         ` Xiangxu Yin
2024-12-03 13:58           ` Dmitry Baryshkov
2024-12-06 20:13             ` Abhinav Kumar
2024-12-09  1:57               ` Xiangxu Yin [this message]
2024-12-09 20:18                 ` Abhinav Kumar
2024-11-29  7:57 ` [PATCH 7/8] drm/msm/dp: Retry Link Training 2 with lower pattern Xiangxu Yin
2024-11-29 13:53   ` Dmitry Baryshkov
2024-12-03  8:13     ` Xiangxu Yin
2024-12-03 14:07       ` Dmitry Baryshkov
2025-05-27 20:49         ` Konrad Dybcio
2025-07-09  9:16           ` Xiangxu Yin
2025-07-19  9:43             ` Dmitry Baryshkov
2025-07-21  4:18               ` Xiangxu Yin
2024-11-29  7:57 ` [PATCH 8/8] drm/msm/dp: Support external GPIO HPD with 3rd pinctrl chip Xiangxu Yin
2024-11-29  8:21   ` Krzysztof Kozlowski
2024-11-29 13:45   ` Dmitry Baryshkov
2024-11-29 13:54   ` neil.armstrong

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=5cdd9f7a-2c28-4ac2-a4da-304d25efbca3@quicinc.com \
    --to=quic_xiangxuy@quicinc.com \
    --cc=airlied@gmail.com \
    --cc=brgl@bgdev.pl \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=kishon@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=marijn.suijten@somainline.org \
    --cc=mripard@kernel.org \
    --cc=quic_abhinavk@quicinc.com \
    --cc=quic_fangez@quicinc.com \
    --cc=quic_khsieh@quicinc.com \
    --cc=quic_lliu6@quicinc.com \
    --cc=robdclark@gmail.com \
    --cc=robh@kernel.org \
    --cc=sean@poorly.run \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    --cc=vkoul@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