public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Daniel Vetter <daniel@ffwll.ch>,
	Vandana Kannan <vandana.kannan@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [RFC] drm/i915: Render decompression support for Gen9 and above
Date: Tue, 08 Sep 2015 15:07:40 -0700	[thread overview]
Message-ID: <55EF5C2C.3000908@virtuousgeek.org> (raw)
In-Reply-To: <20150907163553.GE32505@phenom.ffwll.local>

On 09/07/2015 09:35 AM, Daniel Vetter wrote:
> On Sat, Sep 05, 2015 at 01:12:50AM +0530, Vandana Kannan wrote:
>> This patch includes enabling render decompression after checking all the
>> requirements (format, tiling, rotation etc.). Along with this, the WAs
>> mentioned in BSpec Workaround page have been implemented.
>>
>> This patch has been implemented on top of Nabendu/Chandra's NV12 patches.
>>
>> TODO:
>> 1. Disable stereo 3D when render decomp is enabled (bit 7:6)
>> 2. Render decompression must not be used in VTd pass-through mode
>> 3. Program hashing select CHICKEN_MISC1 bit 15
>> 4. For Gen10, add support for RGB 1010102
>>
>> Signed-off-by: Vandana Kannan <vandana.kannan@intel.com>
>> ---
>>  drivers/gpu/drm/drm_atomic.c         |   4 +
>>  drivers/gpu/drm/drm_crtc.c           |  16 ++++
>>  drivers/gpu/drm/i915/intel_display.c | 174 +++++++++++++++++++++++++++++++++++
>>  drivers/gpu/drm/i915/intel_drv.h     |   7 ++
>>  drivers/gpu/drm/i915/intel_sprite.c  |  35 +++++++
>>  include/drm/drm_crtc.h               |  11 +++
>>  6 files changed, 247 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/drm_atomic.c b/drivers/gpu/drm/drm_atomic.c
>> index 940f80b..d9004e8 100644
>> --- a/drivers/gpu/drm/drm_atomic.c
>> +++ b/drivers/gpu/drm/drm_atomic.c
>> @@ -607,6 +607,8 @@ int drm_atomic_plane_set_property(struct drm_plane *plane,
>>  		state->src_h = val;
>>  	} else if (property == config->rotation_property) {
>>  		state->rotation = val;
>> +	} else if (property == config->compression_property) {
>> +		state->compression = val;
> 
> Please use a framebuffer modifier instead. Also this needs userspace.

I thought we already agreed, based on feedback from the userspace guys,
that a property was easier to use and therefore the way to go?

Jesse

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-09-08 22:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04 19:42 [RFC] drm/i915: Render decompression support for Gen9 and above Vandana Kannan
2015-09-07 16:35 ` Daniel Vetter
2015-09-08 22:07   ` Jesse Barnes [this message]
2015-09-09 15:23     ` Daniel Vetter
2015-09-09 15:24       ` Jesse Barnes
2015-09-09 16:36         ` Smith, Gary K
2015-09-09 17:04           ` Jesse Barnes
2015-09-10 15:02             ` Daniel Vetter
2016-01-19 10:28               ` Daniel Stone
2016-01-25 17:38                 ` Jesse Barnes
2016-01-25 18:15                   ` Smith, Gary K
2016-01-25 18:37                     ` Daniel Stone
2016-01-25 19:04                       ` Smith, Gary K
2016-01-25 19:08                         ` Smith, Gary K
2016-01-25 19:09                         ` Daniel Stone
2016-01-26  9:43                           ` 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=55EF5C2C.3000908@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=vandana.kannan@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