Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Animesh Manna <animesh.manna@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	Chris Wilson <chris@chris-wilson.co.uk>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/dsb: Remove PIN_MAPPABLE from the DSB object VMA
Date: Tue, 29 Oct 2019 18:50:28 +0530	[thread overview]
Message-ID: <76cd793a-d26c-9e37-8047-db2b65b6d860@intel.com> (raw)
In-Reply-To: <a936adad-0172-8f6d-106b-9548315b971a@intel.com>



On 10/25/2019 8:52 PM, Animesh Manna wrote:
>
> On 10/17/2019 9:28 PM, Tvrtko Ursulin wrote:
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> It sounds like the hardware only needs the DSB object to be in global 
>> GTT
>> and not in the mappable region.
>
> Currently tested and working without any regression, waiting for 
> confirmation from h/w team, will update soon.

Got confirmation from h/w team, changes are ok to me.
Reviewed-by: Animesh Manna <animesh.manna@intel.com>
Thanks Chris, Tvrtko for the learning.

Regards,
Animesh

>
> Regards,
> Animesh
>>
>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> Cc: Animesh Manna <animesh.manna@intel.com>
>> ---
>>   drivers/gpu/drm/i915/display/intel_dsb.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_dsb.c 
>> b/drivers/gpu/drm/i915/display/intel_dsb.c
>> index bb5a0e91b370..d8ad5fe1efef 100644
>> --- a/drivers/gpu/drm/i915/display/intel_dsb.c
>> +++ b/drivers/gpu/drm/i915/display/intel_dsb.c
>> @@ -119,7 +119,7 @@ intel_dsb_get(struct intel_crtc *crtc)
>>           goto err;
>>       }
>>   -    vma = i915_gem_object_ggtt_pin(obj, NULL, 0, 0, PIN_MAPPABLE);
>> +    vma = i915_gem_object_ggtt_pin(obj, NULL, 0, 0, 0);
>>       if (IS_ERR(vma)) {
>>           DRM_ERROR("Vma creation failed\n");
>>           i915_gem_object_put(obj);
>

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

WARNING: multiple messages have this Message-ID (diff)
From: Animesh Manna <animesh.manna@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	Chris Wilson <chris@chris-wilson.co.uk>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/dsb: Remove PIN_MAPPABLE from the DSB object VMA
Date: Tue, 29 Oct 2019 18:50:28 +0530	[thread overview]
Message-ID: <76cd793a-d26c-9e37-8047-db2b65b6d860@intel.com> (raw)
Message-ID: <20191029132028.1QrvDxzWk-TxCzsK1U_LziUoRPfh_rXgBXjtFx3uvtA@z> (raw)
In-Reply-To: <a936adad-0172-8f6d-106b-9548315b971a@intel.com>



On 10/25/2019 8:52 PM, Animesh Manna wrote:
>
> On 10/17/2019 9:28 PM, Tvrtko Ursulin wrote:
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> It sounds like the hardware only needs the DSB object to be in global 
>> GTT
>> and not in the mappable region.
>
> Currently tested and working without any regression, waiting for 
> confirmation from h/w team, will update soon.

Got confirmation from h/w team, changes are ok to me.
Reviewed-by: Animesh Manna <animesh.manna@intel.com>
Thanks Chris, Tvrtko for the learning.

Regards,
Animesh

>
> Regards,
> Animesh
>>
>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> Cc: Animesh Manna <animesh.manna@intel.com>
>> ---
>>   drivers/gpu/drm/i915/display/intel_dsb.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_dsb.c 
>> b/drivers/gpu/drm/i915/display/intel_dsb.c
>> index bb5a0e91b370..d8ad5fe1efef 100644
>> --- a/drivers/gpu/drm/i915/display/intel_dsb.c
>> +++ b/drivers/gpu/drm/i915/display/intel_dsb.c
>> @@ -119,7 +119,7 @@ intel_dsb_get(struct intel_crtc *crtc)
>>           goto err;
>>       }
>>   -    vma = i915_gem_object_ggtt_pin(obj, NULL, 0, 0, PIN_MAPPABLE);
>> +    vma = i915_gem_object_ggtt_pin(obj, NULL, 0, 0, 0);
>>       if (IS_ERR(vma)) {
>>           DRM_ERROR("Vma creation failed\n");
>>           i915_gem_object_put(obj);
>

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

  parent reply	other threads:[~2019-10-29 13:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-17 15:58 [PATCH] drm/i915/dsb: Remove PIN_MAPPABLE from the DSB object VMA Tvrtko Ursulin
2019-10-17 20:41 ` ✗ Fi.CI.BAT: failure for " Patchwork
2019-10-18 15:44 ` ✗ Fi.CI.BAT: failure for drm/i915/dsb: Remove PIN_MAPPABLE from the DSB object VMA (rev2) Patchwork
2019-10-25 15:22 ` [PATCH] drm/i915/dsb: Remove PIN_MAPPABLE from the DSB object VMA Animesh Manna
2019-10-25 15:22   ` [Intel-gfx] " Animesh Manna
2019-10-29 13:20   ` Animesh Manna [this message]
2019-10-29 13:20     ` Animesh Manna
2019-11-01 16:57 ` ✓ Fi.CI.BAT: success for drm/i915/dsb: Remove PIN_MAPPABLE from the DSB object VMA (rev3) Patchwork
2019-11-01 16:57   ` [Intel-gfx] " Patchwork
2019-11-03  2:01 ` ✓ Fi.CI.IGT: " Patchwork
2019-11-03  2:01   ` [Intel-gfx] " 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=76cd793a-d26c-9e37-8047-db2b65b6d860@intel.com \
    --to=animesh.manna@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox