From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH v2 0/4] Add ops to intel_uc
Date: Fri, 10 Jan 2020 16:29:26 +0000 [thread overview]
Message-ID: <20200110162930.88968-1-michal.wajdeczko@intel.com> (raw)
Instead of spreading multiple conditionals across the uC code
to find out current mode of uC operation, start using predefined
set of function pointers that reflect that mode.
v2: rebased, using macro to generate ops helpers
Michal Wajdeczko (4):
drm/i915/uc: Add ops to intel_uc
drm/i915/uc: Add init_fw/fini_fw to to intel_uc_ops
drm/i915/uc: Add init/fini to to intel_uc_ops
drm/i915/uc: Add sanitize to to intel_uc_ops
drivers/gpu/drm/i915/gt/uc/intel_uc.c | 77 +++++++++++++++++++--------
drivers/gpu/drm/i915/gt/uc/intel_uc.h | 36 ++++++++++---
2 files changed, 83 insertions(+), 30 deletions(-)
--
2.19.2
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2020-01-10 16:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 16:29 Michal Wajdeczko [this message]
2020-01-10 16:29 ` [Intel-gfx] [PATCH v2 1/4] drm/i915/uc: Add ops to intel_uc Michal Wajdeczko
2020-01-10 16:57 ` Chris Wilson
2020-01-10 18:47 ` Michal Wajdeczko
2020-01-10 18:57 ` Chris Wilson
2020-01-10 19:23 ` [Intel-gfx] [PATCH v3 " Michal Wajdeczko
2020-01-10 16:29 ` [Intel-gfx] [PATCH v2 2/4] drm/i915/uc: Add init_fw/fini_fw to to intel_uc_ops Michal Wajdeczko
2020-01-10 16:29 ` [Intel-gfx] [PATCH v2 3/4] drm/i915/uc: Add init/fini " Michal Wajdeczko
2020-01-10 16:29 ` [Intel-gfx] [PATCH v2 4/4] drm/i915/uc: Add sanitize " Michal Wajdeczko
2020-01-10 19:48 ` Chris Wilson
2020-01-10 22:00 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Add ops to intel_uc (rev3) Patchwork
2020-01-10 22:29 ` [Intel-gfx] ✓ Fi.CI.BAT: success " 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=20200110162930.88968-1-michal.wajdeczko@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-gfx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.