From: Michael Cheng <michael.cheng@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: michael.cheng@intel.com, lucas.demarchi@intel.com,
dri-devel@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH v11 1/6] drm: Add arch arm64 for drm_clflush_virt_range
Date: Tue, 22 Feb 2022 21:58:55 -0800 [thread overview]
Message-ID: <20220223055900.415627-2-michael.cheng@intel.com> (raw)
In-Reply-To: <20220223055900.415627-1-michael.cheng@intel.com>
Add arm64 support for drm_clflush_virt_range. dcache_clean_inval_poc
performs a flush by first performing a clean, follow by an invalidation
operation.
v2 (Michael Cheng): Use correct macro for cleaning and invalidation the
dcache. Thanks Tvrtko for the suggestion.
v3 (Michael Cheng): Replace asm/cacheflush.h with linux/cacheflush.h
Signed-off-by: Michael Cheng <michael.cheng@intel.com>
Reviewed-by: Matt Roper <matthew.d.roper@intel.com>
---
drivers/gpu/drm/drm_cache.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/gpu/drm/drm_cache.c b/drivers/gpu/drm/drm_cache.c
index c3e6e615bf09..f7b17e0d57f0 100644
--- a/drivers/gpu/drm/drm_cache.c
+++ b/drivers/gpu/drm/drm_cache.c
@@ -28,6 +28,7 @@
* Authors: Thomas Hellström <thomas-at-tungstengraphics-dot-com>
*/
+#include <linux/cacheflush.h>
#include <linux/cc_platform.h>
#include <linux/export.h>
#include <linux/highmem.h>
@@ -174,6 +175,11 @@ drm_clflush_virt_range(void *addr, unsigned long length)
if (wbinvd_on_all_cpus())
pr_err("Timed out waiting for cache flush\n");
+
+#elif defined(CONFIG_ARM64)
+ void *end = addr + length;
+ dcache_clean_inval_poc((unsigned long)addr, (unsigned long)end);
+
#else
WARN_ONCE(1, "Architecture has no drm_cache.c support\n");
#endif
--
2.25.1
next prev parent reply other threads:[~2022-02-23 5:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 5:58 [Intel-gfx] [PATCH v11 0/6] Use drm_clflush* instead of clflush Michael Cheng
2022-02-23 5:58 ` Michael Cheng [this message]
2022-02-23 9:56 ` [Intel-gfx] [PATCH v11 1/6] drm: Add arch arm64 for drm_clflush_virt_range kernel test robot
2022-02-23 12:46 ` kernel test robot
2022-02-23 17:43 ` kernel test robot
2022-02-23 5:58 ` [Intel-gfx] [PATCH v11 2/6] drm/i915/gt: Re-work intel_write_status_page Michael Cheng
2022-02-23 5:58 ` [Intel-gfx] [PATCH v11 3/6] drm/i915/gt: Drop invalidate_csb_entries Michael Cheng
2022-02-23 5:58 ` [Intel-gfx] [PATCH v11 4/6] drm/i915/gt: Re-work reset_csb Michael Cheng
2022-02-23 5:58 ` [Intel-gfx] [PATCH v11 5/6] drm/i915/: Re-work clflush_write32 Michael Cheng
2022-02-23 5:59 ` [Intel-gfx] [PATCH v11 6/6] drm/i915/gt: replace cache_clflush_range Michael Cheng
2022-02-23 8:09 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Use drm_clflush* instead of clflush (rev10) Patchwork
2022-02-23 8:10 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-02-23 8:38 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-02-24 4:03 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Use drm_clflush* instead of clflush (rev11) Patchwork
2022-02-24 4:05 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-02-24 4:35 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-02-24 16:40 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=20220223055900.415627-2-michael.cheng@intel.com \
--to=michael.cheng@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@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