From: Abhinav Kumar <quic_abhinavk@quicinc.com>
To: Aleksandrs Vinarskis <alex.vinarskis@gmail.com>,
Dmitry Baryshkov <lumag@kernel.org>,
<linux-arm-msm@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>,
<freedreno@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
<dmitry.baryshkov@oss.qualcomm.com>
Cc: Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
"Marijn Suijten" <marijn.suijten@somainline.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
<laurentiu.tudor1@dell.com>, <abel.vesa@linaro.org>,
<johan@kernel.org>, Johan Hovold <johan+linaro@kernel.org>
Subject: Re: [PATCH v4 1/4] drm/msm/dp: Fix support of LTTPR initialization
Date: Wed, 30 Apr 2025 17:24:40 -0700 [thread overview]
Message-ID: <8a5970fd-8ebb-4ed2-8276-7b5ad4ec2f9f@quicinc.com> (raw)
In-Reply-To: <20250430001330.265970-2-alex.vinarskis@gmail.com>
On 4/29/2025 5:09 PM, Aleksandrs Vinarskis wrote:
> Initialize LTTPR before msm_dp_panel_read_sink_caps, as DPTX shall
> (re)read DPRX caps after LTTPR detection, as required by DP 2.1,
> Section 3.6.7.6.1.
>
Thanks for the patch.
Small correction: this is section 3.6.7.6.1 of DP 2.1a not DP 2.1
> Fixes: 72d0af4accd9 ("drm/msm/dp: Add support for LTTPR handling")
>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> Signed-off-by: Aleksandrs Vinarskis <alex.vinarskis@gmail.com>
> Tested-by: Johan Hovold <johan+linaro@kernel.org>
> Tested-by: Rob Clark <robdclark@gmail.com>
> ---
> drivers/gpu/drm/msm/dp/dp_display.c | 13 +++++++++----
> 1 file changed, 9 insertions(+), 4 deletions(-)
>
No need to resend for this, I can even fix it up while applying,
With that addressed,
Reviewed-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
next prev parent reply other threads:[~2025-05-01 0:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 0:09 [PATCH v4 0/4] drm/msm/dp: Introduce link training per-segment for LTTPRs Aleksandrs Vinarskis
2025-04-30 0:09 ` [PATCH v4 1/4] drm/msm/dp: Fix support of LTTPR initialization Aleksandrs Vinarskis
2025-05-01 0:24 ` Abhinav Kumar [this message]
2025-05-02 17:41 ` Jessica Zhang
2025-05-02 21:54 ` Dmitry Baryshkov
2025-05-02 23:01 ` Jessica Zhang
2025-05-03 3:24 ` Dmitry Baryshkov
2025-04-30 0:09 ` [PATCH v4 2/4] drm/msm/dp: Account for LTTPRs capabilities Aleksandrs Vinarskis
2025-05-01 1:07 ` Abhinav Kumar
2025-04-30 0:09 ` [PATCH v4 3/4] drm/msm/dp: Prepare for link training per-segment for LTTPRs Aleksandrs Vinarskis
2025-05-01 1:20 ` Abhinav Kumar
2025-04-30 0:09 ` [PATCH v4 4/4] drm/msm/dp: Introduce " Aleksandrs Vinarskis
2025-05-01 2:10 ` Abhinav Kumar
2025-05-01 15:56 ` Aleksandrs Vinarskis
2025-05-04 3:02 ` Abhinav Kumar
2025-05-04 22:06 ` Aleksandrs Vinarskis
2025-05-05 14:32 ` Aleksandrs Vinarskis
2025-05-05 23:41 ` Abhinav Kumar
2025-05-07 22:01 ` Aleksandrs Vinarskis
2025-05-07 22:08 ` Abhinav Kumar
2025-05-07 22:22 ` Aleksandrs Vinarskis
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=8a5970fd-8ebb-4ed2-8276-7b5ad4ec2f9f@quicinc.com \
--to=quic_abhinavk@quicinc.com \
--cc=abel.vesa@linaro.org \
--cc=airlied@gmail.com \
--cc=alex.vinarskis@gmail.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=johan+linaro@kernel.org \
--cc=johan@kernel.org \
--cc=laurentiu.tudor1@dell.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
/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
all inboxes | Powered by JetHome®