From: Mullati Siva <siva.mullati@intel.com>
To: intel-gfx@lists.freedesktop.org, siva.mullati@intel.com
Cc: lucas.demarchi@intel.com
Subject: [Intel-gfx] [PATCH 0/1] drm/i915/guc: Refactor CT access to use iosys_map
Date: Mon, 4 Apr 2022 15:01:24 +0530 [thread overview]
Message-ID: <20220404093125.73327-1-siva.mullati@intel.com> (raw)
From: Siva Mullati <siva.mullati@intel.com>
ver2: remove newly added iosys map api from ver1
ver3: address review comments
This is continuation to the below patch series to use iosys map
APIs, to use CT commands and descriptors.
https://patchwork.freedesktop.org/series/99711/
Siva Mullati (1):
drm/i915/guc: Convert ct buffer to iosys_map
drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c | 200 +++++++++++++---------
drivers/gpu/drm/i915/gt/uc/intel_guc_ct.h | 9 +-
2 files changed, 127 insertions(+), 82 deletions(-)
--
2.33.0
next reply other threads:[~2022-04-04 9:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 9:31 Mullati Siva [this message]
2022-04-04 9:31 ` [Intel-gfx] [PATCH 1/1] drm/i915/guc: Convert ct buffer to iosys_map Mullati Siva
2022-04-14 12:11 ` Balasubramani Vivekanandan
2022-04-28 14:13 ` Siva Mullati
2022-04-29 9:07 ` Balasubramani Vivekanandan
2022-04-18 9:08 ` Balasubramani Vivekanandan
2022-04-04 10:41 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/guc: Refactor CT access to use iosys_map (rev3) Patchwork
2022-04-04 11:14 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-04-04 13:42 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-04-08 5:07 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/guc: Refactor CT access to use iosys_map (rev4) Patchwork
2022-04-08 5:42 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2022-05-09 6:49 [Intel-gfx] [PATCH 0/1] drm/i915/guc: Refactor CT access to use iosys_map Mullati Siva
2022-03-22 8:44 Mullati Siva
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=20220404093125.73327-1-siva.mullati@intel.com \
--to=siva.mullati@intel.com \
--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