On Wed, Jan 28, 2026 at 05:57:20PM +0900, Waffle0823 wrote: > Instead of marking the entire display as dirty, calculate > start_row and end_row based on off/len and mark only those rows. > This improves performance for partial framebuffer updates. > > Signed-off-by: Waffle0283 [email protected] > --- > drivers/staging/fbtft/fbtft-core.c | 7 +++++-- > 1 file changed, 5 insertions(+), 2 deletions(-) > > diff --git a/drivers/staging/fbtft/fbtft-core.c > b/drivers/staging/fbtft/fbtft-core.c > index 8a5ccc8ae0a1..0fbdfdaaa94d 100644 > --- a/drivers/staging/fbtft/fbtft-core.c > +++ b/drivers/staging/fbtft/fbtft-core.c > @@ -415,8 +415,11 @@ static void fbtft_ops_damage_range(struct fb_info *info, > off_t off, size_t len) > { > struct fbtft_par *par = info->par; > > - /* TODO: only mark changed area update all for now */ > - par->fbtftops.mkdirty(info, -1, 0); > + __u32 width = info->var.xres; > + __u32 start_row = off / width; > + __u32 end_row = (off + len - 1) / width; > + > + par->fbtftops.mkdirty(info, start_row, end_row); > } > > static void fbtft_ops_damage_area(struct fb_info *info, u32 x, u32 y, u32 > width, u32 height) > -- > 2.52.0 >
Hi, This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him a patch that has triggered this response. He used to manually respond to these common problems, but in order to save his sanity (he kept writing the same thing over and over, yet to different people), I was created. Hopefully you will not take offence and will fix the problem in your patch and resubmit it so that it can be accepted into the Linux kernel tree. You are receiving this message because of the following common error(s) as indicated below: - It looks like you did not use your "real" name for the patch on either the Signed-off-by: line, or the From: line (both of which have to match). Please read the kernel file, Documentation/process/submitting-patches.rst for how to do this correctly. If you wish to discuss this problem further, or you have questions about how to resolve this issue, please feel free to respond to this email and Greg will reply once he has dug out from the pending patches received from other developers. thanks, greg k-h's patch email bot
