All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Sharma, Swati2" <swati2.sharma@intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: daniel.vetter@ffwll.ch, ankit.k.nautiyal@intel.com
Subject: Re: [v2][PATCH 2/3] drm/i915/display: Extract icl_read_luts()
Date: Thu, 19 Sep 2019 15:31:18 +0300	[thread overview]
Message-ID: <878sqkwjqh.fsf@intel.com> (raw)
In-Reply-To: <3ae3fa32-8050-574d-5942-5e38796cc21d@intel.com>

On Wed, 18 Sep 2019, "Sharma, Swati2" <swati2.sharma@intel.com> wrote:
> On 18-Sep-19 3:31 PM, Jani Nikula wrote:
>> On Tue, 17 Sep 2019, Swati Sharma <swati2.sharma@intel.com> wrote:
>>> For icl+, have hw read out to create hw blob of gamma
>>> lut values. icl+ platforms supports multi segmented gamma
>>> mode, add hw lut creation for this mode.
>>>
>>> This will be used to validate gamma programming using dsb
>>> (display state buffer) which is a tgl feature.
>>>
>>> v2: -readout code for multisegmented gamma has to come
>>>       up with some intermediate entries that aren't preserved
>>>       in hardware (Jani N)
>>>      -linear interpolation (Ville)
>>>      -moved common code to check gamma_enable to specific funcs,
>>>       since icl doesn't support that
>>>
>>> Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
>>> ---
>>>   drivers/gpu/drm/i915/display/intel_color.c | 243 ++++++++++++++++++++++++++---
>>>   drivers/gpu/drm/i915/i915_reg.h            |   7 +
>>>   2 files changed, 230 insertions(+), 20 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/i915/display/intel_color.c b/drivers/gpu/drm/i915/display/intel_color.c
>>> index b1f0f7e..0008011 100644
>>> --- a/drivers/gpu/drm/i915/display/intel_color.c
>>> +++ b/drivers/gpu/drm/i915/display/intel_color.c
>>> @@ -1370,6 +1370,9 @@ static int icl_color_check(struct intel_crtc_state *crtc_state)
>>>   
>>>   static int i9xx_gamma_precision(const struct intel_crtc_state *crtc_state)
>>>   {
>>> +	if (!crtc_state->gamma_enable)
>>> +		return 0;    >> +
>> 
>> Why are you moving these checks back to the individual functions?
> As stated in commit message, moved common code to check gamma_enable to 
> specific funcs, since icl doesn't support gamma_enable and code will 
> return 0. If i need to make it generic, i need to make gamma_enable true 
> in icl_color_check() func. Is it fine? ICL enables gamma through 
> gamma_mode unlike other platforms.

Argh. Right. Okay, let's go with what you have in this patch. We can
clean this stuff up later.

Please write the main part of the commit message such that it is
independent of the changelog. The changelog is good, but the actual
changes need to be evident from the message part.

BR,
Jani.

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-09-19 12:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-17 12:48 [v2][PATCH 0/3] adding gamma state checker for icl+ platforms Swati Sharma
2019-09-17 12:48 ` [v2][PATCH 1/3] drm/i915/display: Fix formatting issues Swati Sharma
2019-09-18  8:13   ` Jani Nikula
2019-09-17 12:48 ` [v2][PATCH 2/3] drm/i915/display: Extract icl_read_luts() Swati Sharma
2019-09-18 10:01   ` Jani Nikula
2019-09-18 11:30     ` Sharma, Swati2
2019-09-19 12:31       ` Jani Nikula [this message]
2019-09-19 17:30         ` Sharma, Swati2
2019-09-17 12:48 ` [v2][PATCH 3/3] FOR_TESTING_ONLY: Print rgb values of hw and sw blobs Swati Sharma
2019-09-17 15:56 ` ✗ Fi.CI.CHECKPATCH: warning for adding gamma state checker for icl+ platforms (rev2) Patchwork
2019-09-17 16:18 ` ✓ Fi.CI.BAT: success " Patchwork
2019-09-18  4:20 ` ✗ 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=878sqkwjqh.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=ankit.k.nautiyal@intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=swati2.sharma@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.