From: Philipp Zabel <p.zabel@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>, barebox@lists.infradead.org
Subject: Re: [PATCH 1/3] video: fb: add optional damage tracking
Date: Wed, 05 Apr 2023 14:26:45 +0200 [thread overview]
Message-ID: <013b899a6c8647489b3aa7c2b344c2d08cd6d36d.camel@pengutronix.de> (raw)
In-Reply-To: <7a08e414-95d1-0d81-64b4-9772ceb6f680@pengutronix.de>
On Di, 2023-04-04 at 14:24 +0200, Ahmad Fatoum wrote:
> On 03.04.23 14:18, Philipp Zabel wrote:
> > Add an optional fb_damage operation that drivers may use to accumulate
> > damage on the framebuffer until fb_flush is called. The accumulated
> > damage can be used to support partial updates for displays with an
> > integrated framebuffer.
> >
> > Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> > ---
> > drivers/video/fb.c | 6 ++++++
> > include/fb.h | 9 +++++++++
> > 2 files changed, 15 insertions(+)
> >
> > diff --git a/drivers/video/fb.c b/drivers/video/fb.c
> > index 44754065e7d9..6f412d62c434 100644
> > --- a/drivers/video/fb.c
> > +++ b/drivers/video/fb.c
> > @@ -43,6 +43,12 @@ static int fb_close(struct cdev *cdev)
> > return 0;
> > }
> >
> >
> > +void fb_damage(struct fb_info *info, struct fb_rect *rect)
> > +{
> > + if (info->fbops->fb_damage)
> > + info->fbops->fb_damage(info, rect);
> > +}
> > +
> > static int fb_op_flush(struct cdev *cdev)
> > {
> > struct fb_info *info = cdev->priv;
> > diff --git a/include/fb.h b/include/fb.h
> > index 15bb74b99576..4e3eb611db48 100644
> > --- a/include/fb.h
> > +++ b/include/fb.h
> > @@ -80,6 +80,13 @@ struct fb_bitfield {
> >
> >
> > struct fb_info;
> >
> >
> > +struct fb_rect {
> > + u32 x1;
> > + u32 y1;
> > + u32 x2;
> > + u32 y2;
> > +};
> > +
> > struct fb_ops {
> > /* set color register */
> > int (*fb_setcolreg)(unsigned regno, unsigned red, unsigned green,
> > @@ -87,6 +94,7 @@ struct fb_ops {
> > void (*fb_enable)(struct fb_info *info);
> > void (*fb_disable)(struct fb_info *info);
> > int (*fb_activate_var)(struct fb_info *info);
> > + void (*fb_damage)(struct fb_info *info, struct fb_rect *rect);
>
> const struct fb_rect * ?
Yes, changed to const in v2.
regards
Philipp
prev parent reply other threads:[~2023-04-05 12:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 12:18 Philipp Zabel
2023-04-03 12:18 ` [PATCH 2/3] video: fbconsole: " Philipp Zabel
2023-04-05 11:13 ` Sascha Hauer
2023-04-05 12:27 ` Philipp Zabel
2023-04-03 12:18 ` [PATCH 3/3] video: mipi_dbi: add damage tracking and partial updates Philipp Zabel
2023-04-04 12:24 ` [PATCH 1/3] video: fb: add optional damage tracking Ahmad Fatoum
2023-04-05 12:26 ` Philipp Zabel [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=013b899a6c8647489b3aa7c2b344c2d08cd6d36d.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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