From: Jani Nikula <jani.nikula@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/gt: drop dependency on VLV_DISPLAY_BASE
Date: Thu, 11 May 2023 15:31:16 +0300 [thread overview]
Message-ID: <87sfc3kq23.fsf@intel.com> (raw)
In-Reply-To: <ZFzddTOx2QciRfXE@intel.com>
On Thu, 11 May 2023, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Thu, May 11, 2023 at 12:04:27PM +0300, Jani Nikula wrote:
>> CHV_FUSE_GT (0x182168) is purely about GT fuses, therefore belongs in
>> intel_gt_regs.h, is in the gcfgmmio unit, but is technically in the VLV
>> display base area.
>>
>> Use the 0x182168 MMIO address directly to drop dependency on
>> VLV_DISPLAY_BASE and thus display/intel_display_reg_defs.h in
>> intel_gt_regs.h.
>>
>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>> drivers/gpu/drm/i915/gt/intel_gt_regs.h | 3 +--
>> 1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/gt/intel_gt_regs.h b/drivers/gpu/drm/i915/gt/intel_gt_regs.h
>> index b8a39c219b60..f38550dae6b8 100644
>> --- a/drivers/gpu/drm/i915/gt/intel_gt_regs.h
>> +++ b/drivers/gpu/drm/i915/gt/intel_gt_regs.h
>> @@ -7,7 +7,6 @@
>> #define __INTEL_GT_REGS__
>>
>> #include "i915_reg_defs.h"
>> -#include "display/intel_display_reg_defs.h" /* VLV_DISPLAY_BASE */
>>
>> /*
>> * The perf control registers are technically multicast registers, but the
>> @@ -1469,7 +1468,7 @@
>> #define GEN12_RCU_MODE _MMIO(0x14800)
>> #define GEN12_RCU_MODE_CCS_ENABLE REG_BIT(0)
>>
>> -#define CHV_FUSE_GT _MMIO(VLV_DISPLAY_BASE + 0x2168)
>> +#define CHV_FUSE_GT _MMIO(0x182168)
>
> Or mmaybe s/VLV_DISPLAY_BASE/VLV_GUNIT_BASE/ here? Although all the
> other Gunit register defintions are still in i915_reg.h, and using
> VLV_DISPLAY_BASE. Not sure what to do about all that...
Works for me, as long as I can drop the dependency on
display/intel_display_reg_defs.h.
Just let me know.
BR,
Jani.
>
>> #define CHV_FGT_DISABLE_SS0 (1 << 10)
>> #define CHV_FGT_DISABLE_SS1 (1 << 11)
>> #define CHV_FGT_EU_DIS_SS0_R0_SHIFT 16
>> --
>> 2.39.2
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-05-11 12:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 9:04 [Intel-gfx] [PATCH] drm/i915/gt: drop dependency on VLV_DISPLAY_BASE Jani Nikula
2023-05-11 11:00 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-05-11 12:20 ` [Intel-gfx] [PATCH] " Ville Syrjälä
2023-05-11 12:31 ` Jani Nikula [this message]
2023-05-11 12:33 ` Ville Syrjälä
2023-05-11 12:46 ` Jani Nikula
2023-05-11 14:15 ` Ville Syrjälä
2023-05-11 13:30 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " 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=87sfc3kq23.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.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 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.