From: "Shankar, Uma" <uma.shankar@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [v2] drm/i915/display: Extend DP HDR support to hsw+
Date: Thu, 24 Mar 2022 10:55:55 +0000 [thread overview]
Message-ID: <77ff3aa1b7c641c096b357a8533d707e@intel.com> (raw)
In-Reply-To: <Yjw85i48eTsRZk1C@intel.com>
> -----Original Message-----
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Sent: Thursday, March 24, 2022 3:12 PM
> To: Shankar, Uma <uma.shankar@intel.com>
> Cc: intel-gfx@lists.freedesktop.org
> Subject: Re: [v2] drm/i915/display: Extend DP HDR support to hsw+
>
> On Thu, Mar 24, 2022 at 02:42:15PM +0530, Uma Shankar wrote:
> > HSW+ platforms are able to send out HDR Metadata SDP DIP
> > packet as GMP. Hence, extending the support for HDR on DP encoders for
> > the same.
> >
> > v2: Limited to non eDP ports on hsw/bdw and removed it for lspcon as
> > it is done separately (suggested by Ville)
> >
> > Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/5389
> > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Signed-off-by: Uma Shankar <uma.shankar@intel.com>
> > ---
> > drivers/gpu/drm/i915/display/intel_dp.c | 10 ++++++----
> > 1 file changed, 6 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_dp.c
> > b/drivers/gpu/drm/i915/display/intel_dp.c
> > index 9e19165fd175..09382b6133bc 100644
> > --- a/drivers/gpu/drm/i915/display/intel_dp.c
> > +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> > @@ -4939,10 +4939,12 @@ intel_dp_add_properties(struct intel_dp *intel_dp,
> struct drm_connector *connect
> > intel_attach_dp_colorspace_property(connector);
> > }
> >
> > - if (IS_GEMINILAKE(dev_priv) || DISPLAY_VER(dev_priv) >= 11)
> > - drm_object_attach_property(&connector->base,
> > - connector->dev-
> >mode_config.hdr_output_metadata_property,
> > - 0);
> > + if (!intel_bios_is_lspcon_present(dev_priv, port))
> > + if (((IS_HASWELL(dev_priv) || IS_BROADWELL(dev_priv)) &&
> > + !intel_dp_is_edp(intel_dp)) || DISPLAY_VER(dev_priv) >= 9)
>
> s/is_edp/port==A/
Yeah missed to limit only for port A, will fix it.
> I would put all of that into a helper (has_gamut_metadata_dip() or
> something) to make it actually legible.
Sure, will add a helper.
Regards,
Uma Shankar
>
> > + drm_object_attach_property(&connector->base,
> > + connector->dev-
> >mode_config.hdr_output_metadata_property,
> > + 0);
> >
> > if (intel_dp_is_edp(intel_dp)) {
> > u32 allowed_scalers;
> > --
> > 2.25.1
>
> --
> Ville Syrjälä
> Intel
next prev parent reply other threads:[~2022-03-24 10:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 9:12 [Intel-gfx] [v2] drm/i915/display: Extend DP HDR support to hsw+ Uma Shankar
2022-03-24 9:24 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/display: Extend DP HDR support to hsw+ (rev2) Patchwork
2022-03-24 9:29 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2022-03-24 9:41 ` [Intel-gfx] [v2] drm/i915/display: Extend DP HDR support to hsw+ Ville Syrjälä
2022-03-24 10:55 ` Shankar, Uma [this message]
2022-03-24 9:56 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/display: Extend DP HDR support to hsw+ (rev2) Patchwork
2022-03-24 12:28 ` [Intel-gfx] ✗ 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=77ff3aa1b7c641c096b357a8533d707e@intel.com \
--to=uma.shankar@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--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: 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.