public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/4] drm/i915: Organize GLK_COLORS.
Date: Mon, 2 Oct 2017 15:55:02 -0700	[thread overview]
Message-ID: <20171002225502.b3henxuqfklyiylj@intel.com> (raw)
In-Reply-To: <87efql66u3.fsf@intel.com>

On Mon, Oct 02, 2017 at 01:02:28PM +0000, Jani Nikula wrote:
> On Thu, 28 Sep 2017, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> > Let's organize this in a way that it gets more obvious
> > when looking to the platform colors and in a easier
> > way to get inherited.
> >
> > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > ---
> >  drivers/gpu/drm/i915/i915_pci.c | 6 ++++--
> >  1 file changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/i915_pci.c b/drivers/gpu/drm/i915/i915_pci.c
> > index 9b54aafa2a0b..10537dcdd9c1 100644
> > --- a/drivers/gpu/drm/i915/i915_pci.c
> > +++ b/drivers/gpu/drm/i915/i915_pci.c
> > @@ -54,6 +54,8 @@
> >  	.color = { .degamma_lut_size = 512, .gamma_lut_size = 512 }
> >  #define CHV_COLORS \
> >  	.color = { .degamma_lut_size = 65, .gamma_lut_size = 257 }
> > +#define GLK_COLORS \
> > +	.color = { .degamma_lut_size = 0, .gamma_lut_size = 1024 }
> >  
> >  /* Keep in gen based order, and chronological order within a gen */
> >  #define GEN2_FEATURES \
> > @@ -495,7 +497,7 @@ static const struct intel_device_info intel_geminilake_info __initconst = {
> >  	GEN9_LP_FEATURES,
> >  	.platform = INTEL_GEMINILAKE,
> >  	.ddb_size = 1024,
> > -	.color = { .degamma_lut_size = 0, .gamma_lut_size = 1024 }
> > +	GLK_COLORS
> 
> Please add he comma at the end.
> 
> >  };
> >  
> >  #define KBL_PLATFORM \
> > @@ -543,7 +545,7 @@ static const struct intel_device_info intel_coffeelake_gt3_info __initconst = {
> >  #define GEN10_FEATURES \
> >  	GEN9_FEATURES, \
> >  	.ddb_size = 1024, \
> > -	.color = { .degamma_lut_size = 0, .gamma_lut_size = 1024 }
> > +	GLK_COLORS

this one here doesn't compile. it is inside a define...

So, I have a:
"v2: Add comma at the end (Jani), when possible." here

but I'm not sure about that since comma here is not really needed, also it wasn't there with the .color
and it is not symmetric anymore...

> 
> Ditto.
> 
> BR,
> Jani.
> 
> >  
> >  static const struct intel_device_info intel_cannonlake_gt2_info __initconst = {
> >  	GEN10_FEATURES,
> 
> -- 
> Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-10-02 22:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-28 18:51 [PATCH 0/4] 2-in-1: Organize feature inheritance and disable IPC Rodrigo Vivi
2017-09-28 18:51 ` [PATCH 1/4] drm/i915/skl: Fix has_ipc on skl and document WaDisableIPC Rodrigo Vivi
2017-10-03  5:26   ` Mahesh Kumar
2017-09-28 18:51 ` [PATCH 2/4] drm/i915: Organize GEN features inheritance Rodrigo Vivi
2017-09-28 19:03   ` Chris Wilson
2017-09-28 19:09     ` Rodrigo Vivi
2017-09-28 18:51 ` [PATCH 3/4] drm/i915: Organize GLK_COLORS Rodrigo Vivi
2017-09-28 19:04   ` Chris Wilson
2017-10-02 13:02   ` Jani Nikula
2017-10-02 22:55     ` Rodrigo Vivi [this message]
2017-10-03  5:42       ` Jani Nikula
2017-09-28 18:51 ` [PATCH 4/4] drm/i915: Extend WaDisableIPC to all platforms Rodrigo Vivi
2017-09-28 19:02   ` Chris Wilson
2017-09-28 19:12     ` Rodrigo Vivi
2017-09-28 19:17       ` Chris Wilson
2017-10-03  5:27       ` Mahesh Kumar
2017-10-03  6:43         ` Rodrigo Vivi
2017-09-28 19:15 ` ✗ Fi.CI.BAT: failure for 2-in-1: Organize feature inheritance and disable IPC Patchwork
2017-09-28 19:58 ` ✓ Fi.CI.BAT: success " Patchwork
2017-09-28 20:53 ` ✗ Fi.CI.IGT: failure " Patchwork
2017-10-02 23:17 ` ✓ Fi.CI.BAT: success " 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=20171002225502.b3henxuqfklyiylj@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@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