public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Gustavo Padovan <gustavo@padovan.org>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org,
	Gustavo Padovan <gustavo.padovan@collabora.co.uk>,
	dri-devel@lists.freedesktop.org
Subject: Re: [RFC 2/3] drm/i915: create intel_update_pipe_size()
Date: Tue, 9 Sep 2014 14:43:14 -0300	[thread overview]
Message-ID: <20140909174314.GD26794@joana> (raw)
In-Reply-To: <20140909155318.GK4193@intel.com>

2014-09-09 Ville Syrjälä <ville.syrjala@linux.intel.com>:

> On Tue, Sep 09, 2014 at 11:43:20AM -0300, Gustavo Padovan wrote:
> > From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> > 
> > Factor out a piece of code from intel_pipe_set_base() that updates
> > the pipe size and adjust fitter.
> > 
> > This will help refactor the update primary plane path.
> > 
> > Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> > ---
> >  drivers/gpu/drm/i915/intel_display.c | 71 +++++++++++++++++++++---------------
> >  1 file changed, 41 insertions(+), 30 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> > index 2ccf7c0..e7e7184 100644
> > --- a/drivers/gpu/drm/i915/intel_display.c
> > +++ b/drivers/gpu/drm/i915/intel_display.c
> > @@ -2779,6 +2779,46 @@ static bool intel_crtc_has_pending_flip(struct drm_crtc *crtc)
> >  	return pending;
> >  }
> >  
> > +static void intel_update_pipe_size(struct drm_crtc *crtc)
> 
> These days we usually prefer to pass intel_crtc instead of drm_crtc. You
> can still call it 'crtc' since that's shorter and because we don't need
> anything from drm_crtc in this function there won't be any confusion
> between the two.

Actually we need the drm_crtc 3 times in this function, that is why I left it
as an argument. We could just do the other way around and get it from
&intel_crtc->base.

	Gustavo

  reply	other threads:[~2014-09-09 17:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-09 14:43 [RFC 1/3] drm/i915: remove !enabled handling from commit primary plane step Gustavo Padovan
2014-09-09 14:43 ` [RFC 2/3] drm/i915: create intel_update_pipe_size() Gustavo Padovan
2014-09-09 15:53   ` Ville Syrjälä
2014-09-09 17:43     ` Gustavo Padovan [this message]
2014-09-10  6:32       ` Daniel Vetter
2014-09-09 14:43 ` [RFC 3/3] drm/i915: Merge of visible and !visible paths for primary planes Gustavo Padovan
2014-09-09 17:26   ` Ville Syrjälä
2014-09-09 15:58 ` [RFC 1/3] drm/i915: remove !enabled handling from commit primary plane step Ville Syrjälä
2014-09-10  6:33   ` [Intel-gfx] " Daniel Vetter

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=20140909174314.GD26794@joana \
    --to=gustavo@padovan.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gustavo.padovan@collabora.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --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