From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Gabriel Krisman Bertazi <krisman@collabora.co.uk>
Cc: Ben Widawsky <ben@bwidawsk.net>, intel-gfx@lists.freedesktop.org
Subject: Re: Question about CCS modifier on GLK
Date: Mon, 18 Dec 2017 13:36:23 +0200 [thread overview]
Message-ID: <20171218113623.GG10981@intel.com> (raw)
In-Reply-To: <87y3m07tk6.fsf@collabora.co.uk>
On Sun, Dec 17, 2017 at 10:45:13PM -0200, Gabriel Krisman Bertazi wrote:
>
> Hi Ben and list folks,
>
> I've been investigating some CI failures with the kms_ccs testcase in
> the GLK hardware. The original bug is linked below, but there are other
> more basic tests failing when trying CCS on pipe C.
>
> https://bugs.freedesktop.org/show_bug.cgi?id=104096
>
> The reason for the failure is very straightforward, the function
> skl_check_ccs_aux_surface() in intel_display.c rejects CCS modifiers for
> PIPE_C, since that is not supported for SKL, KBL and as far as I can
> tell APL as well.
>
> But, since I don't have the specs for GLK yet (it's not available in
> 01.org), I can't tell if GLK will support it and the kernel must be
> changed or if the testcase itself is bogus. My money is on the later,
> but I could use a confirmation before writing down the patch.
>
> In short, does pipe C support render compression (ccs modifier) in glk?
No. But the current code is somewhat busted anyway. See
https://patchwork.freedesktop.org/series/29308/
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-12-18 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 0:45 Question about CCS modifier on GLK Gabriel Krisman Bertazi
2017-12-18 11:36 ` Ville Syrjälä [this message]
2017-12-20 16:46 ` Ben Widawsky
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=20171218113623.GG10981@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=ben@bwidawsk.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=krisman@collabora.co.uk \
/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