Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 4/5] drm/i915: Make HW readout mark CRTC scaler as in use.
Date: Tue,  8 Jan 2019 17:08:41 +0100	[thread overview]
Message-ID: <20190108160842.13396-4-maarten.lankhorst@linux.intel.com> (raw)
In-Reply-To: <20190108160842.13396-1-maarten.lankhorst@linux.intel.com>

This way we don't accidentally double allocate it.
Noticed this when I wrote a patch to sanity check all of
the scaler state.

Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
---
 drivers/gpu/drm/i915/intel_display.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
index f8cbdd50fa38..f902f720a3fb 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -8869,6 +8869,7 @@ static void skylake_get_pfit_config(struct intel_crtc *crtc,
 			pipe_config->pch_pfit.enabled = true;
 			pipe_config->pch_pfit.pos = I915_READ(SKL_PS_WIN_POS(crtc->pipe, i));
 			pipe_config->pch_pfit.size = I915_READ(SKL_PS_WIN_SZ(crtc->pipe, i));
+			scaler_state->scalers[i].in_use = true;
 			break;
 		}
 	}
-- 
2.20.1

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-01-08 16:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-08 16:08 [PATCH 1/5] drm/i915/backlight: Restore backlight on resume, v3 Maarten Lankhorst
2019-01-08 16:08 ` [PATCH 2/5] drm/i915/backlight: Fix backlight takeover on LPT, v3 Maarten Lankhorst
2019-01-22  6:21   ` Hans de Goede
2019-01-22 17:44   ` Jani Nikula
2019-01-08 16:08 ` [PATCH 3/5] drm/i915: Enable fastset for non-boot modesets Maarten Lankhorst
2019-01-22  6:21   ` Hans de Goede
2019-01-22 17:45   ` Jani Nikula
2019-01-08 16:08 ` Maarten Lankhorst [this message]
2019-01-08 16:08 ` [PATCH 5/5] drm/i915: Re-enable fastset by default Maarten Lankhorst
2019-01-22  6:22   ` Hans de Goede
2019-01-08 17:51 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/5] drm/i915/backlight: Restore backlight on resume, v3 Patchwork
2019-01-08 17:53 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-01-08 18:12 ` ✓ Fi.CI.BAT: success " Patchwork
2019-01-09  4:46 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-01-09 10:32 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/5] drm/i915/backlight: Restore backlight on resume, v3. (rev2) Patchwork
2019-01-09 10:34 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-01-09 11:21 ` ✓ Fi.CI.BAT: success " Patchwork
2019-01-09 13:10 ` ✓ Fi.CI.IGT: " Patchwork
2019-01-21 14:30 ` [PATCH 1/5] drm/i915/backlight: Restore backlight on resume, v3 Hans de Goede
2019-01-22 17:43 ` Jani Nikula
  -- strict thread matches above, loose matches on Subject: below --
2018-12-17  9:50 [RESEND PATCH 1/5] drm/i915/backlight: Restore backlight on resume, v2 Maarten Lankhorst
2018-12-17  9:50 ` [PATCH 4/5] drm/i915: Make HW readout mark CRTC scaler as in use Maarten Lankhorst

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=20190108160842.13396-4-maarten.lankhorst@linux.intel.com \
    --to=maarten.lankhorst@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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