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: [PATCH v2 1/3] drm/i915: Force background color to black for gen9+
Date: Wed, 14 Nov 2018 19:58:44 +0200 [thread overview]
Message-ID: <20181114175844.GT9144@intel.com> (raw)
In-Reply-To: <20181114173639.GD8652@mdroper-desk.amr.corp.intel.com>
On Wed, Nov 14, 2018 at 09:36:39AM -0800, Matt Roper wrote:
> On Wed, Nov 14, 2018 at 07:28:12PM +0200, Ville Syrjälä wrote:
> > On Tue, Nov 13, 2018 at 03:21:47PM -0800, Matt Roper wrote:
> > > We don't yet allow userspace to control the CRTC background color, but
> > > we should manually program the color to black to ensure the BIOS didn't
> > > leave us with some other color. We should also set the pipe gamma and
> > > pipe CSC bits so that the background color goes through the same color
> > > management transformations that a plane with black pixels would.
> > >
> > > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
> > > ---
> > > We may want to land this patch before the rest of the series since it's
> > > still valuable even without the new ABI the rest of the series adds.
> > >
> > > drivers/gpu/drm/i915/i915_reg.h | 6 ++++++
> > > drivers/gpu/drm/i915/intel_display.c | 18 ++++++++++++++++++
> > > 2 files changed, 24 insertions(+)
> > >
> > > diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
> > > index fe4b913e46ac..b92a721c9bcb 100644
> > > --- a/drivers/gpu/drm/i915/i915_reg.h
> > > +++ b/drivers/gpu/drm/i915/i915_reg.h
> > > @@ -5662,6 +5662,12 @@ enum {
> > > #define PIPEMISC_DITHER_TYPE_SP (0 << 2)
> > > #define PIPEMISC(pipe) _MMIO_PIPE2(pipe, _PIPE_MISC_A)
> > >
> > > +/* Skylake+ pipe bottom (background) color */
> > > +#define _SKL_CANVAS_A 0x70034
> > > +#define SKL_CANVAS_GAMMA_ENABLE (1 << 31)
> > > +#define SKL_CANVAS_CSC_ENABLE (1 << 30)
> > > +#define SKL_CANVAS(pipe) _MMIO_PIPE2(pipe, _SKL_CANVAS_A)
> >
> > Didn't the spec call this BOTTOM_COLOR or something like that?
>
> The register definition is called BOTTOM_COLOR, but other areas of the
> spec refer to this as either "background color" or "canvas color." We
> already have a CHV_CANVAS register that I believe provides the same
> functionality for CHV (although I can't find details for the bit layout
> in the spec), so I decided to just keep this name consistent with that
> one.
While CHV_CANVAS does provide simiar functionality (actually
just the color, not the gamma/csc control) it is still a
different register. IMO better to stick to the naming used
in the spec.
>
>
> Matt
>
> >
> > > +
> > > #define VLV_DPFLIPSTAT _MMIO(VLV_DISPLAY_BASE + 0x70028)
> > > #define PIPEB_LINE_COMPARE_INT_EN (1 << 29)
> > > #define PIPEB_HLINE_INT_EN (1 << 28)
> > > diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> > > index 132e978227fb..1d089d93d88b 100644
> > > --- a/drivers/gpu/drm/i915/intel_display.c
> > > +++ b/drivers/gpu/drm/i915/intel_display.c
> > > @@ -3868,6 +3868,15 @@ static void intel_update_pipe_config(const struct intel_crtc_state *old_crtc_sta
> > > else if (old_crtc_state->pch_pfit.enabled)
> > > ironlake_pfit_disable(old_crtc_state);
> > > }
> > > +
> > > + /*
> > > + * We don't (yet) allow userspace to control the pipe background color,
> > > + * so force it to black, but apply pipe gamma and CSC so that its
> > > + * handling will match how we program our planes.
> > > + */
> > > + if (INTEL_GEN(dev_priv) >= 9)
> > > + I915_WRITE(SKL_CANVAS(crtc->pipe),
> > > + SKL_CANVAS_GAMMA_ENABLE | SKL_CANVAS_CSC_ENABLE);
> > > }
> > >
> > > static void intel_fdi_normal_train(struct intel_crtc *crtc)
> > > @@ -15356,6 +15365,15 @@ static void intel_sanitize_crtc(struct intel_crtc *crtc,
> > > plane->base.type != DRM_PLANE_TYPE_PRIMARY)
> > > intel_plane_disable_noatomic(crtc, plane);
> > > }
> > > +
> > > + /*
> > > + * Disable any background color set by the BIOS, but enable the
> > > + * gamma and CSC to match how we program our planes.
> > > + */
> > > + if (INTEL_GEN(dev_priv) >= 9)
> > > + I915_WRITE(SKL_CANVAS(crtc->pipe),
> > > + SKL_CANVAS_GAMMA_ENABLE |
> > > + SKL_CANVAS_CSC_ENABLE);
> > > }
> > >
> > > /* Adjust the state of the output pipe according to whether we
> > > --
> > > 2.14.4
> >
> > --
> > Ville Syrjälä
> > Intel
>
> --
> Matt Roper
> Graphics Software Engineer
> IoTG Platform Enabling & Development
> Intel Corporation
> (916) 356-2795
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-11-14 17:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 23:21 [PATCH v2 0/3] CRTC background color Matt Roper
2018-11-13 23:21 ` [PATCH v2 1/3] drm/i915: Force background color to black for gen9+ Matt Roper
2018-11-14 17:28 ` Ville Syrjälä
2018-11-14 17:36 ` Matt Roper
2018-11-14 17:58 ` Ville Syrjälä [this message]
2018-11-13 23:21 ` [PATCH v2 2/3] drm: Add CRTC background color property (v2) Matt Roper
2018-11-14 16:17 ` Sean Paul
2018-11-15 0:27 ` Matt Roper
2018-11-14 17:20 ` Ville Syrjälä
2018-11-14 17:29 ` Matt Roper
2018-11-13 23:21 ` [PATCH v2 3/3] drm/i915/gen9+: Add support for pipe background color (v2) Matt Roper
2018-11-14 18:05 ` Ville Syrjälä
2018-11-13 23:22 ` [igt-dev] [PATCH i-g-t v2] tests/kms_crtc_background_color: overhaul for latest ABI proposal (v2) Matt Roper
2018-11-13 23:22 ` Matt Roper
2018-11-13 23:43 ` [igt-dev] [Intel-gfx] " Lionel Landwerlin
2018-11-13 23:43 ` Lionel Landwerlin
2018-11-13 23:53 ` [igt-dev] [Intel-gfx] " Matt Roper
2018-11-13 23:53 ` Matt Roper
2018-11-13 23:31 ` ✗ Fi.CI.CHECKPATCH: warning for CRTC background color (rev2) Patchwork
2018-11-13 23:58 ` ✓ Fi.CI.BAT: success " Patchwork
2018-11-14 1:34 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_crtc_background_color: overhaul for latest ABI proposal (v2) Patchwork
2018-11-14 4:48 ` [igt-dev] ✗ 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=20181114175844.GT9144@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 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.