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] [PATCH] drm/i915/display: Extend DP HDR support to hsw+
Date: Thu, 24 Mar 2022 09:12:08 +0000 [thread overview]
Message-ID: <10ec0a9336a544d3817945a785b89954@intel.com> (raw)
In-Reply-To: <Yjtyktb/iGsSME8G@intel.com>
> -----Original Message-----
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Sent: Thursday, March 24, 2022 12:49 AM
> To: Shankar, Uma <uma.shankar@intel.com>
> Cc: intel-gfx@lists.freedesktop.org
> Subject: Re: [Intel-gfx] [PATCH] drm/i915/display: Extend DP HDR support to hsw+
>
> On Wed, Mar 23, 2022 at 09:04:36PM +0200, Ville Syrjälä wrote:
> > On Thu, Mar 24, 2022 at 12:15:22AM +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.
> > >
> > > 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 | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/gpu/drm/i915/display/intel_dp.c
> > > b/drivers/gpu/drm/i915/display/intel_dp.c
> > > index 9e19165fd175..e10d2c151abf 100644
> > > --- a/drivers/gpu/drm/i915/display/intel_dp.c
> > > +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> > > @@ -4939,7 +4939,7 @@ 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)
> > > + if (IS_HASWELL(dev_priv) || DISPLAY_VER(dev_priv) >= 8)
> >
> > CHV does not have this at all, and HSW/BDW don't have it on transcoder EDP.
>
> Actually vlv/chv might have it since the vlv video DIP was supposedly ripped from ibx.
> So potentially we could just enable this for all ilk+.
> But that would require actual testing, so hsw+ seems like good enough for now.
Sure, will update this.
> >
> > Also if we're going to attach this unconditionally then we should stop
> > attaching it again in the LSPCON init path. Or we should skip this one
> > when LSPCON is present.
Ok, have taken care of it and sent out the next version.
Thanks Ville for the feedback.
Regards,
Uma Shankar
> >
> > > drm_object_attach_property(&connector->base,
> > > connector->dev-
> >mode_config.hdr_output_metadata_property,
> > > 0);
> > > --
> > > 2.25.1
> >
> > --
> > Ville Syrjälä
> > Intel
>
> --
> Ville Syrjälä
> Intel
next prev parent reply other threads:[~2022-03-24 9:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 18:45 [Intel-gfx] [PATCH] drm/i915/display: Extend DP HDR support to hsw+ Uma Shankar
2022-03-23 19:04 ` Ville Syrjälä
2022-03-23 19:18 ` Ville Syrjälä
2022-03-24 9:12 ` Shankar, Uma [this message]
2022-03-23 19:57 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for " Patchwork
2022-03-23 20:17 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-23 21:49 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=10ec0a9336a544d3817945a785b89954@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox