From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 3/5] drm/i915: Extract mchbar_reg()
Date: Thu, 02 Nov 2023 15:31:16 +0200 [thread overview]
Message-ID: <87bkcc2sez.fsf@intel.com> (raw)
In-Reply-To: <20231101114212.9345-4-ville.syrjala@linux.intel.com>
On Wed, 01 Nov 2023, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Stop repeating the same logic to determine the correct
> config space register for MCHBAR.
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/soc/intel_gmch.c | 27 ++++++++++++++-------------
> 1 file changed, 14 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/soc/intel_gmch.c b/drivers/gpu/drm/i915/soc/intel_gmch.c
> index f32e9f78770a..40874ebfb64c 100644
> --- a/drivers/gpu/drm/i915/soc/intel_gmch.c
> +++ b/drivers/gpu/drm/i915/soc/intel_gmch.c
> @@ -33,18 +33,22 @@ int intel_gmch_bridge_setup(struct drm_i915_private *i915)
> i915->gmch.pdev);
> }
>
> +static int mchbar_reg(struct drm_i915_private *i915)
> +{
> + return GRAPHICS_VER(i915) >= 4 ? MCHBAR_I965 : MCHBAR_I915;
> +}
> +
> /* Allocate space for the MCH regs if needed, return nonzero on error */
> static int
> intel_alloc_mchbar_resource(struct drm_i915_private *i915)
> {
> - int reg = GRAPHICS_VER(i915) >= 4 ? MCHBAR_I965 : MCHBAR_I915;
> u32 temp_lo, temp_hi = 0;
> u64 mchbar_addr;
> int ret;
>
> if (GRAPHICS_VER(i915) >= 4)
> - pci_read_config_dword(i915->gmch.pdev, reg + 4, &temp_hi);
> - pci_read_config_dword(i915->gmch.pdev, reg, &temp_lo);
> + pci_read_config_dword(i915->gmch.pdev, mchbar_reg(i915) + 4, &temp_hi);
How about having mchbar_hi_reg() and mchbar_lo_reg(), and drop the magic
+ 4 here and there?
Either way,
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> + pci_read_config_dword(i915->gmch.pdev, mchbar_reg(i915), &temp_lo);
> mchbar_addr = ((u64)temp_hi << 32) | temp_lo;
>
> /* If ACPI doesn't have it, assume we need to allocate it ourselves */
> @@ -68,10 +72,10 @@ intel_alloc_mchbar_resource(struct drm_i915_private *i915)
> }
>
> if (GRAPHICS_VER(i915) >= 4)
> - pci_write_config_dword(i915->gmch.pdev, reg + 4,
> + pci_write_config_dword(i915->gmch.pdev, mchbar_reg(i915) + 4,
> upper_32_bits(i915->gmch.mch_res.start));
>
> - pci_write_config_dword(i915->gmch.pdev, reg,
> + pci_write_config_dword(i915->gmch.pdev, mchbar_reg(i915),
> lower_32_bits(i915->gmch.mch_res.start));
> return 0;
> }
> @@ -79,7 +83,6 @@ intel_alloc_mchbar_resource(struct drm_i915_private *i915)
> /* Setup MCHBAR if possible, return true if we should disable it again */
> void intel_gmch_bar_setup(struct drm_i915_private *i915)
> {
> - int mchbar_reg = GRAPHICS_VER(i915) >= 4 ? MCHBAR_I965 : MCHBAR_I915;
> u32 temp;
> bool enabled;
>
> @@ -92,7 +95,7 @@ void intel_gmch_bar_setup(struct drm_i915_private *i915)
> pci_read_config_dword(i915->gmch.pdev, DEVEN, &temp);
> enabled = !!(temp & DEVEN_MCHBAR_EN);
> } else {
> - pci_read_config_dword(i915->gmch.pdev, mchbar_reg, &temp);
> + pci_read_config_dword(i915->gmch.pdev, mchbar_reg(i915), &temp);
> enabled = temp & 1;
> }
>
> @@ -110,15 +113,13 @@ void intel_gmch_bar_setup(struct drm_i915_private *i915)
> pci_write_config_dword(i915->gmch.pdev, DEVEN,
> temp | DEVEN_MCHBAR_EN);
> } else {
> - pci_read_config_dword(i915->gmch.pdev, mchbar_reg, &temp);
> - pci_write_config_dword(i915->gmch.pdev, mchbar_reg, temp | 1);
> + pci_read_config_dword(i915->gmch.pdev, mchbar_reg(i915), &temp);
> + pci_write_config_dword(i915->gmch.pdev, mchbar_reg(i915), temp | 1);
> }
> }
>
> void intel_gmch_bar_teardown(struct drm_i915_private *i915)
> {
> - int mchbar_reg = GRAPHICS_VER(i915) >= 4 ? MCHBAR_I965 : MCHBAR_I915;
> -
> if (i915->gmch.mchbar_need_disable) {
> if (IS_I915G(i915) || IS_I915GM(i915)) {
> u32 deven_val;
> @@ -131,10 +132,10 @@ void intel_gmch_bar_teardown(struct drm_i915_private *i915)
> } else {
> u32 mchbar_val;
>
> - pci_read_config_dword(i915->gmch.pdev, mchbar_reg,
> + pci_read_config_dword(i915->gmch.pdev, mchbar_reg(i915),
> &mchbar_val);
> mchbar_val &= ~1;
> - pci_write_config_dword(i915->gmch.pdev, mchbar_reg,
> + pci_write_config_dword(i915->gmch.pdev, mchbar_reg(i915),
> mchbar_val);
> }
> }
--
Jani Nikula, Intel
next prev parent reply other threads:[~2023-11-02 13:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 11:42 [Intel-gfx] [PATCH 0/5] drm/i915: Some register cleanups Ville Syrjala
2023-11-01 11:42 ` [Intel-gfx] [PATCH 1/5] drm/i915: Extract hsw_chicken_trans_reg() Ville Syrjala
2023-11-02 13:29 ` Jani Nikula
2023-11-01 11:42 ` [Intel-gfx] [PATCH 2/5] drm/i915: Stop using a 'reg' variable Ville Syrjala
2023-11-02 13:29 ` Jani Nikula
2023-11-01 11:42 ` [Intel-gfx] [PATCH 3/5] drm/i915: Extract mchbar_reg() Ville Syrjala
2023-11-02 13:31 ` Jani Nikula [this message]
2023-11-06 8:07 ` Ville Syrjälä
2023-11-01 11:42 ` [Intel-gfx] [PATCH 4/5] drm/i915/dsi: Remove dead GLK checks Ville Syrjala
2023-11-02 13:32 ` Jani Nikula
2023-11-01 11:42 ` [Intel-gfx] [PATCH 5/5] drm/i915/dsi: Extract port_ctrl_reg() Ville Syrjala
2023-11-02 13:32 ` Jani Nikula
2023-11-01 14:31 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Some register cleanups Patchwork
2023-11-01 14:31 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-11-01 14:50 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-11-04 16:45 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Some register cleanups (rev2) Patchwork
2023-11-04 16:45 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-11-04 17:02 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-11-04 17:53 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Some register cleanups (rev3) Patchwork
2023-11-04 17:53 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-11-04 18:06 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-11-04 19:37 ` [Intel-gfx] ✗ Fi.CI.IGT: 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=87bkcc2sez.fsf@intel.com \
--to=jani.nikula@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox