Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ghimiray, Himal Prasad" <himal.prasad.ghimiray@intel.com>
To: "Upadhyay, Tejas" <tejas.upadhyay@intel.com>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
	"De Marchi, Lucas" <lucas.demarchi@intel.com>
Cc: "Wajdeczko, Michal" <Michal.Wajdeczko@intel.com>
Subject: Re: [PATCH 1/2] drm/xe: Delete unused register from xe_regs.h
Date: Mon, 22 Jul 2024 10:42:23 +0530	[thread overview]
Message-ID: <27476ff3-3cdb-4b51-add4-4e071986a5b2@intel.com> (raw)
In-Reply-To: <SJ1PR11MB620416EAAE7A6BAE9368159881A82@SJ1PR11MB6204.namprd11.prod.outlook.com>



On 22-07-2024 10:23, Upadhyay, Tejas wrote:
> 
> 
>> -----Original Message-----
>> From: Intel-xe <intel-xe-bounces@lists.freedesktop.org> On Behalf Of Himal
>> Prasad Ghimiray
>> Sent: Monday, July 15, 2024 4:26 PM
>> To: intel-xe@lists.freedesktop.org
>> Cc: Ghimiray, Himal Prasad <himal.prasad.ghimiray@intel.com>; Wajdeczko,
>> Michal <Michal.Wajdeczko@intel.com>
>> Subject: [PATCH 1/2] drm/xe: Delete unused register from xe_regs.h
>>
>> Register SOFTWARE_FLAGS_SPR33 is unused; therefore, delete it.
>>
>> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
>> Signed-off-by: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
>> ---
>>   drivers/gpu/drm/xe/regs/xe_regs.h | 2 --
>>   1 file changed, 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/xe/regs/xe_regs.h
>> b/drivers/gpu/drm/xe/regs/xe_regs.h
>> index 55bf47c99016..dfa869f0dddd 100644
>> --- a/drivers/gpu/drm/xe/regs/xe_regs.h
>> +++ b/drivers/gpu/drm/xe/regs/xe_regs.h
>> @@ -15,8 +15,6 @@
>>   #define GU_MISC_IRQ_OFFSET			0x444f0
>>   #define   GU_MISC_GSE				REG_BIT(27)
>>
>> -#define SOFTWARE_FLAGS_SPR33			XE_REG(0x4f084)
> 
> @De Marchi, Lucas I see you added specifically this register in below commit, was there any purpose ? To me it looks fine to remove.
> 
> commit 8cb49012ac171698b1253dea45e56c284e997d38
> Author: Lucas De Marchi <lucas.demarchi@intel.com>
> Date:   Sat Feb 25 12:10:39 2023 -0800
> 
>      drm/xe: Do not spread i915_reg_defs.h include
> 
>      Reduce the use of i915_reg_defs.h so it can be encapsulated in a single
>      place.
> 

The register was being used for ensuring write barriers in dgfx earlier. 
Which is modified to use VF_CAP regs now.

For background of the register usage.
https://lore.kernel.org/intel-xe/20240702183704.1022-4-michal.wajdeczko@intel.com/ 



> If no concerns from Lucas, then
> Reviewed-by: Tejas Upadhyay <tejas.upadhyay@intel.com>
> 
> Thanks,
> Tejas
>> -
>>   #define GU_CNTL_PROTECTED			XE_REG(0x10100C)
>>   #define   DRIVERINT_FLR_DIS			REG_BIT(31)
>>
>> --
>> 2.34.1
> 

  reply	other threads:[~2024-07-22  5:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-15 10:55 [PATCH 0/2] Minor cleanups Himal Prasad Ghimiray
2024-07-15 10:45 ` ✓ CI.Patch_applied: success for " Patchwork
2024-07-15 10:46 ` ✓ CI.checkpatch: " Patchwork
2024-07-15 10:47 ` ✓ CI.KUnit: " Patchwork
2024-07-15 10:55 ` [PATCH 1/2] drm/xe: Delete unused register from xe_regs.h Himal Prasad Ghimiray
2024-07-22  4:53   ` Upadhyay, Tejas
2024-07-22  5:12     ` Ghimiray, Himal Prasad [this message]
2024-07-24 17:53       ` Lucas De Marchi
2024-07-15 10:55 ` [PATCH 2/2] drm/xe: Remove function xe_device_canonicalize_addr Himal Prasad Ghimiray
2024-07-15 14:05   ` Souza, Jose
2024-07-15 17:56     ` Ghimiray, Himal Prasad
2024-07-15 18:14       ` Souza, Jose
2024-07-20 19:15         ` Ghimiray, Himal Prasad
2024-07-25 13:15           ` Francois Dugast
2024-07-15 10:59 ` ✓ CI.Build: success for Minor cleanups Patchwork
2024-07-15 11:01 ` ✓ CI.Hooks: " Patchwork
2024-07-15 11:02 ` ✓ CI.checksparse: " Patchwork
2024-07-15 11:26 ` ✓ CI.BAT: " Patchwork
2024-07-15 12:58 ` ✗ CI.FULL: failure " 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=27476ff3-3cdb-4b51-add4-4e071986a5b2@intel.com \
    --to=himal.prasad.ghimiray@intel.com \
    --cc=Michal.Wajdeczko@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=tejas.upadhyay@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