From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 2/5] drm/i915: preserve swizzle settings if necessary v3
Date: Tue, 10 Jun 2014 12:45:38 -0700 [thread overview]
Message-ID: <20140610124538.350e86ba@jbarnes-desktop> (raw)
In-Reply-To: <20140610193326.GB5821@phenom.ffwll.local>
On Tue, 10 Jun 2014 21:33:27 +0200
Daniel Vetter <daniel@ffwll.ch> wrote:
> On Tue, Jun 10, 2014 at 7:27 PM, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> > Yes, that's what I do below... I even added it to the changelog:
> > http://patchwork.freedesktop.org/patch/27223/
> >
> > Did you miss the later hunk in intel_display.c?
> >
> > What we try to do here is enable swizzling if possible, which we can do
> > if no inherited fbs are tiled.
> >
> > So I think I've done exactly what you repeated above, and documented
> > it. So you're going to need to repeat it with different words so I can
> > understand, if I'm still missing something.
>
> In swizzle_detect:
>
> ...
>
> if (GEN6+) {
> if (preserve_bios_swizzle) {
> if (I915_READ(DISP_ARB_CTL) & DISP_TILE_SURFACE_SWIZZLING) {
> swizzle_x = I915_BIT_6_SWIZZLE_9_10;
> ...
> } else {
> swizzle_x = I915_BIT_6_SWIZZLE_NONE;
> ...
> }
> } else {
> /* existing/old logic to decide about swizzling */
> }
> }
>
> ...
>
> Plus no shortcut in i915_gem_init_swizzling. Personally I'd also just use
> a small helper function to compute preserve_bios_swizzle instead of
> storing it in dev_priv (since we will only use it at exactly one place),
> but that's a pure style preference.
Doesn't this amount to the same thing? I.e. we enable it if possible,
otherwise just report it as unswizzled? So you're just wanting a style
change here?
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-06-10 19:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 18:24 [PATCH 1/5] drm/i915: preserve SSC if previously set v2 Jesse Barnes
2014-06-05 18:24 ` [PATCH 2/5] drm/i915: preserve swizzle settings if necessary v3 Jesse Barnes
2014-06-10 14:02 ` Daniel Vetter
2014-06-10 17:27 ` Jesse Barnes
2014-06-10 19:33 ` Daniel Vetter
2014-06-10 19:45 ` Jesse Barnes [this message]
2014-06-11 9:23 ` Daniel Vetter
2014-06-11 15:13 ` Jesse Barnes
2014-06-11 15:39 ` Daniel Vetter
2014-06-11 15:41 ` Jesse Barnes
2014-06-27 16:15 ` Steve Aarnio
2014-07-07 9:03 ` [Intel-gfx] " Daniel Vetter
2014-06-05 18:24 ` [PATCH 3/5] drm: add drm_mode_same_size function Jesse Barnes
2014-06-05 18:24 ` [PATCH 4/5] drm/i915: use current mode if the size matches the preferred mode Jesse Barnes
2014-06-10 14:05 ` [Intel-gfx] " Daniel Vetter
2014-06-10 17:29 ` Jesse Barnes
2014-06-05 18:24 ` [PATCH 5/5] drm/i915: enable fastboot by default Jesse Barnes
2014-06-06 11:12 ` Jani Nikula
2014-06-10 14:10 ` Daniel Vetter
2014-06-10 14:07 ` [Intel-gfx] " Daniel Vetter
2014-06-10 17:31 ` Jesse Barnes
2014-06-10 18:01 ` Stéphane Marchesin
2014-06-10 18:42 ` [Intel-gfx] " Jesse Barnes
2014-06-11 9:30 ` Daniel Vetter
2014-06-06 11:04 ` [PATCH 1/5] drm/i915: preserve SSC if previously set v2 Jani Nikula
2014-06-06 11:06 ` Chris Wilson
2014-06-10 14:00 ` [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=20140610124538.350e86ba@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--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