From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [PATCH i-g-t 4/4] lib/intel: Documnent gem_can_store_dword()
Date: Wed, 2 Oct 2024 13:45:15 +0300 [thread overview]
Message-ID: <20241002104515.32164-4-ville.syrjala@linux.intel.com> (raw)
In-Reply-To: <20241002104515.32164-1-ville.syrjala@linux.intel.com>
From: Ville Syrjälä <ville.syrjala@linux.intel.com>
Add basic docs for gem_class_can_store_dword() and
gem_can_store_dword().
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
---
lib/igt_gt.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/lib/igt_gt.c b/lib/igt_gt.c
index b8faf2b7bd09..a8f7f4431d1c 100644
--- a/lib/igt_gt.c
+++ b/lib/igt_gt.c
@@ -667,6 +667,13 @@ static bool gem_store_dword_needs_physical(const struct intel_device_info *info)
}
}
+/**
+ * gem_class_can_store_dword:
+ * @fd: open i915 drm file descriptor
+ * @class: engine class
+ *
+ * Is the MI_STORE_DWORD instruction actually usable?
+ */
bool gem_class_can_store_dword(int fd, int class)
{
uint16_t devid = intel_get_drm_devid(fd);
@@ -685,6 +692,13 @@ bool gem_class_can_store_dword(int fd, int class)
return true;
}
+/**
+ * gem_can_store_dword:
+ * @fd: open i915 drm file descriptor
+ * @engine: engine
+ *
+ * Is the MI_STORE_DWORD instruction actually usable?
+ */
bool gem_can_store_dword(int fd, unsigned int engine)
{
return gem_class_can_store_dword(fd,
--
2.45.2
next prev parent reply other threads:[~2024-10-02 10:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 10:45 [PATCH i-g-t 1/4] lib/intel: Extract gem_store_dword_needs_physical() Ville Syrjala
2024-10-02 10:45 ` [PATCH i-g-t 2/4] lib/intel: Unify MI_STORE_DWORD secure batch checks Ville Syrjala
2024-10-02 14:43 ` Kamil Konieczny
2024-10-08 21:27 ` Ville Syrjälä
2024-10-10 18:49 ` Ville Syrjälä
2024-10-11 8:42 ` Kamil Konieczny
2024-10-02 10:45 ` [PATCH i-g-t 3/4] lib/intel: MI_STORE_DWORD doesn't need secure batches on i965 Ville Syrjala
2024-10-11 8:46 ` Kamil Konieczny
2024-10-02 10:45 ` Ville Syrjala [this message]
2024-10-11 8:48 ` [PATCH i-g-t 4/4] lib/intel: Documnent gem_can_store_dword() Kamil Konieczny
2024-10-02 12:00 ` ✗ Fi.CI.BAT: failure for series starting with [i-g-t,1/4] lib/intel: Extract gem_store_dword_needs_physical() Patchwork
2024-10-02 12:12 ` ✓ CI.xeBAT: success " Patchwork
2024-10-02 13:49 ` ✗ CI.xeFULL: failure " Patchwork
2024-10-04 10:33 ` ✗ GitLab.Pipeline: warning " Patchwork
2024-10-07 14:54 ` ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/4] lib/intel: Extract gem_store_dword_needs_physical() (rev2) Patchwork
2024-10-07 15:11 ` ✓ CI.xeBAT: " Patchwork
2024-10-08 6:51 ` ✗ CI.xeFULL: failure " Patchwork
2024-10-08 12:39 ` ✗ Fi.CI.IGT: " Patchwork
2024-10-11 8:45 ` [PATCH i-g-t 1/4] lib/intel: Extract gem_store_dword_needs_physical() Kamil Konieczny
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=20241002104515.32164-4-ville.syrjala@linux.intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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