From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>
Cc: "Nikula, Jani" <jani.nikula@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"tzimmermann@suse.de" <tzimmermann@suse.de>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/fbdev: Implement fb_dirty for intel custom fb helper
Date: Wed, 21 Dec 2022 09:28:00 +0000 [thread overview]
Message-ID: <f0ccd8fc4ac380dd89d7e0bd4cad1dd1a3a918f3.camel@intel.com> (raw)
In-Reply-To: <Y6H3ugZOxZzroO6Q@intel.com>
On Tue, 2022-12-20 at 19:58 +0200, Ville Syrjälä wrote:
> On Tue, Dec 20, 2022 at 07:53:06PM +0200, Ville Syrjälä wrote:
> > On Tue, Nov 29, 2022 at 02:43:02PM +0200, Jouni Högander wrote:
> > > After splitting generic drm_fb_helper into it's own file it's
> > > left to
> > > helper implementation to have fb_dirty function. Currently intel
> > > fb doesn't have it. This is causing problems when PSR is enabled.
> > >
> > > Implement simple fb_dirty callback to deliver notifications to
> > > psr
> > > about updates in fb console.
> >
> > Just found this regression myself after being baffled why the
> > vt console was inoperable right after the driver gets loaded.
> >
> > It's also not just psr, but also fbc that is having issues.
> >
> > Needs a fixes + cc:stable tags.
>
> Actually looks like it didn't make it into 6.1 so I guess
> no cc:stable needed.
Added Fixes tag.
>
> >
> > >
> > > Cc: Thomas Zimmermann <tzimmermann@suse.de>
> > > Cc: Jani Nikula <jani.nikula@intel.com>
> > > Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
> > > ---
> > > drivers/gpu/drm/i915/display/intel_fbdev.c | 9 +++++++++
> > > 1 file changed, 9 insertions(+)
> > >
> > > diff --git a/drivers/gpu/drm/i915/display/intel_fbdev.c
> > > b/drivers/gpu/drm/i915/display/intel_fbdev.c
> > > index 5575d7abdc09..7c7fba3fe69e 100644
> > > --- a/drivers/gpu/drm/i915/display/intel_fbdev.c
> > > +++ b/drivers/gpu/drm/i915/display/intel_fbdev.c
> > > @@ -328,8 +328,17 @@ static int intelfb_create(struct
> > > drm_fb_helper *helper,
> > > return ret;
> > > }
> > >
> > > +static int intelfb_dirty(struct drm_fb_helper *helper, struct
> > > drm_clip_rect *clip)
> > > +{
> >
> > The original thing had some kind of "is this rect actually
> > visible?"
> > check here. Does anyone know why it was there, and if so maybe it
> > should
> > go back to the higher level function so everyone doens't need to
> > add it
> > back in?
I'll guess you mean this one ?:
// snip
/* Call damage handlers only if necessary */
if (!(clip->x1 < clip->x2 && clip->y1 < clip->y2))
return 0;
// snip
I will create separate patch for this.
> >
> > > + if (helper->fb->funcs->dirty)
> > > + return helper->fb->funcs->dirty(helper->fb, NULL,
> > > 0, 0, clip, 1);
> > > +
> > > + return 0;
> > > +}
> > > +
> > > static const struct drm_fb_helper_funcs intel_fb_helper_funcs =
> > > {
> > > .fb_probe = intelfb_create,
> > > + .fb_dirty = intelfb_dirty,
> > > };
> > >
> > > static void intel_fbdev_destroy(struct intel_fbdev *ifbdev)
> > > --
> > > 2.34.1
> >
> > --
> > Ville Syrjälä
> > Intel
>
BR,
Jouni Högander
next prev parent reply other threads:[~2022-12-21 9:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 12:43 [Intel-gfx] [PATCH] drm/i915/fbdev: Implement fb_dirty for intel custom fb helper Jouni Högander
2022-11-29 13:51 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-11-29 17:21 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-12-20 17:53 ` [Intel-gfx] [PATCH] " Ville Syrjälä
2022-12-20 17:58 ` Ville Syrjälä
2022-12-21 9:28 ` Hogander, Jouni [this message]
2022-12-21 10:49 ` Thomas Zimmermann
2022-12-21 11:22 ` Hogander, Jouni
2022-12-21 14:51 ` Ville Syrjälä
2022-12-21 15:08 ` Thomas Zimmermann
2022-12-21 15:22 ` Ville Syrjälä
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=f0ccd8fc4ac380dd89d7e0bd4cad1dd1a3a918f3.camel@intel.com \
--to=jouni.hogander@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=tzimmermann@suse.de \
--cc=ville.syrjala@linux.intel.com \
/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