All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: Michel Thierry <michel.thierry@intel.com>,
	Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [PATCH 4/4] drm/i915/tgl: Report valid VDBoxes with SFC capability
Date: Wed, 31 Jul 2019 10:09:54 -0700	[thread overview]
Message-ID: <d4080825-d4ed-ed55-40cc-8ac3a02d7b37@intel.com> (raw)
In-Reply-To: <bc420e6a-f716-36b9-c57a-f575b08bd4f5@linux.intel.com>



On 7/30/19 10:59 PM, Tvrtko Ursulin wrote:
> 
> On 31/07/2019 01:49, Daniele Ceraolo Spurio wrote:
>> From: Michel Thierry <michel.thierry@intel.com>
>>
>> In Gen11, only even numbered "logical" VDBoxes are hooked up to a SFC
>> (Scaler & Format Converter) unit. This is not the case in Tigerlake,
>> where each VDBox can access a SFC.
>>
>> We will use this information to decide when the SFC units need to be 
>> reset
>> and also pass it to the GuC.
>>
>> Bspec: 48077
>> Signed-off-by: Michel Thierry <michel.thierry@intel.com>
>> Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
>> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
>> Cc: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
>> ---
>>   drivers/gpu/drm/i915/intel_device_info.c | 3 ++-
>>   1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_device_info.c 
>> b/drivers/gpu/drm/i915/intel_device_info.c
>> index f99c9fd497b2..2a39b52c3582 100644
>> --- a/drivers/gpu/drm/i915/intel_device_info.c
>> +++ b/drivers/gpu/drm/i915/intel_device_info.c
>> @@ -1022,8 +1022,9 @@ void intel_device_info_init_mmio(struct 
>> drm_i915_private *dev_priv)
>>           /*
>>            * In Gen11, only even numbered logical VDBOXes are
>>            * hooked up to an SFC (Scaler & Format Converter) unit.
>> +         * In TGL each VDBOX has access to an SFC.
>>            */
>> -        if (logical_vdbox++ % 2 == 0)
>> +        if (IS_TIGERLAKE(dev_priv) || logical_vdbox++ % 2 == 0)
>>               RUNTIME_INFO(dev_priv)->vdbox_sfc_access |= BIT(i);
>>       }
>>       DRM_DEBUG_DRIVER("vdbox enable: %04x, instances: %04lx\n",
>>
> 
> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> 
> Only uncertainty is if we want to code the condition as Icelake 
> exception instead for more future proofing. Like if "!IS_ICELAKE ||" 
> instead of "IS_TIGERLAKE ||"?

If I'm understanding the specs correctly then this isn't going to apply 
to all future platform and we'll have some of them that behave like ICL 
instead. Maybe a device flag would work better? HAS_SFC_FOR_EACH_VCS()?

Daniele

> 
> Regards,
> 
> Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-07-31 17:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-31  0:48 [PATCH 0/4] Initial TGL submission changes Daniele Ceraolo Spurio
2019-07-31  0:48 ` [PATCH 1/4] drm/i915/tgl: add Gen12 default indirect ctx offset Daniele Ceraolo Spurio
2019-07-31  0:49 ` [PATCH 2/4] drm/i915/tgl: add GEN12_MAX_CONTEXT_HW_ID Daniele Ceraolo Spurio
2019-07-31  0:49 ` [PATCH 3/4] drm/i915/tgl: Gen12 csb support Daniele Ceraolo Spurio
2019-07-31  6:29   ` Tvrtko Ursulin
2019-07-31 17:33     ` Daniele Ceraolo Spurio
2019-07-31  7:33   ` Chris Wilson
2019-07-31 20:18     ` Daniele Ceraolo Spurio
2019-07-31  0:49 ` [PATCH 4/4] drm/i915/tgl: Report valid VDBoxes with SFC capability Daniele Ceraolo Spurio
2019-07-31  5:59   ` Tvrtko Ursulin
2019-07-31 17:09     ` Daniele Ceraolo Spurio [this message]
2019-07-31  1:10 ` ✗ Fi.CI.CHECKPATCH: warning for Initial TGL submission changes Patchwork
2019-07-31  1:39 ` ✓ Fi.CI.BAT: success " Patchwork
2019-08-01 15:15 ` ✓ Fi.CI.IGT: " Patchwork

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=d4080825-d4ed-ed55-40cc-8ac3a02d7b37@intel.com \
    --to=daniele.ceraolospurio@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=michel.thierry@intel.com \
    --cc=tvrtko.ursulin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.