From: Jani Nikula <jani.nikula@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/7] drm/i915: move I915_IDLE_ENGINES_TIMEOUT next to its only user
Date: Fri, 20 Jan 2023 12:39:23 +0200 [thread overview]
Message-ID: <87v8l18p7o.fsf@intel.com> (raw)
In-Reply-To: <Y8ptwyLJQqEbhjqy@intel.com>
On Fri, 20 Jan 2023, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> On Wed, Jan 18, 2023 at 03:15:33PM +0200, Jani Nikula wrote:
>> Declutter i915_drv.h. If there's ever a need to use this in more than
>> one place, we can figure out a better spot then. For now, this seems
>> easiest.
>
> why don't we get rid of the single use macro instead?
I thought it had self-documenting value as-is.
In any case, I merged this already, so follow-ups welcome. ;)
BR,
Jani.
>
>>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>> drivers/gpu/drm/i915/i915_debugfs.c | 3 +++
>> drivers/gpu/drm/i915/i915_drv.h | 2 --
>> 2 files changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
>> index a356ca490159..51ba9a8369c5 100644
>> --- a/drivers/gpu/drm/i915/i915_debugfs.c
>> +++ b/drivers/gpu/drm/i915/i915_debugfs.c
>> @@ -648,6 +648,9 @@ i915_drop_caches_get(void *data, u64 *val)
>>
>> return 0;
>> }
>> +
>> +#define I915_IDLE_ENGINES_TIMEOUT (200) /* in ms */
>> +
>> static int
>> gt_drop_caches(struct intel_gt *gt, u64 val)
>> {
>> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
>> index 8377173e8de5..343e3e568774 100644
>> --- a/drivers/gpu/drm/i915/i915_drv.h
>> +++ b/drivers/gpu/drm/i915/i915_drv.h
>> @@ -194,8 +194,6 @@ struct i915_gem_mm {
>> u32 shrink_count;
>> };
>>
>> -#define I915_IDLE_ENGINES_TIMEOUT (200) /* in ms */
>> -
>> #define HAS_HW_SAGV_WM(i915) (DISPLAY_VER(i915) >= 13 && !IS_DGFX(i915))
>>
>> struct i915_virtual_gpu {
>> --
>> 2.34.1
>>
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-01-20 10:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 13:15 [Intel-gfx] [PATCH 1/7] drm/i915: add i915_config.h and move relevant declarations there Jani Nikula
2023-01-18 13:15 ` [Intel-gfx] [PATCH 2/7] drm/i915: move I915_IDLE_ENGINES_TIMEOUT next to its only user Jani Nikula
2023-01-18 13:27 ` Tvrtko Ursulin
2023-01-20 10:32 ` Rodrigo Vivi
2023-01-20 10:39 ` Jani Nikula [this message]
2023-01-18 13:15 ` [Intel-gfx] [PATCH 3/7] drm/i915: drop a number of unnecessary forward declarations Jani Nikula
2023-01-18 13:28 ` Tvrtko Ursulin
2023-01-20 10:34 ` Rodrigo Vivi
2023-01-18 13:15 ` [Intel-gfx] [PATCH 4/7] drm/i915: move a few HAS_ macros closer to their place Jani Nikula
2023-01-20 10:36 ` Rodrigo Vivi
2023-01-18 13:15 ` [Intel-gfx] [PATCH 5/7] drm/i915: move I915_GEM_GPU_DOMAINS to i915_gem.h Jani Nikula
2023-01-18 13:27 ` Tvrtko Ursulin
2023-01-18 14:05 ` Das, Nirmoy
2023-01-20 10:40 ` Rodrigo Vivi
2023-01-18 13:15 ` [Intel-gfx] [PATCH 6/7] drm/i915: move I915_COLOR_UNEVICTABLE to i915_gem_gtt.h Jani Nikula
2023-01-18 13:28 ` Tvrtko Ursulin
2023-01-20 10:43 ` Rodrigo Vivi
2023-01-23 13:17 ` Jani Nikula
2023-01-18 13:15 ` [Intel-gfx] [PATCH 7/7] drm/i915: move GT_FREQUENCY_MULTIPLIER and GEN9_FREQ_SCALER to intel_rps.h Jani Nikula
2023-01-18 13:28 ` Tvrtko Ursulin
2023-01-18 13:32 ` [Intel-gfx] [PATCH 1/7] drm/i915: add i915_config.h and move relevant declarations there Tvrtko Ursulin
2023-01-20 8:22 ` Jani Nikula
2023-01-18 22:03 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/7] " Patchwork
2023-01-18 22:34 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-01-19 1:39 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/7] drm/i915: add i915_config.h and move relevant declarations there (rev2) Patchwork
2023-01-19 1:39 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-01-19 2:09 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-01-20 1:16 ` [Intel-gfx] ✓ 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=87v8l18p7o.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@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