Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 8/9] drm/i915: treat no fb -> fb as simple flip instead of full mode set
Date: Wed, 27 Mar 2013 08:51:03 -0700	[thread overview]
Message-ID: <20130327085103.4b69edd0@jbarnes-desktop> (raw)
In-Reply-To: <CAKMK7uHB_Z3fXhCMpjsr+dFeNeTOMfrJCUBSgFLD6mDhhzD6BA@mail.gmail.com>

On Wed, 27 Mar 2013 13:49:47 +0100
Daniel Vetter <daniel@ffwll.ch> wrote:

> On Wed, Mar 27, 2013 at 3:09 AM, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> > If for example the BIOS fb is too small for the dual pipe config we detect,
> > we may have valid timings and such, but no fb. The pfit case also hits this
> > path (though currently only fastboots if you hack your mode clock to match).
> 
> But even when the BIOS fb is to small and the BIOS config uses the
> pfit, we /should/ have an fb around. Looking a bit closer I think the
> confusion stems from you reading out the adjusted mode, but treating
> it like the requested mode. I think it'd be much more solid if we
> store the read-out mode in the adjusted_mode (won't work otherwise
> with hw state cross-checking anyway), and then do two comparisons
> here:

Yeah, there's an fb, but it may not be what we want.  So we don't
allocate it and thus crtc->fb is empty.

> - Does the request mode (plus everything else) match? If so, just do
> an fb_set_base call.
> - Does the adjusted mode match (plus the entire output routing ofc)?
> That means there's either the vga plane or a pfit in-between which we
> don't like. If possible we can then play some tricks to avoid the full
> modeset.

Right, I'm trying to play tricks here for sure.

> The reason that I'm a bit freaked about about your change here is that
> in a lot of places we treat crtc->fb == NULL as "no mode set". So I
> fear we're breaking a few too many assumptions here with that hack,
> and it simply needs more thought about what we should actually check.

Yeah I was worried about that too.  Maybe we should use crtc->active
for that everywhere?

With the modeset rework and pipe config stuff, we should be able to
drop this in favor of something that looks at the pipe_config and
figures out the minimal mode set sequence required.

-- 
Jesse Barnes, Intel Open Source Technology Center

  parent reply	other threads:[~2013-03-27 15:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27  2:09 [PATCH 8/9] drm/i915: treat no fb -> fb as simple flip instead of full mode set Jesse Barnes
2013-03-27 12:49 ` Daniel Vetter
2013-03-27 13:40   ` Chris Wilson
2013-03-27 15:51   ` Jesse Barnes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-03-26 23:33 Updated fastboot patches Jesse Barnes
2013-03-26 23:33 ` [PATCH 8/9] drm/i915: treat no fb -> fb as simple flip instead of full mode set Jesse Barnes
2013-03-27  0:03   ` 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=20130327085103.4b69edd0@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.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