Small fixes to speed up resume
Subsystems (2)
cover Small fixes to speed up resume
Recently David Weinehall has been investigating how we can make the resume process in i915 faster, and poked me to take a look at why we were taking so long while reprobing. As it turns out the main issue is just that we hold up the entire resume process while we reprobe connectors, which isn't really necessary. This fixes things so we can actually run the connector reprobing on resume asynchronously.
Lyude (2):
drm/i915: Remove redundant reprobe in i915_drm_resume drm/i915: Reinit polling before hpd when resuming
drivers/gpu/drm/i915/i915_drv.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)
Signature · 6 lines
2.7.4 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 1/2 drm/i915: Remove redundant reprobe in i915_drm_resume
Weine's investigation on benchmarking the suspend/resume process pointed out a lot of the time in suspend/resume is being spent reprobing. While the reprobing process is a lengthy one for good reason, we don't need to hold up the entire suspend/resume process while we wait for it to finish. Luckily as it turns out, we already trigger a full connector reprobe in i915_hpd_poll_init_work(), so we can just ditch reprobing in i915_drm_resume() entirely.
This won't lead to less time spent resuming just yet since now the bottleneck will be waiting for the mode_config lock in drm_kms_helper_poll_enable(), since that will be held as long as i915_hpd_poll_init_work() is reprobing all of the connectors. But we'll address that in the next patch.
--- drivers/gpu/drm/i915/i915_drv.c | 2 -- 1 file changed, 2 deletions(-)
drivers/gpu/drm/i915/i915_drv.c +0 -2
@@ -1602,8 +1602,6 @@ static int i915_drm_resume(struct drm_device *dev)* notifications. * */ intel_hpd_init (dev_priv); -/* Config may have changed between suspend and resume */ -drm_helper_hpd_irq_event (dev);intel_opregion_register (dev_priv);
Signature · 1 line
2.7.4
Re: [Intel-gfx] [PATCH 1/2] drm/i915: Remove redundant reprobe in i915_drm_resume
Quoted 25 lines · Lyude
Weine's investigation on benchmarking the suspend/resume process pointed out a lot of the time in suspend/resume is being spent reprobing. While the reprobing process is a lengthy one for good reason, we don't need to hold up the entire suspend/resume process while we wait for it to finish. Luckily as it turns out, we already trigger a full connector reprobe in
i915_hpd_poll_init_work(), so we can just ditch reprobing ini915_drm_resume()entirely.This won't lead to less time spent resuming just yet since now the bottleneck will be waiting for the
mode_configlock indrm_kms_helper_poll_enable(), since that will be held as long asi915_hpd_poll_init_work()is reprobing all of the connectors. But we'll address that in the next patch.Signed-off-by Lyude <[email protected]>Cc David Weinehall <[email protected]>--- drivers/gpu/drm/i915/i915_drv.c | 2 -- 1 file changed, 2 deletions(-)drivers/gpu/drm/i915/i915_drv.c +0
-0
drivers/gpu/drm/i915/i915_drv.c static int i915_drm_resume(struct drm_device *dev) · line 1606
Quoted 5 lines
drivers/gpu/drm/i915/i915_drv.c +0
-2@@ -1602,8 +1602,6 @@ static int i915_drm_resume(struct drm_device *dev)* notifications. * */ intel_hpd_init (dev_priv); -/* Config may have changed between suspend and resume */ -drm_helper_hpd_irq_event (dev);
The comment is still apt. This code is known to be broken since it doesn't detect a change in monitors (e.g. a change in external connectors from docking) between suspend and resend. We still have to send the uevent.
+ drm_kms_helper_hotplug_event(dev);
which also depends upon us actually reseting the connector->status to unknown in drm_mode_config_reset(), Daniel!
-Chris
Signature · 5 lines
Chris Wilson, Intel Open Source Technology Centre _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [Intel-gfx] [PATCH 1/2] drm/i915: Remove redundant reprobe in i915_drm_resume
Quoted 38 lines · Chris Wilson
Quoted 27 lines · Lyude
Weine's investigation on benchmarking the suspend/resume process pointed out a lot of the time in suspend/resume is being spent reprobing. While the reprobing process is a lengthy one for good reason, we don't need to hold up the entire suspend/resume process while we wait for it to finish. Luckily as it turns out, we already trigger a full connector reprobe in
i915_hpd_poll_init_work(), so we can just ditch reprobing ini915_drm_resume()entirely.This won't lead to less time spent resuming just yet since now the bottleneck will be waiting for the
mode_configlock indrm_kms_helper_poll_enable(), since that will be held as long asi915_hpd_poll_init_work()is reprobing all of the connectors. But we'll address that in the next patch.Signed-off-by Lyude <[email protected]>Cc David Weinehall <[email protected]>---
drivers/gpu/drm/i915/i915_drv.c | 2 --1 file changed, 2 deletions(-)drivers/gpu/drm/i915/i915_drv.c +0
-0drivers/gpu/drm/i915/i915_drv.c static int i915_drm_resume(struct drm_device *dev) · line 1606
Quoted 5 lines
drivers/gpu/drm/i915/i915_drv.c +0
-2@@ -1602,8 +1602,6 @@ static int i915_drm_resume(struct drm_device *dev)* notifications. * */ intel_hpd_init(dev_priv); -/* Config may have changed between suspend and resume */ -drm_helper_hpd_irq_event (dev);The comment is still apt. This code is known to be broken since it doesn't detect a change in monitors (e.g. a change in external connectors from docking) between suspend and resend. We still have to send the uevent.
Review
Quoted 1 line
(quoted diff) +1
-0+ drm_kms_helper_hotplug_event(dev);
I might not have explained myself very well. The way things should look with this patch is like this:
i915_drm_resume()
-> intel_hpd_init()
-> sets dev_priv->hotplug.poll_enabled to true
-> schedules dev_priv->hotplug.poll_init_work
-> continue resume…
at the same time:
i915_hpd_poll_init_work() gets scheduled and starts
-> since dev_priv->hotplug.poll_enabled == false, drm_helper_hpd_irq_event() is called -> drm_helper_hpd_irq_event() reprobes connectors
-> if anything changed, drm_kms_helper_hotplug_event() gets called.
So we're still polling the connectors when coming out of resume just like before, except now we're doing it without needlessly making the whole resume process stall until we're done. We're also no longer reprobing display connectors twice…
Quoted 5 lines
which also depends upon us actually reseting the
connector->statusto unknown indrm_mode_config_reset(), Daniel!
-Chris
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [Intel-gfx] [PATCH 1/2] drm/i915: Remove redundant reprobe in i915_drm_resume
Quoted 41 lines · Lyude Paul
Quoted 40 lines · Chris Wilson
Quoted 28 lines · Lyude
Weine's investigation on benchmarking the suspend/resume process pointed out a lot of the time in suspend/resume is being spent reprobing. While the reprobing process is a lengthy one for good reason, we don't need to hold up the entire suspend/resume process while we wait for it to finish. Luckily as it turns out, we already trigger a full connector reprobe in
i915_hpd_poll_init_work(), so we can just ditch reprobing ini915_drm_resume()entirely.This won't lead to less time spent resuming just yet since now the bottleneck will be waiting for the
mode_configlock indrm_kms_helper_poll_enable(), since that will be held as long asi915_hpd_poll_init_work()is reprobing all of the connectors. But we'll address that in the next patch.Signed-off-by Lyude <[email protected]>Cc David Weinehall <[email protected]>---
drivers/gpu/drm/i915/i915_drv.c | 2 --1 file changed, 2 deletions(-)drivers/gpu/drm/i915/i915_drv.c +0
-0drivers/gpu/drm/i915/i915_drv.c static int i915_drm_resume(struct drm_device *dev) · line 1606
Quoted 5 lines
drivers/gpu/drm/i915/i915_drv.c +0
-2@@ -1602,8 +1602,6 @@ static int i915_drm_resume(struct drm_device *dev)* notifications. * */ intel_hpd_init(dev_priv); -/* Config may have changed between suspend and resume */ -drm_helper_hpd_irq_event (dev);The comment is still apt. This code is known to be broken since it doesn't detect a change in monitors (e.g. a change in external connectors from docking) between suspend and resend. We still have to send the uevent.
Quoted 8 lines
Review
Quoted 1 line
(quoted diff) +1
-0+ drm_kms_helper_hotplug_event(dev);I might not have explained myself very well. The way things should look with this patch is like this:
i915_drm_resume()
->intel_hpd_init()
-> setsdev_priv->hotplug.poll_enabledto true
Whoops, s/true/false/
Quoted 11 lines
-> schedules
dev_priv->hotplug.poll_init_work
-> continue resume…at the same time:
i915_hpd_poll_init_work()gets scheduled and starts
-> sincedev_priv->hotplug.poll_enabled== false,drm_helper_hpd_irq_event()is called
->drm_helper_hpd_irq_event()reprobes connectors
-> if anything changed,drm_kms_helper_hotplug_event()gets called.
Quoted 11 lines
So we're still polling the connectors when coming out of resume just like before, except now we're doing it without needlessly making the whole resume process stall until we're done. We're also no longer reprobing display connectors twice…
Quoted 6 lines
which also depends upon us actually reseting the
connector->statusto unknown indrm_mode_config_reset(), Daniel!
-Chris
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [Intel-gfx] [PATCH 1/2] drm/i915: Remove redundant reprobe in i915_drm_resume
Quoted 47 lines · Lyude Paul
Quoted 46 lines · Lyude Paul
Quoted 40 lines · Chris Wilson
Quoted 28 lines · Lyude
Weine's investigation on benchmarking the suspend/resume process pointed out a lot of the time in suspend/resume is being spent reprobing. While the reprobing process is a lengthy one for good reason, we don't need to hold up the entire suspend/resume process while we wait for it to finish. Luckily as it turns out, we already trigger a full connector reprobe in
i915_hpd_poll_init_work(), so we can just ditch reprobing ini915_drm_resume()entirely.This won't lead to less time spent resuming just yet since now the bottleneck will be waiting for the
mode_configlock indrm_kms_helper_poll_enable(), since that will be held as long asi915_hpd_poll_init_work()is reprobing all of the connectors. But we'll address that in the next patch.Signed-off-by Lyude <[email protected]>Cc David Weinehall <[email protected]>---
drivers/gpu/drm/i915/i915_drv.c | 2 --1 file changed, 2 deletions(-)drivers/gpu/drm/i915/i915_drv.c +0
-0drivers/gpu/drm/i915/i915_drv.c static int i915_drm_resume(struct drm_device *dev) · line 1606
Quoted 5 lines
drivers/gpu/drm/i915/i915_drv.c +0
-2@@ -1602,8 +1602,6 @@ static int i915_drm_resume(struct drm_device *dev)* notifications. * */ intel_hpd_init(dev_priv); -/* Config may have changed between suspend and resume */ -drm_helper_hpd_irq_event (dev);The comment is still apt. This code is known to be broken since it doesn't detect a change in monitors (e.g. a change in external connectors from docking) between suspend and resend. We still have to send the uevent.
Review
Quoted 1 line
(quoted diff) +1
-0+ drm_kms_helper_hotplug_event(dev);I might not have explained myself very well. The way things should look with this patch is like this:
Quoted 15 lines
Quoted 3 lines
i915_drm_resume()
->intel_hpd_init()
-> setsdev_priv->hotplug.poll_enabledto trueWhoops, s/true/false/
Quoted 10 lines
-> schedules
dev_priv->hotplug.poll_init_work
-> continue resume…at the same time:
i915_hpd_poll_init_work()gets scheduled and starts
-> sincedev_priv->hotplug.poll_enabled== false,drm_helper_hpd_irq_event()is called
->drm_helper_hpd_irq_event()reprobes connectors
-> if anything changed,drm_kms_helper_hotplug_event()gets called.
drm_helper_hpd_irq_event() does not detect a change in monitors, for example, so there is no uevent in that case.
-Chris
Signature · 5 lines
Chris Wilson, Intel Open Source Technology Centre _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [Intel-gfx] [PATCH 1/2] drm/i915: Remove redundant reprobe in i915_drm_resume
Quoted 79 lines · Chris Wilson
Quoted 60 lines · Lyude Paul
Quoted 58 lines · Lyude Paul
Quoted 50 lines · Chris Wilson
Quoted 34 lines · Lyude
Weine's investigation on benchmarking the suspend/resume process pointed
out a lot of the time in suspend/resume is being spent reprobing. While
the reprobing process is a lengthy one for good reason, we don't need to
hold up the entire suspend/resume process while we wait for it to finish. Luckily as it turns out, we already trigger a full connector reprobe ini915_hpd_poll_init_work(), so we can just ditch reprobing ini915_drm_resume()entirely.This won't lead to less time spent resuming just yet since now the bottleneck will be waiting for the
mode_configlock indrm_kms_helper_poll_enable(), since that will be held as long asi915_hpd_poll_init_work()is reprobing all of the connectors. But we'll
address that in the next patch.Signed-off-by Lyude <[email protected]>Cc David Weinehall <[email protected]>---
drivers/gpu/drm/i915/i915_drv.c | 2 --1 file changed, 2 deletions(-)drivers/gpu/drm/i915/i915_drv.c +0
-0drivers/gpu/drm/i915/i915_drv.c static int i915_drm_resume(struct drm_device · line 1607
Quoted 6 lines
drivers/gpu/drm/i915/i915_drv.c +0
-2@@ -1602,8 +1602,6 @@ static int i915_drm_resume(struct drm_device*dev) * notifications. * */ intel_hpd_init(dev_priv); -/* Config may have changed between suspend and resume */ -drm_helper_hpd_irq_event (dev);The comment is still apt. This code is known to be broken since it doesn't detect a change in monitors (e.g. a change in external connectors
from docking) between suspend and resend. We still have to send the uevent.Review
Quoted 1 line
(quoted diff) +1
-0+ drm_kms_helper_hotplug_event(dev);I might not have explained myself very well. The way things should look with
this patch is like this:Quoted 17 lines
Quoted 3 lines
i915_drm_resume()
->intel_hpd_init()
-> setsdev_priv->hotplug.poll_enabledto trueWhoops, s/true/false/
Quoted 12 lines
-> schedules
dev_priv->hotplug.poll_init_work
-> continue resume…at the same time:
i915_hpd_poll_init_work()gets scheduled and starts
-> sincedev_priv->hotplug.poll_enabled== false,drm_helper_hpd_irq_event()
is called
->drm_helper_hpd_irq_event()reprobes connectors
-> if anything changed,drm_kms_helper_hotplug_event()gets called.
Quoted 2 lines
drm_helper_hpd_irq_event()does not detect a change in monitors, for example, so there is no uevent in that case.
I still think you're mistaken (and I wouldn't blame you, drm_helper_hpd_irq_event() has a rather misleading name). Contents of drm_helper_hpd_irq_event()
bool drm_helper_hpd_irq_event(struct drm_device *dev)
{
struct drm_connector *connector;
enum drm_connector_status old_status;
bool changed = false;
if (!dev->mode_config.poll_enabled)
return false;
mutex_lock(&dev->mode_config.mutex);
drm_for_each_connector(connector, dev) {
/* Only handle HPD capable connectors. */
if (!(connector->polled & DRM_CONNECTOR_POLL_HPD))
continue;
old_status = connector->status;
connector->status = connector->funcs->detect(connector, false);
DRM_DEBUG_KMS("[CONNECTOR:%d:%s] status updated from %s to
%s\n",
connector->base.id,
connector->name,
drm_get_connector_status_name(old_status),
drm_get_connector_status_name(connector->status));
if (old_status != connector->status)
changed = true;
}
mutex_unlock(&dev->mode_config.mutex);
if (changed)
drm_kms_helper_hotplug_event(dev);
return changed;
}Unless I made a mistake somewhere down the line of writing these: poll_enabled will be set to true (due to the change done in the second patch where we move the call for enabling polling up so that it gets called before intel_hpd_init()), which causes it to go through all the connectors and call connector->funcs->detect() (which will be intel_dp_detect(), intel_hdmi_detect(), etc. And then send a uevent if their status changed.
This being said there's a couple of cases I know we don't handle correctly from writing up igt tests with the chamelium: we don't simulate a disconnect + connect when the EDID changed from what we had last, so if we suspend the system with monitor A connected to port foo and resume it with monitor B connected to port foo, it will still think we're connected to monitor A. However, we don't handle this properly with the current code either.
As for connector->funcs->detect(), it does do a real connector reprobe as opposed to just checking the status of the HPD pins, I'd look at the detect() functions if you're still skeptical.
Quoted 2 lines
-Chris
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [PATCH 1/2] drm/i915: Remove redundant reprobe in i915_drm_resume
In reply to LyudeQuoted 8 lines · Lyude
Weine's investigation on benchmarking the suspend/resume process pointed out a lot of the time in suspend/resume is being spent reprobing. While the reprobing process is a lengthy one for good reason, we don't need to hold up the entire suspend/resume process while we wait for it to finish. Luckily as it turns out, we already trigger a full connector reprobe in
i915_hpd_poll_init_work(), so we can just ditch reprobing ini915_drm_resume()entirely.
Quoted 8 lines
This won't lead to less time spent resuming just yet since now the bottleneck will be waiting for the
mode_configlock indrm_kms_helper_poll_enable(), since that will be held as long asi915_hpd_poll_init_work()is reprobing all of the connectors. But we'll address that in the next patch.Signed-off-by Lyude <[email protected]>Cc David Weinehall <[email protected]>
Testcase: analyze_suspend.py -config config/suspend-callgraph.cfg -filter i915
Quoted 24 lines
--- drivers/gpu/drm/i915/i915_drv.c | 2 -- 1 file changed, 2 deletions(-)drivers/gpu/drm/i915/i915_drv.c +0
-2@@ -1602,8 +1602,6 @@ static int i915_drm_resume(struct drm_device *dev)* notifications. * */ intel_hpd_init (dev_priv); -/* Config may have changed between suspend and resume */ -drm_helper_hpd_irq_event (dev);intel_opregion_register (dev_priv);Signature · 6 lines
2.7.4 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 2/2 drm/i915: Reinit polling before hpd when resuming
In reply to LyudeNow that we don't run the connector reprobing from i915_drm_resume(), we need to make it so we don't have to wait for reprobing to finish so that we actually speed things up. In order to do this, we need to make sure that i915_drm_resume() doesn't get blocked by i915_hpd_poll_init_work() while trying to acquire the mode_config lock that drm_kms_helper_poll_enable() needs to acquire.
The easiest way to do this is to just enable polling before hpd. This shouldn't break anything since at that point we have everything else we need for polling enabled.
As well, this should result in a rather significant improvement in how quickly we can resume the system.
--- drivers/gpu/drm/i915/i915_drv.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/i915_drv.c +2 -1
@@ -1595,6 +1595,8 @@ static int i915_drm_resume(struct drm_device *dev)intel_display_resume (dev); +drm_kms_helper_poll_enable (dev); +/* * ... but also need to make sure that hotplug processing * doesn't cause havoc. Like in the driver load code we don't
@@ -1614,7 +1616,6 @@ static int i915_drm_resume(struct drm_device *dev)intel_opregion_notify_adapter (dev_priv,PCI_D0 );intel_autoenable_gt_powersave (dev_priv); -drm_kms_helper_poll_enable (dev);enable_rpm_wakeref_asserts (dev_priv);
Signature · 6 lines
2.7.4 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [PATCH 2/2] drm/i915: Reinit polling before hpd when resuming
Quoted 11 lines · Lyude
Now that we don't run the connector reprobing from
i915_drm_resume(), we need to make it so we don't have to wait for reprobing to finish so that we actually speed things up. In order to do this, we need to make sure thati915_drm_resume()doesn't get blocked byi915_hpd_poll_init_work()while trying to acquire themode_configlock thatdrm_kms_helper_poll_enable()needs to acquire.The easiest way to do this is to just enable polling before hpd. This shouldn't break anything since at that point we have everything else we need for polling enabled.
Quoted 5 lines
As well, this should result in a rather significant improvement in how quickly we can resume the system.
Signed-off-by Lyude <[email protected]>Cc David Weinehall <[email protected]>
Testcase: analyze_suspend.py -config config/suspend-callgraph.cfg -filter i915
Quoted 32 lines
--- drivers/gpu/drm/i915/i915_drv.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/i915_drv.c +2
-1@@ -1595,6 +1595,8 @@ static int i915_drm_resume(struct drm_device *dev)intel_display_resume (dev); +drm_kms_helper_poll_enable (dev); +/* * ... but also need to make sure that hotplug processing * doesn't cause havoc. Like in the driver load code we don't @@ -1614,7 +1616,6 @@ static int i915_drm_resume(struct drm_device *dev)intel_opregion_notify_adapter (dev_priv,PCI_D0 );intel_autoenable_gt_powersave (dev_priv); -drm_kms_helper_poll_enable (dev);enable_rpm_wakeref_asserts (dev_priv);Signature · 6 lines
2.7.4 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI✓ Fi.CI.BAT: success for Small fixes to speed up resume
In reply to Lyude== Series Details ==
== Series Details ==
Series: Small fixes to speed up resume
URL : https://patchwork.freedesktop.org/series/14787/
State : success
== Summary ==
Series 14787v1 Small fixes to speed up resume
https://patchwork.freedesktop.org/api/1.0/series/14787/revisions/1/mbox/
fi-bdw-5557u total:241 pass:226 dwarn:0 dfail:0 fail:0 skip:15 fi-bsw-n3050 total:241 pass:201 dwarn:0 dfail:0 fail:0 skip:40 fi-bxt-t5700 total:241 pass:213 dwarn:0 dfail:0 fail:0 skip:28 fi-byt-j1900 total:241 pass:213 dwarn:0 dfail:0 fail:0 skip:28 fi-byt-n2820 total:241 pass:209 dwarn:0 dfail:0 fail:0 skip:32 fi-hsw-4770 total:241 pass:221 dwarn:0 dfail:0 fail:0 skip:20 fi-hsw-4770r total:241 pass:221 dwarn:0 dfail:0 fail:0 skip:20 fi-ilk-650 total:241 pass:188 dwarn:0 dfail:0 fail:0 skip:53 fi-ivb-3520m total:241 pass:219 dwarn:0 dfail:0 fail:0 skip:22 fi-ivb-3770 total:241 pass:219 dwarn:0 dfail:0 fail:0 skip:22 fi-kbl-7200u total:241 pass:219 dwarn:0 dfail:0 fail:0 skip:22 fi-skl-6260u total:241 pass:227 dwarn:0 dfail:0 fail:0 skip:14 fi-skl-6700hq total:241 pass:220 dwarn:0 dfail:0 fail:0 skip:21 fi-skl-6700k total:241 pass:219 dwarn:1 dfail:0 fail:0 skip:21 fi-skl-6770hq total:241 pass:227 dwarn:0 dfail:0 fail:0 skip:14 fi-snb-2520m total:241 pass:209 dwarn:0 dfail:0 fail:0 skip:32 fi-snb-2600 total:241 pass:208 dwarn:0 dfail:0 fail:0 skip:33
8a1c897ee1d0d93b8e70991becb6f9f8488dba1b drm-intel-nightly: 2016y-11m-03d-13h-53m-22s UTC integration manifest 643b3b8 drm/i915: Reinit polling before hpd when resuming
3f36aca drm/i915: Remove redundant reprobe in i915_drm_resume
== Logs ==
For more details see: https://intel-gfx-ci.01.org/CI/Patchwork_2898/
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx