From: Michel Thierry <michel.thierry@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [PATCH] drm/i915: Move LRC register offsets to a header file
Date: Mon, 22 Jan 2018 12:26:35 -0800 [thread overview]
Message-ID: <24f68542-9cd4-c7ed-3ecc-4107b4e1aedd@intel.com> (raw)
In-Reply-To: <151665205674.21091.14995344395344242567@mail.alporthouse.com>
On 1/22/2018 12:14 PM, Chris Wilson wrote:
> Quoting Michel Thierry (2018-01-22 20:06:32)
>> Newer platforms may have subtle offset changes, which will increase the
>> number of defines, so it is probably better to start moving them to its
>> own header file. Also move the macros used while setting the reg state.
>
> I was scared that we might be starting to duplicate the lrc setup
> code. If you can see a quick way of splitting the lrc setup from
> execlists submission, that would also be good.
>
At the very least, we will need different implementations of
execlists_init_reg_state.
>> Signed-off-by: Michel Thierry <michel.thierry@intel.com>
>> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
>> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
>> ---
>> drivers/gpu/drm/i915/intel_lrc.c | 50 +-----------------
>> drivers/gpu/drm/i915/intel_lrc_reg_offsets.h | 78 ++++++++++++++++++++++++++++
>> 2 files changed, 79 insertions(+), 49 deletions(-)
>> create mode 100644 drivers/gpu/drm/i915/intel_lrc_reg_offsets.h
>>
>> diff --git a/drivers/gpu/drm/i915/intel_lrc.c b/drivers/gpu/drm/i915/intel_lrc.c
>> index 506bc2bc04f9..bc9287645bf3 100644
>> --- a/drivers/gpu/drm/i915/intel_lrc.c
>> +++ b/drivers/gpu/drm/i915/intel_lrc.c
>> @@ -137,6 +137,7 @@
>> #include <drm/i915_drm.h>
>> #include "i915_drv.h"
>> #include "i915_gem_render_state.h"
>> +#include "intel_lrc_reg_offsets.h"
>
> Just intel_lrc_reg.h to be consistent with i915_reg.h and
> intel_guc_reg.h
>
> The numbers look the same, so with a new filename,
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Thanks, I'll resend it with the new filename.
> -Chris
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-01-22 20:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 20:06 [PATCH] drm/i915: Move LRC register offsets to a header file Michel Thierry
2018-01-22 20:14 ` Chris Wilson
2018-01-22 20:26 ` Michel Thierry [this message]
2018-01-22 20:26 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-01-22 20:32 ` [PATCH v2] " Michel Thierry
2018-01-22 20:56 ` Lucas De Marchi
2018-01-22 21:28 ` Michal Wajdeczko
2018-01-22 21:49 ` Michel Thierry
2018-01-23 0:31 ` Lucas De Marchi
2018-01-23 0:41 ` Michel Thierry
2018-01-23 8:48 ` Chris Wilson
2018-01-23 16:06 ` Lucas De Marchi
2018-01-23 16:18 ` Michal Wajdeczko
2018-01-23 16:27 ` Lucas De Marchi
2018-01-23 16:28 ` Chris Wilson
2018-01-24 10:13 ` Jani Nikula
2018-01-22 20:54 ` ✓ Fi.CI.BAT: success for drm/i915: Move LRC register offsets to a header file (rev2) Patchwork
2018-01-23 0:41 ` [PATCH v3] drm/i915: Move LRC register offsets to a header file Michel Thierry
2018-01-23 1:00 ` ✓ Fi.CI.BAT: success for drm/i915: Move LRC register offsets to a header file (rev3) Patchwork
2018-01-23 7:46 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-01-23 19:50 ` [PATCH v4] drm/i915: Move LRC register offsets to a header file Michel Thierry
2018-01-23 20:57 ` Chris Wilson
2018-01-23 20:09 ` ✓ Fi.CI.BAT: success for drm/i915: Move LRC register offsets to a header file (rev4) Patchwork
2018-01-24 4:52 ` ✓ Fi.CI.IGT: " 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=24f68542-9cd4-c7ed-3ecc-4107b4e1aedd@intel.com \
--to=michel.thierry@intel.com \
--cc=chris@chris-wilson.co.uk \
--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