From: Nam Cao <namcaov@gmail.com>
To: ChanSoo Shin <csshin9928@gmail.com>, andy@kernel.org
Cc: gregkh@linuxfoundation.org, dri-devel@lists.freedesktop.org,
linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev,
ChanSoo Shin <csshin9928@gmail.com>
Subject: Re: [PATCH v5] fbtft: limit dirty rows based on damage range
Date: Fri, 06 Feb 2026 01:04:45 +0100 [thread overview]
Message-ID: <87y0l668ki.fsf@yellow.woof> (raw)
In-Reply-To: <20260128203938.962414-1-csshin9928@gmail.com>
Hi ChanSoo,
ChanSoo Shin <csshin9928@gmail.com> writes:
> Instead of marking the entire display as dirty, calculate the start
> and end rows based on the damage offset and length and only mark the
> affected rows dirty. This reduces unnecessary full framebuffer updates
> for partial writes.
>
> Signed-off-by: ChanSoo Shin <csshin9928@gmail.com>
This looks useful and I prefer to see it applied. I understand lack of
testing is the main obstacle. Are you still trying to get it merged? If
not, I can take over.
Nam
next prev parent reply other threads:[~2026-02-06 0:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 20:39 [PATCH v5] fbtft: limit dirty rows based on damage range ChanSoo Shin
2026-01-28 22:35 ` Andy Shevchenko
2026-01-29 6:29 ` Dan Carpenter
2026-01-29 10:59 ` Andy Shevchenko
2026-02-06 0:04 ` Nam Cao [this message]
2026-02-06 10:36 ` Andy Shevchenko
2026-02-06 10:51 ` Nam Cao
2026-02-06 11:35 ` Andy Shevchenko
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=87y0l668ki.fsf@yellow.woof \
--to=namcaov@gmail.com \
--cc=andy@kernel.org \
--cc=csshin9928@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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