From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 1/2] drm/i915: Define MCH registers relative to MCHBAR_MIRROR_BASE
Date: Wed, 16 Feb 2022 10:41:57 +0200 [thread overview]
Message-ID: <Ygy41YWHyQR3yz8I@intel.com> (raw)
In-Reply-To: <20220215061342.2055952-1-matthew.d.roper@intel.com>
On Mon, Feb 14, 2022 at 10:13:41PM -0800, Matt Roper wrote:
> A few of our MCH registers are defined with absolute register offsets.
> For consistency, let's switch their definitions to be relative offsets
> from MCHBAR_MIRROR_BASE.
>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
Looks correct to my eyes.
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/i915_reg.h | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
> index 4ea1713e6b60..72cb6e13b4e2 100644
> --- a/drivers/gpu/drm/i915/i915_reg.h
> +++ b/drivers/gpu/drm/i915/i915_reg.h
> @@ -1922,16 +1922,16 @@
> #define HPLLVCO _MMIO(MCHBAR_MIRROR_BASE + 0xc38)
> #define HPLLVCO_MOBILE _MMIO(MCHBAR_MIRROR_BASE + 0xc0f)
>
> -#define TSC1 _MMIO(0x11001)
> +#define TSC1 _MMIO(MCHBAR_MIRROR_BASE + 0x1001)
> #define TSE (1 << 0)
> -#define TR1 _MMIO(0x11006)
> -#define TSFS _MMIO(0x11020)
> +#define TR1 _MMIO(MCHBAR_MIRROR_BASE + 0x1006)
> +#define TSFS _MMIO(MCHBAR_MIRROR_BASE + 0x1020)
> #define TSFS_SLOPE_MASK 0x0000ff00
> #define TSFS_SLOPE_SHIFT 8
> #define TSFS_INTR_MASK 0x000000ff
>
> -#define CSIPLL0 _MMIO(0x12c10)
> -#define DDRMPLL1 _MMIO(0X12c20)
> +#define CSIPLL0 _MMIO(MCHBAR_MIRROR_BASE + 0x2c10)
> +#define DDRMPLL1 _MMIO(MCHBAR_MIRROR_BASE + 0x2c20)
> #define PEG_BAND_GAP_DATA _MMIO(0x14d68)
>
> #define GEN6_GT_PERF_STATUS _MMIO(MCHBAR_MIRROR_BASE_SNB + 0x5948)
> @@ -4320,7 +4320,7 @@
> ((fbc) << WM1_LP_FBC_SHIFT) | ((pri) << WM1_LP_SR_SHIFT) | (cur))
>
> /* Memory latency timer register */
> -#define MLTR_ILK _MMIO(0x11222)
> +#define MLTR_ILK _MMIO(MCHBAR_MIRROR_BASE + 0x1222)
> #define MLTR_WM1_SHIFT 0
> #define MLTR_WM2_SHIFT 8
> /* the unit of memory self-refresh latency time is 0.5us */
> --
> 2.34.1
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2022-02-16 8:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 6:13 [Intel-gfx] [PATCH v2 1/2] drm/i915: Define MCH registers relative to MCHBAR_MIRROR_BASE Matt Roper
2022-02-15 6:13 ` [Intel-gfx] [PATCH v2 2/2] drm/i915: Move MCHBAR registers to their own header Matt Roper
2022-02-16 8:49 ` Ville Syrjälä
2022-02-16 6:06 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v2,1/2] drm/i915: Define MCH registers relative to MCHBAR_MIRROR_BASE Patchwork
2022-02-16 6:07 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-02-16 6:38 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-02-16 8:41 ` Ville Syrjälä [this message]
2022-02-16 11:22 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-02-16 20:56 ` Matt Roper
2022-02-22 17:36 ` Vudum, Lakshminarayana
2022-02-22 17:26 ` [Intel-gfx] ✓ Fi.CI.IGT: success " 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=Ygy41YWHyQR3yz8I@intel.com \
--to=ville.syrjala@linux.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