Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Kalvala, Haridhar" <haridhar.kalvala@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/i915: Eliminate has_4tile feature flag
Date: Wed, 16 Aug 2023 21:34:07 +0530	[thread overview]
Message-ID: <6ca21583-6ada-af0e-25c1-244f6de43ee6@intel.com> (raw)
In-Reply-To: <20230816151823.GQ209733@mdroper-desk1.amr.corp.intel.com>


On 8/16/2023 8:48 PM, Matt Roper wrote:
> On Wed, Aug 16, 2023 at 12:16:25PM +0530, Kalvala, Haridhar wrote:
>> On 8/11/2023 5:16 AM, Matt Roper wrote:
>>> We don't really need a feature flag for has_4tile since there's a
>>> well-defined cutover point (DG2) at which all new platforms started
>>> using Tile4 as their Y-major tiling layout.  The GT side of the code
>>> already handles Tile4 vs legacy TileY with checks on the IP version
>>> rather than looking at the feature flag, and we can simplify the display
>>> code similarly (which will also make it more self-contained for re-use
>>> in the Xe driver).
>> Hi Matt,
>>
>> Looks good to me.
Reviewed-by: Haridhar Kalvala <haridhar.kalvala@intel.com>
>>> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
>>> ---
>>>    drivers/gpu/drm/i915/display/intel_display_device.h | 1 +
>>>    drivers/gpu/drm/i915/i915_drv.h                     | 1 -
>>>    drivers/gpu/drm/i915/i915_pci.c                     | 1 -
>>>    drivers/gpu/drm/i915/intel_device_info.h            | 1 -
>>>    4 files changed, 1 insertion(+), 3 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/i915/display/intel_display_device.h b/drivers/gpu/drm/i915/display/intel_display_device.h
>>> index 215e682bd8b7..eb630a946343 100644
>>> --- a/drivers/gpu/drm/i915/display/intel_display_device.h
>>> +++ b/drivers/gpu/drm/i915/display/intel_display_device.h
>>> @@ -32,6 +32,7 @@ struct drm_printer;
>>>    	func(overlay_needs_physical); \
>>>    	func(supports_tv);
>>> +#define HAS_4TILE(i915)			(IS_DG2(i915) || DISPLAY_VER(i915) >= 14)
>> is this tab space aligned with below lines ?
> Yes, it's aligned with the code below.  But if you're just reading the
> diff, the extra column added for the '+' at the beginning of the line
> throws off the spacing.
>
>
> Matt
>
>>>    #define HAS_ASYNC_FLIPS(i915)		(DISPLAY_VER(i915) >= 5)
>>>    #define HAS_CDCLK_CRAWL(i915)		(DISPLAY_INFO(i915)->has_cdclk_crawl)
>>>    #define HAS_CDCLK_SQUASH(i915)		(DISPLAY_INFO(i915)->has_cdclk_squash)
>>> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
>>> index 7a8ce7239bc9..4c6852f0a61c 100644
>>> --- a/drivers/gpu/drm/i915/i915_drv.h
>>> +++ b/drivers/gpu/drm/i915/i915_drv.h
>>> @@ -737,7 +737,6 @@ IS_SUBPLATFORM(const struct drm_i915_private *i915,
>>>    #define CMDPARSER_USES_GGTT(i915) (GRAPHICS_VER(i915) == 7)
>>>    #define HAS_LLC(i915)	(INTEL_INFO(i915)->has_llc)
>>> -#define HAS_4TILE(i915)	(INTEL_INFO(i915)->has_4tile)
>>>    #define HAS_SNOOP(i915)	(INTEL_INFO(i915)->has_snoop)
>>>    #define HAS_EDRAM(i915)	((i915)->edram_size_mb)
>>>    #define HAS_SECURE_BATCHES(i915) (GRAPHICS_VER(i915) < 6)
>>> diff --git a/drivers/gpu/drm/i915/i915_pci.c b/drivers/gpu/drm/i915/i915_pci.c
>>> index fcacdc21643c..df7c261410f7 100644
>>> --- a/drivers/gpu/drm/i915/i915_pci.c
>>> +++ b/drivers/gpu/drm/i915/i915_pci.c
>>> @@ -713,7 +713,6 @@ static const struct intel_device_info adl_p_info = {
>>>    	.has_3d_pipeline = 1, \
>>>    	.has_64bit_reloc = 1, \
>>>    	.has_flat_ccs = 1, \
>>> -	.has_4tile = 1, \
>>>    	.has_global_mocs = 1, \
>>>    	.has_gt_uc = 1, \
>>>    	.has_llc = 1, \
>>> diff --git a/drivers/gpu/drm/i915/intel_device_info.h b/drivers/gpu/drm/i915/intel_device_info.h
>>> index dbfe6443457b..19d120728ff1 100644
>>> --- a/drivers/gpu/drm/i915/intel_device_info.h
>>> +++ b/drivers/gpu/drm/i915/intel_device_info.h
>>> @@ -150,7 +150,6 @@ enum intel_ppgtt_type {
>>>    	func(gpu_reset_clobbers_display); \
>>>    	func(has_reset_engine); \
>>>    	func(has_3d_pipeline); \
>>> -	func(has_4tile); \
>>>    	func(has_flat_ccs); \
>>>    	func(has_global_mocs); \
>>>    	func(has_gmd_id); \
>> -- 
>> Regards,
>> Haridhar Kalvala
>>
-- 
Regards,
Haridhar Kalvala


  reply	other threads:[~2023-08-16 16:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10 23:46 [Intel-gfx] [PATCH 1/2] drm/i915/selftest: Simplify Y-major tiling in blit selftest Matt Roper
2023-08-10 23:46 ` [Intel-gfx] [PATCH 2/2] drm/i915: Eliminate has_4tile feature flag Matt Roper
2023-08-16  6:46   ` Kalvala, Haridhar
2023-08-16 15:18     ` Matt Roper
2023-08-16 16:04       ` Kalvala, Haridhar [this message]
2023-08-11  2:20 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915/selftest: Simplify Y-major tiling in blit selftest Patchwork
2023-08-11  2:20 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-08-11  2:39 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-08-11 18:43 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915/selftest: Simplify Y-major tiling in blit selftest (rev2) Patchwork
2023-08-11 18:44 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-08-11 18:59 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-08-12  0:34 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915/selftest: Simplify Y-major tiling in blit selftest (rev3) Patchwork
2023-08-12  0:34 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-08-12  0:45 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-08-13  7:19 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-08-17 22:45   ` Matt Roper
2023-08-16  6:40 ` [Intel-gfx] [PATCH 1/2] drm/i915/selftest: Simplify Y-major tiling in blit selftest Kalvala, Haridhar
2023-08-16 16:12   ` Kalvala, Haridhar

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=6ca21583-6ada-af0e-25c1-244f6de43ee6@intel.com \
    --to=haridhar.kalvala@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.d.roper@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