From: Teguh Sobirin <teguh@sobir.in>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Rob Clark <robin.clark@oss.qualcomm.com>,
Dmitry Baryshkov <lumag@kernel.org>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
Jessica Zhang <jesszhan0024@gmail.com>,
Sean Paul <sean@poorly.run>,
Marijn Suijten <marijn.suijten@somainline.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"freedreno@lists.freedesktop.org"
<freedreno@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/msm/dpu: Set vsync source irrespective of mdp top support
Date: Mon, 17 Nov 2025 07:55:08 +0000 [thread overview]
Message-ID: <TYUPR06MB60990F649387CA675ADF2813DDC9A@TYUPR06MB6099.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <w3fffuitwki7imcpc75m2e5kv5fpg5nj6udpxytm55kqa4mkud@rkl2ywspwm5y>
>
> On 14 Nov 2025, at 12.10, Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> wrote:
>
> On Tue, Oct 28, 2025 at 07:02:28PM +0200, Dmitry Baryshkov wrote:
>>> On Tue, Oct 28, 2025 at 08:36:35PM +0800, Teguh Sobirin wrote:
>>> Move the loop over phys_encs outside the
>>> hw_mdptop->ops.setup_vsync_source block.
>>> This way, vsync_sel() is called for each interface.
>>>
>>> This change ensures TE vsync selection works
>>> even if setup_vsync_source is not implemented.
>>
>> Please see Documentation/processs/submitting-patches.rst. Don't describe
>> the change and pleasw wrap the commit message on 72-75 chars boundary.
>>
>> I can suggest something like this:
>>
>> Since DPU 5.x the vsync source TE setup is split between MDP TOP and
>> INTF blocks. Currently all code to setup vsync_source is only exectued
>> if MDP TOP implements the setup_vsync_source() callback. However on
>> DPU >= 8.x this callback is not implemented, making DPU driver skip all
>> vsync setup. Move the INTF part out of this condition, letting DPU
>> driver to setup TE vsync selection on all new DPU devices.
>>
>> The patch itself looks good to me.
>
>
> Teguh, any updates on the patch?
>
> --
> With best wishes
> Dmitry
I will send a new one with corrected commit message
Regards,
Teguh.
prev parent reply other threads:[~2025-11-17 7:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 12:36 Teguh Sobirin
2025-10-28 17:02 ` Dmitry Baryshkov
2025-11-14 4:10 ` Dmitry Baryshkov
2025-11-17 7:55 ` Teguh Sobirin [this message]
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=TYUPR06MB60990F649387CA675ADF2813DDC9A@TYUPR06MB6099.apcprd06.prod.outlook.com \
--to=teguh@sobir.in \
--cc=abhinav.kumar@linux.dev \
--cc=airlied@gmail.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jesszhan0024@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=robin.clark@oss.qualcomm.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®