From: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>
To: "C, Ramalingam" <ramalingam.c@intel.com>
Cc: "Ser, Simon" <simon.ser@intel.com>,
"daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Peres, Martin" <martin.peres@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"paul.kocialkowski@bootlin.com" <paul.kocialkowski@bootlin.com>,
"ppaalanen@gmail.com" <ppaalanen@gmail.com>
Subject: Re: [PATCH v2 3/3] drm/i915: Send hotplug event if edid had changed.
Date: Fri, 28 Jun 2019 11:36:09 +0000 [thread overview]
Message-ID: <b45b3aade954bc07faf063f32b025eaaddcaf3c2.camel@intel.com> (raw)
In-Reply-To: <20190628042419.GD24852@intel.com>
On Fri, 2019-06-28 at 09:54 +0530, Ramalingam C wrote:
> On 2019-06-28 at 11:24:54 +0300, Stanislav Lisovskiy wrote:
> > Added edid checking to dp and hdmi edid setting functions, which
> > are called from detect hooks. The result currently is propagated
> > to calling layer using drm_connector->change_counter(proposed by
> > Daniel Vetter).
> > drm_helper_hpd_irq_event and intel_encoder_hotplug are currently
> > both
> > responsible for checking if this counter or connection status is
> > changed.
> >
> > There are conflicting parts in drm and i915 which attempt
> > to do the same job - drm_helper_hpd_irq_event attempts to
> > check connector status changes and then call hotplug,
> > just as i915_hotplug_work_func, which calls encoder->hotplug
> > hook which in turn calls generic intel_encoder_hotplug function
> > which attempts to probe if output has changed.
> > Looks like both needs to be changed, so added edid checking
> > also to intel_encoder_hotplug function which is called both
> > for hdmi and dp.
> >
> > v2: Renamed change counter to epoch counter. Fixed type name.
> >
> >
> > @@ -2524,11 +2524,22 @@ intel_hdmi_set_edid(struct drm_connector
> > *connector)
> >
> > intel_display_power_put(dev_priv, POWER_DOMAIN_GMBUS, wakeref);
> >
> > + old_edid = to_intel_connector(connector)->detect_edid;
> > +
> > + if (!drm_edid_are_equal(edid, old_edid)) {
> > + intel_connector_update_modes(connector, edid);
> > + DRM_DEBUG_KMS("Updating change counter to %llu\n",
> > connector->epoch_counter);
> > + connector->epoch_counter += 1;
> > +
> > + DRM_DEBUG_KMS("[CONNECTOR:%d:%s] Edid was changed!
> > Updating blob property.\n",
> > + connector->base.id, connector->name);
> > + }
> > + intel_hdmi_unset_edid(connector);
> > to_intel_connector(connector)->detect_edid = edid;
> > +
>
> This and next changes are unrelated with this commit. Might want to
> keep
> it for separate patch.
What do you mean by unrelated? I thought dependent changes should go in
one patch series and here we are taking into use epoch_counter for
i915, which was introduced in previous 2 separate drm patches from that
series.
The drm changes should obviously always go first here, otherwise this
patch will fail - I wouldn't even be able to send it for testing if
that would be in another series.
>
> -Ram
> > if (edid && edid->input & DRM_EDID_INPUT_DIGITAL) {
> > intel_hdmi->has_audio = drm_detect_monitor_audio(edid);
> > intel_hdmi->has_hdmi_sink =
> > drm_detect_hdmi_monitor(edid);
> > -
> > connected = true;
> > }
> >
> > @@ -2555,7 +2566,6 @@ intel_hdmi_detect(struct drm_connector
> > *connector, bool force)
> > !intel_digital_port_connected(encoder))
> > goto out;
> >
> > - intel_hdmi_unset_edid(connector);
> >
> > if (intel_hdmi_set_edid(connector))
> > status = connector_status_connected;
> > diff --git a/drivers/gpu/drm/i915/display/intel_hotplug.c
> > b/drivers/gpu/drm/i915/display/intel_hotplug.c
> > index ea3de4acc850..f9d9e963196a 100644
> > --- a/drivers/gpu/drm/i915/display/intel_hotplug.c
> > +++ b/drivers/gpu/drm/i915/display/intel_hotplug.c
> > @@ -271,23 +271,33 @@ bool intel_encoder_hotplug(struct
> > intel_encoder *encoder,
> > {
> > struct drm_device *dev = connector->base.dev;
> > enum drm_connector_status old_status;
> > + u64 old_epoch_counter;
> > + bool ret = false;
> >
> > WARN_ON(!mutex_is_locked(&dev->mode_config.mutex));
> > old_status = connector->base.status;
> >
> > + old_epoch_counter = connector->base.epoch_counter;
> > +
> > connector->base.status =
> > drm_helper_probe_detect(&connector->base, NULL, false);
> >
> > - if (old_status == connector->base.status)
> > - return false;
> > + if (old_epoch_counter != connector->base.epoch_counter)
> > + ret = true;
> >
> > - DRM_DEBUG_KMS("[CONNECTOR:%d:%s] status updated from %s to
> > %s\n",
> > + if (old_status != connector->base.status)
> > + ret = true;
> > +
> > + if (ret) {
> > + DRM_DEBUG_KMS("[CONNECTOR:%d:%s] status updated from %s
> > to %s(change counter %llu)\n",
> > connector->base.base.id,
> > connector->base.name,
> > drm_get_connector_status_name(old_status),
> > - drm_get_connector_status_name(connector-
> > >base.status));
> > + drm_get_connector_status_name(connector-
> > >base.status),
> > + connector->base.epoch_counter);
> > + }
> >
> > - return true;
> > + return ret;
> > }
> >
> > static bool intel_encoder_has_hpd_pulse(struct intel_encoder
> > *encoder)
> > --
> > 2.17.1
> >
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-06-28 11:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 8:24 [PATCH v2 0/3] Send a hotplug when edid changes Stanislav Lisovskiy
2019-06-28 8:24 ` [PATCH v2 1/3] drm: Add helper to compare edids Stanislav Lisovskiy
2019-06-28 4:13 ` Ramalingam C
2019-07-01 19:52 ` Lyude Paul
2019-06-28 8:24 ` [PATCH v2 2/3] drm: Introduce change counter to drm_connector Stanislav Lisovskiy
2019-06-28 4:16 ` Ramalingam C
2019-06-28 8:24 ` [PATCH v2 3/3] drm/i915: Send hotplug event if edid had changed Stanislav Lisovskiy
2019-06-28 4:24 ` Ramalingam C
2019-06-28 11:36 ` Lisovskiy, Stanislav [this message]
2019-06-28 4:50 ` Ramalingam C
2019-06-28 8:48 ` ✗ Fi.CI.CHECKPATCH: warning for Send a hotplug when edid changes (rev2) Patchwork
2019-06-28 15:49 ` ✓ Fi.CI.BAT: success " Patchwork
2019-06-28 23:11 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-07-22 11:25 ` ✗ Fi.CI.BAT: failure for Send a hotplug when edid changes (rev3) 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=b45b3aade954bc07faf063f32b025eaaddcaf3c2.camel@intel.com \
--to=stanislav.lisovskiy@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=martin.peres@intel.com \
--cc=paul.kocialkowski@bootlin.com \
--cc=ppaalanen@gmail.com \
--cc=ramalingam.c@intel.com \
--cc=simon.ser@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