From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/4] drm/i915: Intel-specific primary plane handling (v6)
Date: Thu, 15 May 2014 20:00:48 +0300 [thread overview]
Message-ID: <20140515170048.GG27580@intel.com> (raw)
In-Reply-To: <20140515163755.GD23405@intel.com>
On Thu, May 15, 2014 at 09:37:55AM -0700, Matt Roper wrote:
> On Thu, May 15, 2014 at 06:52:28PM +0300, Ville Syrjälä wrote:
> ...
> >
> > > + };
> > > + bool visible;
> > > + int ret;
> > > +
> > > + ret = drm_primary_helper_check_update(plane, crtc, fb,
> > > + &src, &dest, &clip,
> > > + DRM_PLANE_HELPER_NO_SCALING,
> > > + DRM_PLANE_HELPER_NO_SCALING,
> > > + false, true, &visible);
> > > + if (ret)
> > > + return ret;
> > > +
> > > + if (!visible)
> > > + return intel_primary_plane_disable(plane);
> >
> > Here we unpin the old fb...
> >
> > > +
> > > + /*
> > > + * If the CRTC isn't enabled, we're just pinning the framebuffer,
> > > + * updating the fb pointer, and returning without touching the
> > > + * hardware. This allows us to later do a drmModeSetCrtc with fb=-1 to
> > > + * turn on the display with all planes setup as desired.
> > > + */
> > > + if (!crtc->enabled)
> > > + /* Pin and return without programming hardware */
> > > + return intel_pin_and_fence_fb_obj(dev,
> > > + to_intel_framebuffer(fb)->obj,
> > > + NULL);
> >
> > ...but here we just pin the new fb and leave the old also pinned?
> >
> > Something's a bit fishy here. Also a non-enabled crtc but visible primary
> > plane doesn't seem to make sense. We also need to remember that set_base
> > will always unpin the old_fb. So if something can result in set_base
> > being called w/ old_fb!=NULL when it's not pinned, we'll be in deep
> > doodoo.
>
> Right, I guess we need to unpin the old fb, if any, here as well in case
> they perform several setplane() calls while the crtc is disabled.
>
> Eventually the crtc will get reenabled by a drmModeSetCrtc call. If we
> do setcrtc(fb = -1), then it should keep whatever fb we've already
> pinned via the setplane. If they provide a new fb, then the pinning
> we're doing here will get unpinned by the set_base that gets called.
>
> I don't see a way that you can hit set_base with an unpinned
> old_fb!=NULL (since the disable plane case farther up also clears
> primary->fb).
But it doesn't.
>
>
> Matt
>
> >
> > > +
> > > + intel_crtc_wait_for_pending_flips(crtc);
> > > + ret = intel_pipe_set_base(crtc, src.x1, src.y1, fb);
> > > + if (ret)
> > > + return ret;
> > > +
> > > + if (!intel_crtc->primary_enabled)
> > > + intel_enable_primary_hw_plane(dev_priv, intel_crtc->plane,
> > > + intel_crtc->pipe);
> > > +
> > > + return 0;
> > > +}
> > > +
> > > +static void intel_primary_plane_destroy(struct drm_plane *plane)
> > > +{
> > > + struct intel_plane *intel_plane = to_intel_plane(plane);
> > > + drm_plane_cleanup(plane);
> > > + kfree(intel_plane);
> > > +}
> > > +
> > > +static const struct drm_plane_funcs intel_primary_plane_funcs = {
> > > + .update_plane = intel_primary_plane_setplane,
> > > + .disable_plane = intel_primary_plane_disable,
> > > + .destroy = intel_primary_plane_destroy,
> > > +};
> > > +
> > > +static struct drm_plane *intel_primary_plane_create(struct drm_device *dev,
> > > + int pipe)
> > > +{
> > > + struct intel_plane *primary;
> > > + const uint32_t *intel_primary_formats;
> > > + int num_formats;
> > > +
> > > + primary = kzalloc(sizeof(*primary), GFP_KERNEL);
> > > + if (primary == NULL)
> > > + return NULL;
> > > +
> > > + primary->can_scale = false;
> > > + primary->max_downscale = 1;
> > > + primary->pipe = pipe;
> > > + primary->plane = pipe;
> > > + if (HAS_FBC(dev) && INTEL_INFO(dev)->gen < 4)
> > > + primary->plane = !pipe;
> > > +
> > > + if (INTEL_INFO(dev)->gen <= 3) {
> > > + intel_primary_formats = intel_primary_formats_gen3;
> > > + num_formats = ARRAY_SIZE(intel_primary_formats_gen3);
> > > + } else {
> > > + intel_primary_formats = intel_primary_formats_gen4;
> > > + num_formats = ARRAY_SIZE(intel_primary_formats_gen4);
> > > + }
> > > +
> > > + drm_plane_init(dev, &primary->base, 0,
> > > + &intel_primary_plane_funcs, intel_primary_formats,
> > > + num_formats, DRM_PLANE_TYPE_PRIMARY);
> > > + return &primary->base;
> > > +}
> > > +
> > > static void intel_crtc_init(struct drm_device *dev, int pipe)
> > > {
> > > struct drm_i915_private *dev_priv = dev->dev_private;
> > > struct intel_crtc *intel_crtc;
> > > - int i;
> > > + struct drm_plane *primary;
> > > + int i, ret;
> > >
> > > intel_crtc = kzalloc(sizeof(*intel_crtc), GFP_KERNEL);
> > > if (intel_crtc == NULL)
> > > return;
> > >
> > > - drm_crtc_init(dev, &intel_crtc->base, &intel_crtc_funcs);
> > > + primary = intel_primary_plane_create(dev, pipe);
> > > + ret = drm_crtc_init_with_planes(dev, &intel_crtc->base, primary,
> > > + NULL, &intel_crtc_funcs);
> > > + if (ret) {
> > > + drm_plane_cleanup(primary);
> > > + kfree(intel_crtc);
> > > + return;
> > > + }
> > >
> > > drm_mode_crtc_set_gamma_size(&intel_crtc->base, 256);
> > > for (i = 0; i < 256; i++) {
> > > --
> > > 1.8.5.1
> > >
> > > _______________________________________________
> > > Intel-gfx mailing list
> > > Intel-gfx@lists.freedesktop.org
> > > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> >
> > --
> > Ville Syrjälä
> > Intel OTC
>
> --
> Matt Roper
> Graphics Software Engineer
> IoTG Platform Enabling & Development
> Intel Corporation
> (916) 356-2795
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2014-05-15 17:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 17:06 [PATCH 0/4] Intel primary plane support (v6) Matt Roper
2014-04-30 17:07 ` [PATCH 1/4] drm: Check CRTC compatibility in setplane Matt Roper
2014-04-30 17:07 ` [PATCH 2/4] drm/plane-helper: Add drm_primary_helper_check_update() (v2) Matt Roper
2014-05-16 2:51 ` Lee, Chon Ming
2014-05-16 3:04 ` Rob Clark
2014-05-16 5:25 ` Lee, Chon Ming
2014-05-16 8:02 ` Daniel Vetter
2014-05-16 15:45 ` Matt Roper
2014-05-19 21:46 ` [PATCH 2/4] drm/plane-helper: Add drm_plane_helper_check_update() (v3) Matt Roper
2014-04-30 17:07 ` [PATCH 3/4] drm/i915: don't force full modeset if primary plane is disabled Matt Roper
2014-05-15 14:54 ` Ville Syrjälä
2014-05-15 16:13 ` [PATCH 3/4] drm/i915: don't force full modeset if primary plane is disabled (v2) Matt Roper
2014-04-30 17:07 ` [PATCH 4/4] drm/i915: Intel-specific primary plane handling (v6) Matt Roper
2014-05-15 15:52 ` Ville Syrjälä
2014-05-15 16:37 ` Matt Roper
2014-05-15 17:00 ` Ville Syrjälä [this message]
2014-05-15 19:35 ` Matt Roper
2014-05-15 20:49 ` Daniel Vetter
2014-05-15 20:59 ` Matt Roper
2014-05-15 21:20 ` Daniel Vetter
2014-05-15 21:25 ` Matt Roper
2014-05-15 19:21 ` [PATCH 4/4] drm/i915: Intel-specific primary plane handling (v7) Matt Roper
2014-05-18 15:53 ` Lee, Chon Ming
2014-05-19 21:44 ` Matt Roper
2014-05-19 21:48 ` [PATCH 4/4] drm/i915: Intel-specific primary plane handling (v8) Matt Roper
2014-05-28 5:41 ` Lee, Chon Ming
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=20140515170048.GG27580@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@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