All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Intel-specific primary plane handling (v2)
Date: Fri, 11 Apr 2014 20:27:41 +0200	[thread overview]
Message-ID: <20140411182741.GO9262@phenom.ffwll.local> (raw)
In-Reply-To: <20140411174155.GH1063@intel.com>

On Fri, Apr 11, 2014 at 10:41:56AM -0700, Matt Roper wrote:
> On Fri, Apr 11, 2014 at 11:34:36AM +0200, Daniel Vetter wrote:
> > On Thu, Apr 10, 2014 at 05:24:36PM -0700, Matt Roper wrote:
> ...
> > 
> > Hm, I've thought we could do a simple
> > 
> > 	if (intel_crtc->primary_enabled)
> > 		call_primary_plane_helper
> > 	else
> > 		enable_the_hw_plane
> > 
> > But we need to do all the arg checking for the !primary_enabled case :(
> > Anyway more code sharing make me happier.
> > 
> > Cheers, Daniel
> 
> I think the problem here is that the helper has a bunch of tests
> targetted at the lowest common denominator hardware.  Some of the things
> it rejects are things that our hardware may begin to allow at some point
> in the future (e.g., primary plane scaling, partial CRTC coverage of
> primary plane, etc.).  We can probably call into the helper today and
> get the behavior we want, but I'd expect that some of those restrictions
> will need to be relaxed in the future and then we'll have to switch the
> code back at that point.  Given that we still need to do all this
> checking in the 'if (!enabled)' case, I don't think it's worth trying to
> call through the helper for the 'if (enabled)' case (especially since
> the actual "work" here after we're done testing is just a couple lines
> of code)?

Well for that future I simply expect that we'll get a completely new
update_plane function. I agree that reusing the helper completely doesn't
work really, but sharing the tests would be nice imo.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2014-04-11 18:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-11  0:24 [PATCH] drm/i915: Intel-specific primary plane handling (v2) Matt Roper
2014-04-11  0:26 ` [PATCH i-g-t 0/3] Universal plane testing Matt Roper
2014-04-11  0:26   ` [PATCH i-g-t 1/3] kms: Add universal plane support Matt Roper
2014-04-11  0:26   ` [PATCH i-g-t 2/3] kms_plane: Update for universal plane changes Matt Roper
2014-04-11  0:26   ` [PATCH i-g-t 3/3] kms_universal_plane: Universal plane testing Matt Roper
2014-04-11  9:22     ` Daniel Vetter
2014-04-11 11:57       ` Daniel Vetter
2014-04-11  9:34 ` [PATCH] drm/i915: Intel-specific primary plane handling (v2) Daniel Vetter
2014-04-11 14:17   ` Matt Roper
2014-04-11 14:23     ` Daniel Vetter
2014-04-11 17:41   ` Matt Roper
2014-04-11 18:27     ` Daniel Vetter [this message]
2014-04-11 20:44 ` [PATCH] drm/i915: Intel-specific primary plane handling (v3) Matt Roper
2014-04-11 21:13   ` [PATCH] drm/i915: Intel-specific primary plane handling (v4) Matt Roper
2014-04-22 12:47     ` Ville Syrjälä
2014-04-22 15:18       ` Matt Roper
2014-04-22 17:14         ` Daniel Vetter
2014-04-22 17:32           ` Matt Roper

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=20140411182741.GO9262@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.