From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Uma Shankar <uma.shankar@intel.com>
Cc: intel-gfx@lists.freedesktop.org, ville.syrjala@intel.com,
maarten.lankhorst@intel.com
Subject: Re: [v2 0/2] Fixed GC MAX register programming for gamma luts
Date: Fri, 29 Mar 2019 20:32:38 +0200 [thread overview]
Message-ID: <20190329183238.GG3888@intel.com> (raw)
In-Reply-To: <1553869756-4546-1-git-send-email-uma.shankar@intel.com>
On Fri, Mar 29, 2019 at 07:59:14PM +0530, Uma Shankar wrote:
> Register offsets used to program GC max were not correct. This series
> fixes the same, also limits the values to accurately clamp at 1.0.
> Also added support to program EXT2 GC Max needed for values from 3.0
> to 7.0. Limiting it again to 1.0 due to ABI limitations.
>
> v2: Addressed Ville's review comments.
>
> Uma Shankar (2):
> drm/i915: Fix GCMAX color register programming
> drm/i915: Program EXT2 GC MAX registers
Both pushed to dinq. Thanks.
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2019-03-29 18:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 14:29 [v2 0/2] Fixed GC MAX register programming for gamma luts Uma Shankar
2019-03-29 14:29 ` [v2 1/2] drm/i915: Fix GCMAX color register programming Uma Shankar
2019-03-29 14:29 ` [v2 2/2] drm/i915: Program EXT2 GC MAX registers Uma Shankar
2019-03-29 14:30 ` [v2 0/2] Fixed GC MAX register programming for gamma luts Lionel Landwerlin
2019-03-29 14:49 ` Shankar, Uma
2019-03-29 14:36 ` ✗ Fi.CI.CHECKPATCH: warning for Fixed GC MAX register programming for gamma luts (rev2) Patchwork
2019-03-29 15:02 ` ✓ Fi.CI.BAT: success " Patchwork
2019-03-29 18:17 ` ✓ Fi.CI.IGT: " Patchwork
2019-03-29 18:32 ` Ville Syrjälä [this message]
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=20190329183238.GG3888@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@intel.com \
--cc=uma.shankar@intel.com \
--cc=ville.syrjala@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.