From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Shankar, Uma" <uma.shankar@intel.com>
Cc: "dcastagna@chromium.org" <dcastagna@chromium.org>,
"jonas@kwiboo.se" <jonas@kwiboo.se>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"seanpaul@chromium.org" <seanpaul@chromium.org>
Subject: Re: [v10 09/12] drm/i915:Enabled Modeset when HDR Infoframe changes
Date: Thu, 16 May 2019 16:13:12 +0300 [thread overview]
Message-ID: <20190516131312.GK24299@intel.com> (raw)
In-Reply-To: <E7C9878FBA1C6D42A1CA3F62AEB6945F8202AF4E@BGSMSX104.gar.corp.intel.com>
On Thu, May 16, 2019 at 10:54:14AM +0000, Shankar, Uma wrote:
>
>
> >-----Original Message-----
> >From: dri-devel [mailto:dri-devel-bounces@lists.freedesktop.org] On Behalf Of Ville
> >Syrjälä
> >Sent: Thursday, May 16, 2019 12:57 AM
> >To: Shankar, Uma <uma.shankar@intel.com>
> >Cc: dcastagna@chromium.org; jonas@kwiboo.se; intel-gfx@lists.freedesktop.org;
> >emil.l.velikov@gmail.com; dri-devel@lists.freedesktop.org; seanpaul@chromium.org
> >Subject: Re: [v10 09/12] drm/i915:Enabled Modeset when HDR Infoframe changes
> >
> >On Tue, May 14, 2019 at 11:06:31PM +0530, Uma Shankar wrote:
> >> This patch enables modeset whenever HDR metadata needs to be updated
> >> to sink.
> >>
> >> v2: Addressed Shashank's review comments.
> >>
> >> v3: Added Shashank's RB.
> >>
> >> v4: Addressed Ville's review comments.
> >>
> >> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >> Signed-off-by: Uma Shankar <uma.shankar@intel.com>
> >> Reviewed-by: Shashank Sharma <shashank.sharma@intel.com>
> >> ---
> >> drivers/gpu/drm/i915/intel_atomic.c | 14 +++++++++++++-
> >> drivers/gpu/drm/i915/intel_hdmi.c | 13 +++++++++++++
> >> 2 files changed, 26 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/gpu/drm/i915/intel_atomic.c
> >> b/drivers/gpu/drm/i915/intel_atomic.c
> >> index 58b8049..6b985e8 100644
> >> --- a/drivers/gpu/drm/i915/intel_atomic.c
> >> +++ b/drivers/gpu/drm/i915/intel_atomic.c
> >> @@ -105,6 +105,16 @@ int intel_digital_connector_atomic_set_property(struct
> >drm_connector *connector,
> >> return -EINVAL;
> >> }
> >>
> >> +static bool blob_equal(const struct drm_property_blob *a,
> >> + const struct drm_property_blob *b) {
> >> + if (a && b)
> >> + return a->length == b->length &&
> >> + !memcmp(a->data, b->data, a->length);
> >> +
> >> + return !a == !b;
> >> +}
> >> +
> >> int intel_digital_connector_atomic_check(struct drm_connector *conn,
> >> struct drm_connector_state *new_state) {
> >@@ -132,7 +142,9 @@
> >> int intel_digital_connector_atomic_check(struct drm_connector *conn,
> >> new_conn_state->base.colorspace != old_conn_state->base.colorspace ||
> >> new_conn_state->base.picture_aspect_ratio != old_conn_state-
> >>base.picture_aspect_ratio ||
> >> new_conn_state->base.content_type != old_conn_state-
> >>base.content_type ||
> >> - new_conn_state->base.scaling_mode != old_conn_state-
> >>base.scaling_mode)
> >> + new_conn_state->base.scaling_mode != old_conn_state-
> >>base.scaling_mode ||
> >> + !blob_equal(new_conn_state->base.hdr_output_metadata,
> >> + old_conn_state->base.hdr_output_metadata))
> >> crtc_state->mode_changed = true;
> >>
> >> return 0;
> >> diff --git a/drivers/gpu/drm/i915/intel_hdmi.c
> >> b/drivers/gpu/drm/i915/intel_hdmi.c
> >> index b80406b..e97bf6e 100644
> >> --- a/drivers/gpu/drm/i915/intel_hdmi.c
> >> +++ b/drivers/gpu/drm/i915/intel_hdmi.c
> >> @@ -806,6 +806,11 @@ void intel_read_infoframe(struct intel_encoder *encoder,
> >> return true;
> >> }
> >>
> >> +static inline bool is_eotf_supported(u8 output_eotf, u8 sink_eotf) {
> >> + return sink_eotf & BIT(output_eotf); }
> >> +
> >> static bool
> >> intel_hdmi_compute_drm_infoframe(struct intel_encoder *encoder,
> >> struct intel_crtc_state *crtc_state, @@ -814,6
> >+819,7 @@ void
> >> intel_read_infoframe(struct intel_encoder *encoder,
> >> struct hdmi_drm_infoframe *frame = &crtc_state->infoframes.drm.drm;
> >> struct hdr_output_metadata *hdr_metadata;
> >> struct drm_i915_private *dev_priv = to_i915(encoder->base.dev);
> >> + struct drm_connector *connector = conn_state->connector;
> >> int ret;
> >>
> >> if (!(INTEL_GEN(dev_priv) >= 10 || IS_GEMINILAKE(dev_priv))) @@
> >> -828,6 +834,13 @@ void intel_read_infoframe(struct intel_encoder
> >> *encoder,
> >>
> >> hdr_metadata = conn_state->hdr_output_metadata->data;
> >>
> >> + /* Sink EOTF is Bit map while infoframe is absolute values */
> >> + if (!is_eotf_supported(hdr_metadata->hdmi_metadata_type1.eotf,
> >> + connector->hdr_sink_metadata.hdmi_type1.eotf)) {
> >> + DRM_ERROR("EOTF Not Supported\n");
> >> + return true;
> >> + }
> >
> >I was going to say that this should probably be in the
> >drm_set_hdr_metdata() or whatever it was called.
> >
> >But now I'm now wondering if we can even have this check here. What happens if
> >someone does a display switcheroo while the machine is suspended? Depends on
> >when we're going to reprobe the displays I suppose. Hmm. Maybe it's fine. We
> >already have a similar issue after all wih the has_hdmi2_sink stuff.
> >
> >Either way the user triggerable DRM_ERROR()s are at least a nono.
>
> Ok, Will keep the check and move it inside the drm_set_hdr_metdata(). Also downgrade
> the print as INFO instead of ERROR. Hope this is fine.
DEBUG_KMS like everything else.
>
> >> +
> >> crtc_state->infoframes.enable |=
> >> intel_hdmi_infoframe_enable(HDMI_INFOFRAME_TYPE_DRM);
> >>
> >> --
> >> 1.9.1
> >
> >--
> >Ville Syrjälä
> >Intel
> >_______________________________________________
> >dri-devel mailing list
> >dri-devel@lists.freedesktop.org
> >https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-05-16 13:13 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 17:36 [v10 00/12] Add HDR Metadata Parsing and handling in DRM layer Uma Shankar
2019-05-14 17:29 ` ✗ Fi.CI.CHECKPATCH: warning for Add HDR Metadata Parsing and handling in DRM layer (rev10) Patchwork
2019-05-14 17:36 ` [v10 01/12] drm: Add HDR source metadata property Uma Shankar
2019-05-15 19:10 ` Ville Syrjälä
2019-05-15 19:33 ` Jonas Karlman
2019-05-15 19:45 ` Ville Syrjälä
2019-05-15 19:50 ` Jonas Karlman
2019-05-16 7:21 ` Shankar, Uma
2019-05-14 17:36 ` [v10 02/12] drm: Add reference counting on HDR metadata blob Uma Shankar
2019-05-14 17:36 ` [v10 03/12] drm: Parse HDR metadata info from EDID Uma Shankar
2019-05-15 19:36 ` Ville Syrjälä
2019-05-16 7:25 ` Shankar, Uma
2019-05-14 17:36 ` [v10 04/12] drm: Enable HDR infoframe support Uma Shankar
2019-05-15 19:15 ` Ville Syrjälä
2019-05-16 7:22 ` Shankar, Uma
2019-05-14 17:36 ` [v10 05/12] drm/i915: Attach HDR metadata property to connector Uma Shankar
2019-05-14 17:36 ` [v10 06/12] drm/i915: Write HDR infoframe and send to panel Uma Shankar
2019-05-14 17:36 ` [v10 07/12] drm: Add HLG EOTF Uma Shankar
2019-05-14 17:36 ` [v10 08/12] drm/i915: Enable infoframes on GLK+ for HDR Uma Shankar
2019-05-14 17:36 ` [v10 09/12] drm/i915:Enabled Modeset when HDR Infoframe changes Uma Shankar
2019-05-15 19:27 ` Ville Syrjälä
2019-05-16 10:54 ` Shankar, Uma
2019-05-16 13:13 ` Ville Syrjälä [this message]
2019-05-14 17:36 ` [v10 10/12] drm/i915: Added DRM Infoframe handling for BYT/CHT Uma Shankar
2019-05-14 17:36 ` [v10 11/12] video/hdmi: Add Unpack function for DRM infoframe Uma Shankar
2019-05-14 17:36 ` [v10 12/12] drm/i915: Add state readout " Uma Shankar
2019-05-15 19:29 ` Ville Syrjälä
2019-05-16 7:23 ` Shankar, Uma
2019-05-14 17:50 ` ✓ Fi.CI.BAT: success for Add HDR Metadata Parsing and handling in DRM layer (rev10) Patchwork
2019-05-15 1:23 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-05-15 8:59 ` Shankar, Uma
2019-05-15 10:34 ` Saarinen, Jani
2019-05-15 19:32 ` Ville Syrjälä
2019-05-16 7:28 ` Shankar, Uma
2019-05-16 13:15 ` Ville Syrjälä
2019-05-16 13:18 ` Shankar, Uma
2019-05-16 14:08 ` Martin Peres
2019-05-17 13:04 ` Ville Syrjälä
2019-05-17 13:09 ` Peres, Martin
2019-05-17 13:17 ` Shankar, Uma
2019-05-17 13:24 ` Ville Syrjälä
2019-05-17 13:38 ` Shankar, Uma
2019-05-15 12:33 ` ✓ Fi.CI.IGT: 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=20190516131312.GK24299@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dcastagna@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jonas@kwiboo.se \
--cc=seanpaul@chromium.org \
--cc=uma.shankar@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.