public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrzej Hajda <andrzej.hajda@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org,
	Andi Shyti <andi.shyti@linux.intel.com>,
	Chris Wilson <chris.p.wilson@linux.intel.com>,
	Nirmoy Das <nirmoy.das@intel.com>,
	Andrzej Hajda <andrzej.hajda@intel.com>
Subject: [PATCH v5 2/4] drm/i915/display: use nop_clear_range instead of local function
Date: Wed, 08 Mar 2023 16:39:04 +0100	[thread overview]
Message-ID: <20230308-guard_error_capture-v5-2-6d1410d13540@intel.com> (raw)
In-Reply-To: <20230308-guard_error_capture-v5-0-6d1410d13540@intel.com>

Since nop_clear_range is visible it can be used here.

Signed-off-by: Andrzej Hajda <andrzej.hajda@intel.com>
---
 drivers/gpu/drm/i915/display/intel_dpt.c | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/drivers/gpu/drm/i915/display/intel_dpt.c b/drivers/gpu/drm/i915/display/intel_dpt.c
index ad1a37b515fb1c..eb9d1a6cbfb9dd 100644
--- a/drivers/gpu/drm/i915/display/intel_dpt.c
+++ b/drivers/gpu/drm/i915/display/intel_dpt.c
@@ -73,11 +73,6 @@ static void dpt_insert_entries(struct i915_address_space *vm,
 		gen8_set_pte(&base[i++], pte_encode | addr);
 }
 
-static void dpt_clear_range(struct i915_address_space *vm,
-			    u64 start, u64 length)
-{
-}
-
 static void dpt_bind_vma(struct i915_address_space *vm,
 			 struct i915_vm_pt_stash *stash,
 			 struct i915_vma_resource *vma_res,
@@ -291,7 +286,7 @@ intel_dpt_create(struct intel_framebuffer *fb)
 	i915_address_space_init(vm, VM_CLASS_DPT);
 
 	vm->insert_page = dpt_insert_page;
-	vm->clear_range = dpt_clear_range;
+	vm->clear_range = nop_clear_range;
 	vm->insert_entries = dpt_insert_entries;
 	vm->cleanup = dpt_cleanup;
 

-- 
2.34.1

  parent reply	other threads:[~2023-03-08 15:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08 15:39 [PATCH v5 0/4] drm/i915: add guard page to ggtt->error_capture Andrzej Hajda
2023-03-08 15:39 ` [PATCH v5 1/4] drm/i915/gt: make nop_clear_range public Andrzej Hajda
2023-03-09  0:00   ` Andi Shyti
2023-03-08 15:39 ` Andrzej Hajda [this message]
2023-03-09  0:01   ` [PATCH v5 2/4] drm/i915/display: use nop_clear_range instead of local function Andi Shyti
2023-03-08 15:39 ` [PATCH v5 3/4] drm/i915/selftests: " Andrzej Hajda
2023-03-09  0:02   ` Andi Shyti
2023-03-08 15:39 ` [PATCH v5 4/4] drm/i915: add guard page to ggtt->error_capture Andrzej Hajda
2023-03-09  9:08   ` Tvrtko Ursulin
2023-03-09  9:34     ` Andrzej Hajda
2023-03-09  9:43       ` Tvrtko Ursulin
2023-03-09  9:59         ` Andrzej Hajda
2023-03-09 10:17           ` Tvrtko Ursulin

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=20230308-guard_error_capture-v5-2-6d1410d13540@intel.com \
    --to=andrzej.hajda@intel.com \
    --cc=andi.shyti@linux.intel.com \
    --cc=chris.p.wilson@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nirmoy.das@intel.com \
    --cc=rodrigo.vivi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox