From: "Shankar, Uma" <uma.shankar@intel.com> To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>, "Harry Wentland" <harry.wentland@amd.com> Cc: "Shashank.Sharma@amd.com" <Shashank.Sharma@amd.com>, "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>, "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>, "sebastian@sebastianwick.net" <sebastian@sebastianwick.net> Subject: RE: [RFC v2 05/22] drm/i915/xelpd: Define Degamma Lut range struct for HDR planes Date: Thu, 11 Nov 2021 20:42:29 +0000 [thread overview] Message-ID: <edc4b80279354ec7bcdb0a890dae7d79@intel.com> (raw) In-Reply-To: <YY1H//+XISVMFZNL@intel.com> > -----Original Message----- > From: Ville Syrjälä <ville.syrjala@linux.intel.com> > Sent: Thursday, November 11, 2021 10:13 PM > To: Harry Wentland <harry.wentland@amd.com> > Cc: Shankar, Uma <uma.shankar@intel.com>; intel-gfx@lists.freedesktop.org; dri- > devel@lists.freedesktop.org; ppaalanen@gmail.com; brian.starkey@arm.com; > sebastian@sebastianwick.net; Shashank.Sharma@amd.com > Subject: Re: [RFC v2 05/22] drm/i915/xelpd: Define Degamma Lut range struct for > HDR planes > > On Thu, Nov 11, 2021 at 10:17:17AM -0500, Harry Wentland wrote: > > > > > > On 2021-09-06 17:38, Uma Shankar wrote: > > > Define the structure with XE_LPD degamma lut ranges. HDR and SDR > > > planes have different capabilities, implemented respective structure > > > for the HDR planes. > > > > > > Signed-off-by: Uma Shankar <uma.shankar@intel.com> > > > --- > > > drivers/gpu/drm/i915/display/intel_color.c | 52 > > > ++++++++++++++++++++++ > > > 1 file changed, 52 insertions(+) > > > > > > diff --git a/drivers/gpu/drm/i915/display/intel_color.c > > > b/drivers/gpu/drm/i915/display/intel_color.c > > > index afcb4bf3826c..6403bd74324b 100644 > > > --- a/drivers/gpu/drm/i915/display/intel_color.c > > > +++ b/drivers/gpu/drm/i915/display/intel_color.c > > > @@ -2092,6 +2092,58 @@ static void icl_read_luts(struct intel_crtc_state > *crtc_state) > > > } > > > } > > > > > > + /* FIXME input bpc? */ > > > +__maybe_unused > > > +static const struct drm_color_lut_range d13_degamma_hdr[] = { > > > + /* segment 1 */ > > > + { > > > + .flags = (DRM_MODE_LUT_GAMMA | > > > + DRM_MODE_LUT_REFLECT_NEGATIVE | > > > + DRM_MODE_LUT_INTERPOLATE | > > > + DRM_MODE_LUT_NON_DECREASING), > > > + .count = 128, > > > + .input_bpc = 24, .output_bpc = 16, > > > + .start = 0, .end = (1 << 24) - 1, > > > + .min = 0, .max = (1 << 24) - 1, > > > + }, > > > + /* segment 2 */ > > > + { > > > + .flags = (DRM_MODE_LUT_GAMMA | > > > + DRM_MODE_LUT_REFLECT_NEGATIVE | > > > + DRM_MODE_LUT_INTERPOLATE | > > > + DRM_MODE_LUT_REUSE_LAST | > > > + DRM_MODE_LUT_NON_DECREASING), > > > + .count = 1, > > > + .input_bpc = 24, .output_bpc = 16, > > > + .start = (1 << 24) - 1, .end = 1 << 24, > > > + .min = 0, .max = (1 << 27) - 1, > > > + }, > > > + /* Segment 3 */ > > > + { > > > + .flags = (DRM_MODE_LUT_GAMMA | > > > + DRM_MODE_LUT_REFLECT_NEGATIVE | > > > + DRM_MODE_LUT_INTERPOLATE | > > > + DRM_MODE_LUT_REUSE_LAST | > > > + DRM_MODE_LUT_NON_DECREASING), > > > + .count = 1, > > > + .input_bpc = 24, .output_bpc = 16, > > > + .start = 1 << 24, .end = 3 << 24, > > > + .min = 0, .max = (1 << 27) - 1, > > > + }, > > > + /* Segment 4 */ > > > + { > > > + .flags = (DRM_MODE_LUT_GAMMA | > > > + DRM_MODE_LUT_REFLECT_NEGATIVE | > > > + DRM_MODE_LUT_INTERPOLATE | > > > + DRM_MODE_LUT_REUSE_LAST | > > > + DRM_MODE_LUT_NON_DECREASING), > > > + .count = 1, > > > + .input_bpc = 24, .output_bpc = 16, > > > + .start = 3 << 24, .end = 7 << 24, > > > + .min = 0, .max = (1 << 27) - 1, > > > + }, > > > +}; > > > > If I understand this right, userspace would need this definition in > > order to populate the degamma blob. Should this sit in a UAPI header? Hi Harry, Pekka and Ville, Sorry for being a bit late on the replies, got side tracked with various issues. I am back on this. Apologies for delay. > My original idea (not sure it's fully realized in this series) is to have a new > GAMMA_MODE/etc. enum property on each crtc (or plane) for which each enum > value points to a kernel provided blob that contains one of these LUT descriptors. > Userspace can then query them dynamically and pick the best one for its current use > case. We have this as part of the series Ville. Patch 3 of this series creates a DEGAMMA_MODE property just for this. With that userspace can just query the blob_id's and will get the various degamma mode possible and the respective segment and lut distributions. This will be generic, so for userspace it should just be able to query this and parse and get the lut distribution and segment ranges. > The algorithm for choosing the best one might be something like: > - prefer LUT with bpc >= FB bpc, but perhaps not needlessly high bpc > - prefer interpolated vs. direct lookup based on current needs (eg. X > could prefer direct lookup to get directcolor visuals). > - prefer one with extended range values if needed > - for HDR prefer smaller step size in dark tones, > for SDR perhaps prefer a more uniform step size > > Or maybe we should include some kind of usage hints as well? I think the segment range and distribution of lut should be enough for a userspace to pick the right ones, but we can add some examples in UAPI descriptions as hints. > And I was thinking of even adding a new property type (eg. > ENUM_BLOB) just for this sort of usecase. That could let us have a bit more generic > code to do all the validation around the property values and whatnot. > > The one nagging concern I really have with GAMMA_MODE is how a mix of old and > new userspace would work. Though that is more of a generic issue with any new > property really. For plane properties getting added newly, old userspace will not get it so I think this should be ok. Newer userspace will implement this and get the new functionality. Problem will be in extending this to crtc where we have a legacy baggage, the client caps approach may help us there. Have it as part of separate series just to not mix it with this new plane stuff, though the idea remains same based on your design. Series below for reference: https://patchwork.freedesktop.org/series/90821/ Regards, Uma Shankar > -- > Ville Syrjälä > Intel
WARNING: multiple messages have this Message-ID (diff)
From: "Shankar, Uma" <uma.shankar@intel.com> To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>, "Harry Wentland" <harry.wentland@amd.com> Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>, "ppaalanen@gmail.com" <ppaalanen@gmail.com>, "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>, "sebastian@sebastianwick.net" <sebastian@sebastianwick.net> Subject: Re: [Intel-gfx] [RFC v2 05/22] drm/i915/xelpd: Define Degamma Lut range struct for HDR planes Date: Thu, 11 Nov 2021 20:42:29 +0000 [thread overview] Message-ID: <edc4b80279354ec7bcdb0a890dae7d79@intel.com> (raw) In-Reply-To: <YY1H//+XISVMFZNL@intel.com> > -----Original Message----- > From: Ville Syrjälä <ville.syrjala@linux.intel.com> > Sent: Thursday, November 11, 2021 10:13 PM > To: Harry Wentland <harry.wentland@amd.com> > Cc: Shankar, Uma <uma.shankar@intel.com>; intel-gfx@lists.freedesktop.org; dri- > devel@lists.freedesktop.org; ppaalanen@gmail.com; brian.starkey@arm.com; > sebastian@sebastianwick.net; Shashank.Sharma@amd.com > Subject: Re: [RFC v2 05/22] drm/i915/xelpd: Define Degamma Lut range struct for > HDR planes > > On Thu, Nov 11, 2021 at 10:17:17AM -0500, Harry Wentland wrote: > > > > > > On 2021-09-06 17:38, Uma Shankar wrote: > > > Define the structure with XE_LPD degamma lut ranges. HDR and SDR > > > planes have different capabilities, implemented respective structure > > > for the HDR planes. > > > > > > Signed-off-by: Uma Shankar <uma.shankar@intel.com> > > > --- > > > drivers/gpu/drm/i915/display/intel_color.c | 52 > > > ++++++++++++++++++++++ > > > 1 file changed, 52 insertions(+) > > > > > > diff --git a/drivers/gpu/drm/i915/display/intel_color.c > > > b/drivers/gpu/drm/i915/display/intel_color.c > > > index afcb4bf3826c..6403bd74324b 100644 > > > --- a/drivers/gpu/drm/i915/display/intel_color.c > > > +++ b/drivers/gpu/drm/i915/display/intel_color.c > > > @@ -2092,6 +2092,58 @@ static void icl_read_luts(struct intel_crtc_state > *crtc_state) > > > } > > > } > > > > > > + /* FIXME input bpc? */ > > > +__maybe_unused > > > +static const struct drm_color_lut_range d13_degamma_hdr[] = { > > > + /* segment 1 */ > > > + { > > > + .flags = (DRM_MODE_LUT_GAMMA | > > > + DRM_MODE_LUT_REFLECT_NEGATIVE | > > > + DRM_MODE_LUT_INTERPOLATE | > > > + DRM_MODE_LUT_NON_DECREASING), > > > + .count = 128, > > > + .input_bpc = 24, .output_bpc = 16, > > > + .start = 0, .end = (1 << 24) - 1, > > > + .min = 0, .max = (1 << 24) - 1, > > > + }, > > > + /* segment 2 */ > > > + { > > > + .flags = (DRM_MODE_LUT_GAMMA | > > > + DRM_MODE_LUT_REFLECT_NEGATIVE | > > > + DRM_MODE_LUT_INTERPOLATE | > > > + DRM_MODE_LUT_REUSE_LAST | > > > + DRM_MODE_LUT_NON_DECREASING), > > > + .count = 1, > > > + .input_bpc = 24, .output_bpc = 16, > > > + .start = (1 << 24) - 1, .end = 1 << 24, > > > + .min = 0, .max = (1 << 27) - 1, > > > + }, > > > + /* Segment 3 */ > > > + { > > > + .flags = (DRM_MODE_LUT_GAMMA | > > > + DRM_MODE_LUT_REFLECT_NEGATIVE | > > > + DRM_MODE_LUT_INTERPOLATE | > > > + DRM_MODE_LUT_REUSE_LAST | > > > + DRM_MODE_LUT_NON_DECREASING), > > > + .count = 1, > > > + .input_bpc = 24, .output_bpc = 16, > > > + .start = 1 << 24, .end = 3 << 24, > > > + .min = 0, .max = (1 << 27) - 1, > > > + }, > > > + /* Segment 4 */ > > > + { > > > + .flags = (DRM_MODE_LUT_GAMMA | > > > + DRM_MODE_LUT_REFLECT_NEGATIVE | > > > + DRM_MODE_LUT_INTERPOLATE | > > > + DRM_MODE_LUT_REUSE_LAST | > > > + DRM_MODE_LUT_NON_DECREASING), > > > + .count = 1, > > > + .input_bpc = 24, .output_bpc = 16, > > > + .start = 3 << 24, .end = 7 << 24, > > > + .min = 0, .max = (1 << 27) - 1, > > > + }, > > > +}; > > > > If I understand this right, userspace would need this definition in > > order to populate the degamma blob. Should this sit in a UAPI header? Hi Harry, Pekka and Ville, Sorry for being a bit late on the replies, got side tracked with various issues. I am back on this. Apologies for delay. > My original idea (not sure it's fully realized in this series) is to have a new > GAMMA_MODE/etc. enum property on each crtc (or plane) for which each enum > value points to a kernel provided blob that contains one of these LUT descriptors. > Userspace can then query them dynamically and pick the best one for its current use > case. We have this as part of the series Ville. Patch 3 of this series creates a DEGAMMA_MODE property just for this. With that userspace can just query the blob_id's and will get the various degamma mode possible and the respective segment and lut distributions. This will be generic, so for userspace it should just be able to query this and parse and get the lut distribution and segment ranges. > The algorithm for choosing the best one might be something like: > - prefer LUT with bpc >= FB bpc, but perhaps not needlessly high bpc > - prefer interpolated vs. direct lookup based on current needs (eg. X > could prefer direct lookup to get directcolor visuals). > - prefer one with extended range values if needed > - for HDR prefer smaller step size in dark tones, > for SDR perhaps prefer a more uniform step size > > Or maybe we should include some kind of usage hints as well? I think the segment range and distribution of lut should be enough for a userspace to pick the right ones, but we can add some examples in UAPI descriptions as hints. > And I was thinking of even adding a new property type (eg. > ENUM_BLOB) just for this sort of usecase. That could let us have a bit more generic > code to do all the validation around the property values and whatnot. > > The one nagging concern I really have with GAMMA_MODE is how a mix of old and > new userspace would work. Though that is more of a generic issue with any new > property really. For plane properties getting added newly, old userspace will not get it so I think this should be ok. Newer userspace will implement this and get the new functionality. Problem will be in extending this to crtc where we have a legacy baggage, the client caps approach may help us there. Have it as part of separate series just to not mix it with this new plane stuff, though the idea remains same based on your design. Series below for reference: https://patchwork.freedesktop.org/series/90821/ Regards, Uma Shankar > -- > Ville Syrjälä > Intel
next prev parent reply other threads:[~2021-11-11 20:42 UTC|newest] Thread overview: 154+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-06 21:38 [Intel-gfx] [RFC v2 00/22] Add Support for Plane Color Lut and CSC features Uma Shankar 2021-09-06 21:38 ` Uma Shankar 2021-09-06 21:26 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Add Support for Plane Color Lut and CSC features (rev2) Patchwork 2021-09-06 21:30 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork 2021-09-06 21:38 ` [Intel-gfx] [RFC v2 01/22] drm: RFC for Plane Color Hardware Pipeline Uma Shankar 2021-09-06 21:38 ` Uma Shankar 2021-10-12 10:30 ` Pekka Paalanen 2021-10-12 10:30 ` [Intel-gfx] " Pekka Paalanen 2021-10-12 10:35 ` Simon Ser 2021-10-12 10:35 ` [Intel-gfx] " Simon Ser 2021-10-12 12:00 ` Pekka Paalanen 2021-10-12 12:00 ` [Intel-gfx] " Pekka Paalanen 2021-10-12 19:11 ` Shankar, Uma 2021-10-12 19:11 ` [Intel-gfx] " Shankar, Uma 2021-10-13 7:25 ` Pekka Paalanen 2021-10-13 7:25 ` [Intel-gfx] " Pekka Paalanen 2021-10-14 19:46 ` Shankar, Uma 2021-10-14 19:46 ` [Intel-gfx] " Shankar, Uma 2021-10-12 20:58 ` Shankar, Uma 2021-10-12 20:58 ` [Intel-gfx] " Shankar, Uma 2021-10-13 8:30 ` Pekka Paalanen 2021-10-13 8:30 ` [Intel-gfx] " Pekka Paalanen 2021-10-14 19:44 ` Shankar, Uma 2021-10-14 19:44 ` [Intel-gfx] " Shankar, Uma 2021-10-15 7:42 ` Pekka Paalanen 2021-10-15 7:42 ` [Intel-gfx] " Pekka Paalanen 2021-10-26 15:11 ` Harry Wentland 2021-10-26 15:11 ` [Intel-gfx] " Harry Wentland 2021-10-26 15:36 ` Harry Wentland 2021-10-26 15:36 ` [Intel-gfx] " Harry Wentland 2021-10-27 8:00 ` Pekka Paalanen 2021-10-27 8:00 ` [Intel-gfx] " Pekka Paalanen 2021-10-27 12:48 ` Harry Wentland 2021-10-27 12:48 ` Harry Wentland 2021-10-26 15:40 ` Harry Wentland 2021-10-26 15:40 ` [Intel-gfx] " Harry Wentland 2021-11-23 15:05 ` Harry Wentland 2021-11-23 15:05 ` [Intel-gfx] " Harry Wentland 2021-11-25 20:43 ` Shankar, Uma 2021-11-25 20:43 ` [Intel-gfx] " Shankar, Uma 2021-11-26 8:21 ` Pekka Paalanen 2021-11-26 8:21 ` [Intel-gfx] " Pekka Paalanen 2021-09-06 21:38 ` [Intel-gfx] [RFC v2 02/22] drm: Add Enhanced Gamma and color lut range attributes Uma Shankar 2021-09-06 21:38 ` Uma Shankar 2021-11-03 15:08 ` Harry Wentland 2021-11-03 15:08 ` [Intel-gfx] " Harry Wentland 2021-11-04 8:38 ` Pekka Paalanen 2021-11-04 8:38 ` [Intel-gfx] " Pekka Paalanen 2021-11-04 16:27 ` Harry Wentland 2021-11-04 16:27 ` [Intel-gfx] " Harry Wentland 2021-11-05 11:49 ` Ville Syrjälä 2021-11-05 11:49 ` [Intel-gfx] " Ville Syrjälä 2021-11-09 20:22 ` Harry Wentland 2021-11-09 20:22 ` [Intel-gfx] " Harry Wentland 2021-11-08 9:54 ` Pekka Paalanen 2021-11-08 9:54 ` [Intel-gfx] " Pekka Paalanen 2021-11-09 20:47 ` Harry Wentland 2021-11-09 20:47 ` [Intel-gfx] " Harry Wentland 2021-11-09 22:02 ` Ville Syrjälä 2021-11-09 22:02 ` [Intel-gfx] " Ville Syrjälä 2021-11-10 8:49 ` Pekka Paalanen 2021-11-10 8:49 ` [Intel-gfx] " Pekka Paalanen 2021-11-10 11:55 ` Ville Syrjälä 2021-11-10 11:55 ` [Intel-gfx] " Ville Syrjälä 2021-11-10 15:17 ` Harry Wentland 2021-11-10 15:17 ` [Intel-gfx] " Harry Wentland 2021-11-11 8:22 ` Pekka Paalanen 2021-11-11 8:22 ` [Intel-gfx] " Pekka Paalanen 2021-09-06 21:38 ` [Intel-gfx] [RFC v2 03/22] drm: Add Plane Degamma Mode property Uma Shankar 2021-09-06 21:38 ` Uma Shankar 2021-10-12 11:50 ` Pekka Paalanen 2021-10-12 11:50 ` [Intel-gfx] " Pekka Paalanen 2021-10-12 21:02 ` Shankar, Uma 2021-10-12 21:02 ` [Intel-gfx] " Shankar, Uma 2021-09-06 21:38 ` [Intel-gfx] [RFC v2 04/22] drm: Add Plane Degamma Lut property Uma Shankar 2021-09-06 21:38 ` Uma Shankar 2021-09-06 21:38 ` [Intel-gfx] [RFC v2 05/22] drm/i915/xelpd: Define Degamma Lut range struct for HDR planes Uma Shankar 2021-09-06 21:38 ` Uma Shankar 2021-11-03 15:10 ` Harry Wentland 2021-11-03 15:10 ` [Intel-gfx] " Harry Wentland 2021-11-05 12:59 ` Ville Syrjälä 2021-11-05 12:59 ` [Intel-gfx] " Ville Syrjälä 2021-11-09 20:19 ` Harry Wentland 2021-11-09 20:19 ` [Intel-gfx] " Harry Wentland 2021-11-09 21:45 ` Ville Syrjälä 2021-11-09 21:45 ` [Intel-gfx] " Ville Syrjälä 2021-11-09 21:56 ` Harry Wentland 2021-11-09 21:56 ` [Intel-gfx] " Harry Wentland 2021-11-11 15:17 ` Harry Wentland 2021-11-11 15:17 ` [Intel-gfx] " Harry Wentland 2021-11-11 16:42 ` Ville Syrjälä 2021-11-11 16:42 ` [Intel-gfx] " Ville Syrjälä 2021-11-11 20:42 ` Shankar, Uma [this message] 2021-11-11 20:42 ` Shankar, Uma 2021-11-11 21:10 ` Harry Wentland 2021-11-11 21:10 ` [Intel-gfx] " Harry Wentland 2021-11-11 21:58 ` Shankar, Uma 2021-11-11 21:58 ` [Intel-gfx] " Shankar, Uma 2021-11-12 8:37 ` Pekka Paalanen 2021-11-12 8:37 ` [Intel-gfx] " Pekka Paalanen 2021-11-23 14:40 ` Harry Wentland 2021-11-23 14:40 ` [Intel-gfx] " Harry Wentland 2021-11-12 14:54 ` Ville Syrjälä 2021-11-12 14:54 ` [Intel-gfx] " Ville Syrjälä 2021-11-16 8:15 ` Pekka Paalanen 2021-11-16 8:15 ` [Intel-gfx] " Pekka Paalanen 2021-09-06 21:38 ` [Intel-gfx] [RFC v2 06/22] drm/i915/xelpd: Add register definitions for Plane Degamma Uma Shankar 2021-09-06 21:38 ` Uma Shankar 2021-09-06 21:38 ` [Intel-gfx] [RFC v2 07/22] drm/i915/xelpd: Enable plane color features Uma Shankar 2021-09-06 21:38 ` Uma Shankar 2021-09-06 21:38 ` [Intel-gfx] [RFC v2 08/22] drm/i915/xelpd: Add color capabilities of SDR planes Uma Shankar 2021-09-06 21:38 ` Uma Shankar 2021-09-06 21:38 ` [Intel-gfx] [RFC v2 09/22] drm/i915/xelpd: Program Plane Degamma Registers Uma Shankar 2021-09-06 21:38 ` Uma Shankar 2021-09-06 21:38 ` [Intel-gfx] [RFC v2 10/22] drm/i915/xelpd: Add plane color check to glk_plane_color_ctl Uma Shankar 2021-09-06 21:38 ` Uma Shankar 2021-09-06 21:38 ` [Intel-gfx] [RFC v2 11/22] drm/i915/xelpd: Initialize plane color features Uma Shankar 2021-09-06 21:38 ` Uma Shankar 2021-09-06 21:38 ` [RFC v2 12/22] drm/i915/xelpd: Load plane color luts from atomic flip Uma Shankar 2021-09-06 21:38 ` [Intel-gfx] " Uma Shankar 2021-09-06 21:38 ` [RFC v2 13/22] drm: Add Plane CTM property Uma Shankar 2021-09-06 21:38 ` [Intel-gfx] " Uma Shankar 2021-09-06 21:38 ` [RFC v2 14/22] drm: Add helper to attach Plane ctm property Uma Shankar 2021-09-06 21:38 ` [Intel-gfx] " Uma Shankar 2021-09-06 21:38 ` [RFC v2 15/22] drm/i915/xelpd: Define Plane CSC Registers Uma Shankar 2021-09-06 21:38 ` [Intel-gfx] " Uma Shankar 2021-09-06 21:38 ` [RFC v2 16/22] drm/i915/xelpd: Enable Plane CSC Uma Shankar 2021-09-06 21:38 ` [Intel-gfx] " Uma Shankar 2021-09-06 21:38 ` [RFC v2 17/22] drm: Add Plane Gamma Mode property Uma Shankar 2021-09-06 21:38 ` [Intel-gfx] " Uma Shankar 2021-09-06 21:39 ` [RFC v2 18/22] drm: Add Plane Gamma Lut property Uma Shankar 2021-09-06 21:39 ` [Intel-gfx] " Uma Shankar 2021-09-06 21:39 ` [RFC v2 19/22] drm/i915/xelpd: Define and Initialize Plane Gamma Lut range Uma Shankar 2021-09-06 21:39 ` [Intel-gfx] " Uma Shankar 2021-09-06 21:39 ` [RFC v2 20/22] drm/i915/xelpd: Add register definitions for Plane Gamma Uma Shankar 2021-09-06 21:39 ` [Intel-gfx] " Uma Shankar 2021-09-06 21:39 ` [RFC v2 21/22] drm/i915/xelpd: Program Plane Gamma Registers Uma Shankar 2021-09-06 21:39 ` [Intel-gfx] " Uma Shankar 2021-09-06 21:39 ` [RFC v2 22/22] drm/i915/xelpd: Enable plane gamma Uma Shankar 2021-09-06 21:39 ` [Intel-gfx] " Uma Shankar 2021-09-06 21:57 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Add Support for Plane Color Lut and CSC features (rev2) Patchwork 2021-09-06 23:12 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork 2021-10-12 11:55 ` [RFC v2 00/22] Add Support for Plane Color Lut and CSC features Pekka Paalanen 2021-10-12 11:55 ` [Intel-gfx] " Pekka Paalanen 2021-10-12 21:01 ` Shankar, Uma 2021-10-12 21:01 ` [Intel-gfx] " Shankar, Uma 2021-10-26 15:02 ` Harry Wentland 2021-10-26 15:02 ` [Intel-gfx] " Harry Wentland 2021-10-27 8:18 ` Pekka Paalanen 2021-10-27 8:18 ` [Intel-gfx] " Pekka Paalanen 2022-02-02 16:11 ` Harry Wentland 2022-02-02 16:11 ` [Intel-gfx] " Harry Wentland 2022-02-03 17:22 ` Shankar, Uma 2022-02-03 17:22 ` [Intel-gfx] " Shankar, Uma
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=edc4b80279354ec7bcdb0a890dae7d79@intel.com \ --to=uma.shankar@intel.com \ --cc=Shashank.Sharma@amd.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=harry.wentland@amd.com \ --cc=intel-gfx@lists.freedesktop.org \ --cc=sebastian@sebastianwick.net \ --cc=ville.syrjala@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: linkBe 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.