From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Zhang Jiaxi <Z1529105815@outlook.com>,
Rob Clark <robin.clark@oss.qualcomm.com>,
Dmitry Baryshkov <lumag@kernel.org>
Cc: 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: [RFC PATCH 0/3] drm/msm: correct DSC RGB and command-mode vblank handling
Date: Mon, 12 Oct 2026 09:00:58 +0200 [thread overview]
Message-ID: <6e67b0b2-8bae-4568-a276-56f9db360b80@oss.qualcomm.com> (raw)
In-Reply-To: <SY5PR01MB1060041363FC41A7F40DF59DBA1932@SY5PR01MB10600.ausprd01.prod.outlook.com>
On 10/9/26 12:34 AM, Zhang Jiaxi wrote:
> These three independent corrections preserve current target APIs:
> select the existing RGB DSC 1.2 RC table only for version 1.2 and reject
> native subsampling in a forced-RGB path; retain the commit's vblank reference
> until completion delivers its page-flip event; and reject video-porch
> scanout-position conversion for a command-mode tear-check counter.
>
> Command mode initializes that counter at vdisplay, puts RD_PTR at
> vdisplay+1 and can wrap at twice vtotal. This is not the video raster used
> by the shared timestamp conversion. Returning false only marks that
> accurate scanout-derived timestamp unavailable; TE IRQ/counting and the
> current off-delay policy remain in place. No always-on IRQ policy is added.
> The completion callback consumes the current count/time and does not wait
> for another TE interrupt.
[...]
You sent a number of patches with broken threading, please switch to
using the b4 tool - https://b4.docs.kernel.org/en/latest/
Konrad
next prev parent reply other threads:[~2026-10-12 7:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 22:34 Zhang Jiaxi
2026-10-12 7:00 ` Konrad Dybcio [this message]
2026-10-12 18:44 ` Zhang Jiaxi
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=6e67b0b2-8bae-4568-a276-56f9db360b80@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=Z1529105815@outlook.com \
--cc=abhinav.kumar@linux.dev \
--cc=airlied@gmail.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®