* [PATCH v5] drm/i915/psr: Account for sink CRC raciness on some panels
@ 2017-08-09 20:40 Jim Bride
2017-08-09 21:07 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-08-15 16:58 ` [PATCH v5] " Jim Bride
0 siblings, 2 replies; 5+ messages in thread
From: Jim Bride @ 2017-08-09 20:40 UTC (permalink / raw)
To: intel-gfx; +Cc: Jani Nikula, Paulo Zanoni, Rodrigo Vivi
According to the eDP spec, when the count field in TEST_SINK_MISC
increments then the six bytes of sink CRC information in the DPCD
should be valid. Unfortunately, this doesn't seem to be the case
on some panels, and as a result we get some incorrect and inconsistent
values from the sink CRC DPCD locations at times. This problem exhibits
itself more on faster processors (relative failure rates HSW < SKL < KBL.)
In order to try and account for this, we try a lot harder to read the sink
CRC until we get consistent values twice in a row before returning what we
read and delay for a time before trying to read. We still see some
occasional failures, but reading the sink CRC is much more reliable,
particularly on SKL, with these changes than without.
v2: * Reduce number of retries when reading the sink CRC (Jani)
* Refactor to minimize changes to the code (Jani)
* Rebase
v3: * Rebase
v4: * Switch from do-while to for loop when reading CRC values (Jani)
* Rebase
v5: * Checkpatch cleanup and commit message tweaks
* Rebase
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>
Signed-off-by: Jim Bride <jim.bride@linux.intel.com>
---
drivers/gpu/drm/i915/intel_dp.c | 32 +++++++++++++++++++++++++++++---
1 file changed, 29 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
index 76c8a0b..b64757c 100644
--- a/drivers/gpu/drm/i915/intel_dp.c
+++ b/drivers/gpu/drm/i915/intel_dp.c
@@ -3906,6 +3906,10 @@ int intel_dp_sink_crc(struct intel_dp *intel_dp, u8 *crc)
u8 buf;
int count, ret;
int attempts = 6;
+ u8 old_crc[6];
+
+ if (crc == NULL)
+ return -ENOMEM;
ret = intel_dp_sink_crc_start(intel_dp);
if (ret)
@@ -3929,11 +3933,33 @@ int intel_dp_sink_crc(struct intel_dp *intel_dp, u8 *crc)
goto stop;
}
- if (drm_dp_dpcd_read(&intel_dp->aux, DP_TEST_CRC_R_CR, crc, 6) < 0) {
- ret = -EIO;
- goto stop;
+ /*
+ * Sometimes it takes a while for the "real" CRC values to land in
+ * the DPCD, so try several times until we get two reads in a row
+ * that are the same. If we're an eDP panel, delay between reads
+ * for a while since the values take a bit longer to propagate.
+ */
+ for (attempts = 0; attempts < 6; attempts++) {
+ intel_wait_for_vblank(dev_priv, intel_crtc->pipe);
+
+ if (drm_dp_dpcd_read(&intel_dp->aux, DP_TEST_CRC_R_CR,
+ crc, 6) < 0) {
+ ret = -EIO;
+ break;
+ }
+
+ if (attempts && memcmp(old_crc, crc, 6) == 0)
+ break;
+ memcpy(old_crc, crc, 6);
+
+ if (is_edp(intel_dp))
+ usleep_range(20000, 25000);
}
+ if (attempts == 6) {
+ DRM_DEBUG_KMS("Failed to get CRC after 6 attempts.\n");
+ ret = -ETIMEDOUT;
+ }
stop:
intel_dp_sink_crc_stop(intel_dp);
return ret;
--
2.7.4
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 5+ messages in thread
* ✓ Fi.CI.BAT: success for drm/i915/psr: Account for sink CRC raciness on some panels
2017-08-09 20:40 [PATCH v5] drm/i915/psr: Account for sink CRC raciness on some panels Jim Bride
@ 2017-08-09 21:07 ` Patchwork
2017-08-15 16:58 ` [PATCH v5] " Jim Bride
1 sibling, 0 replies; 5+ messages in thread
From: Patchwork @ 2017-08-09 21:07 UTC (permalink / raw)
To: Jim Bride; +Cc: intel-gfx
== Series Details ==
Series: drm/i915/psr: Account for sink CRC raciness on some panels
URL : https://patchwork.freedesktop.org/series/28583/
State : success
== Summary ==
Series 28583v1 drm/i915/psr: Account for sink CRC raciness on some panels
https://patchwork.freedesktop.org/api/1.0/series/28583/revisions/1/mbox/
Test gem_exec_flush:
Subgroup basic-batch-kernel-default-uc:
fail -> PASS (fi-snb-2600) fdo#100007
fdo#100007 https://bugs.freedesktop.org/show_bug.cgi?id=100007
fi-bdw-5557u total:279 pass:268 dwarn:0 dfail:0 fail:0 skip:11 time:436s
fi-bdw-gvtdvm total:279 pass:265 dwarn:0 dfail:0 fail:0 skip:14 time:417s
fi-blb-e6850 total:279 pass:224 dwarn:1 dfail:0 fail:0 skip:54 time:357s
fi-bsw-n3050 total:279 pass:243 dwarn:0 dfail:0 fail:0 skip:36 time:507s
fi-bxt-j4205 total:279 pass:260 dwarn:0 dfail:0 fail:0 skip:19 time:486s
fi-byt-j1900 total:279 pass:254 dwarn:1 dfail:0 fail:0 skip:24 time:521s
fi-glk-2a total:279 pass:260 dwarn:0 dfail:0 fail:0 skip:19 time:585s
fi-hsw-4770 total:279 pass:263 dwarn:0 dfail:0 fail:0 skip:16 time:431s
fi-hsw-4770r total:279 pass:263 dwarn:0 dfail:0 fail:0 skip:16 time:403s
fi-ilk-650 total:279 pass:229 dwarn:0 dfail:0 fail:0 skip:50 time:419s
fi-ivb-3520m total:279 pass:261 dwarn:0 dfail:0 fail:0 skip:18 time:511s
fi-ivb-3770 total:279 pass:261 dwarn:0 dfail:0 fail:0 skip:18 time:476s
fi-kbl-7500u total:279 pass:261 dwarn:0 dfail:0 fail:0 skip:18 time:458s
fi-kbl-7560u total:279 pass:269 dwarn:0 dfail:0 fail:0 skip:10 time:567s
fi-kbl-r total:279 pass:261 dwarn:0 dfail:0 fail:0 skip:18 time:576s
fi-pnv-d510 total:279 pass:223 dwarn:1 dfail:0 fail:0 skip:55 time:533s
fi-skl-6260u total:279 pass:269 dwarn:0 dfail:0 fail:0 skip:10 time:462s
fi-skl-6700k total:279 pass:261 dwarn:0 dfail:0 fail:0 skip:18 time:647s
fi-skl-6770hq total:279 pass:269 dwarn:0 dfail:0 fail:0 skip:10 time:464s
fi-skl-gvtdvm total:279 pass:266 dwarn:0 dfail:0 fail:0 skip:13 time:432s
fi-skl-x1585l total:279 pass:269 dwarn:0 dfail:0 fail:0 skip:10 time:484s
fi-snb-2520m total:279 pass:251 dwarn:0 dfail:0 fail:0 skip:28 time:550s
fi-snb-2600 total:279 pass:250 dwarn:0 dfail:0 fail:0 skip:29 time:406s
2d0288b5b28c0d67460f0258a41bb4f78b812f29 drm-tip: 2017y-08m-09d-18h-09m-54s UTC integration manifest
0ecc35180f53 drm/i915/psr: Account for sink CRC raciness on some panels
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_5358/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH v5] drm/i915/psr: Account for sink CRC raciness on some panels
2017-08-09 20:40 [PATCH v5] drm/i915/psr: Account for sink CRC raciness on some panels Jim Bride
2017-08-09 21:07 ` ✓ Fi.CI.BAT: success for " Patchwork
@ 2017-08-15 16:58 ` Jim Bride
2017-08-15 23:41 ` Rodrigo Vivi
1 sibling, 1 reply; 5+ messages in thread
From: Jim Bride @ 2017-08-15 16:58 UTC (permalink / raw)
To: intel-gfx; +Cc: Jani Nikula, Paulo Zanoni, Rodrigo Vivi
On Wed, Aug 09, 2017 at 01:40:00PM -0700, Jim Bride wrote:
> According to the eDP spec, when the count field in TEST_SINK_MISC
> increments then the six bytes of sink CRC information in the DPCD
> should be valid. Unfortunately, this doesn't seem to be the case
> on some panels, and as a result we get some incorrect and inconsistent
> values from the sink CRC DPCD locations at times. This problem exhibits
> itself more on faster processors (relative failure rates HSW < SKL < KBL.)
> In order to try and account for this, we try a lot harder to read the sink
> CRC until we get consistent values twice in a row before returning what we
> read and delay for a time before trying to read. We still see some
> occasional failures, but reading the sink CRC is much more reliable,
> particularly on SKL, with these changes than without.
>
> v2: * Reduce number of retries when reading the sink CRC (Jani)
> * Refactor to minimize changes to the code (Jani)
> * Rebase
> v3: * Rebase
> v4: * Switch from do-while to for loop when reading CRC values (Jani)
> * Rebase
> v5: * Checkpatch cleanup and commit message tweaks
> * Rebase
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
> Cc: Jani Nikula <jani.nikula@intel.com>
I think I addressed all previous review comments for this patch. Any
thoughts?
Jim
> Signed-off-by: Jim Bride <jim.bride@linux.intel.com>
> ---
> drivers/gpu/drm/i915/intel_dp.c | 32 +++++++++++++++++++++++++++++---
> 1 file changed, 29 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> index 76c8a0b..b64757c 100644
> --- a/drivers/gpu/drm/i915/intel_dp.c
> +++ b/drivers/gpu/drm/i915/intel_dp.c
> @@ -3906,6 +3906,10 @@ int intel_dp_sink_crc(struct intel_dp *intel_dp, u8 *crc)
> u8 buf;
> int count, ret;
> int attempts = 6;
> + u8 old_crc[6];
> +
> + if (crc == NULL)
> + return -ENOMEM;
>
> ret = intel_dp_sink_crc_start(intel_dp);
> if (ret)
> @@ -3929,11 +3933,33 @@ int intel_dp_sink_crc(struct intel_dp *intel_dp, u8 *crc)
> goto stop;
> }
>
> - if (drm_dp_dpcd_read(&intel_dp->aux, DP_TEST_CRC_R_CR, crc, 6) < 0) {
> - ret = -EIO;
> - goto stop;
> + /*
> + * Sometimes it takes a while for the "real" CRC values to land in
> + * the DPCD, so try several times until we get two reads in a row
> + * that are the same. If we're an eDP panel, delay between reads
> + * for a while since the values take a bit longer to propagate.
> + */
> + for (attempts = 0; attempts < 6; attempts++) {
> + intel_wait_for_vblank(dev_priv, intel_crtc->pipe);
> +
> + if (drm_dp_dpcd_read(&intel_dp->aux, DP_TEST_CRC_R_CR,
> + crc, 6) < 0) {
> + ret = -EIO;
> + break;
> + }
> +
> + if (attempts && memcmp(old_crc, crc, 6) == 0)
> + break;
> + memcpy(old_crc, crc, 6);
> +
> + if (is_edp(intel_dp))
> + usleep_range(20000, 25000);
> }
>
> + if (attempts == 6) {
> + DRM_DEBUG_KMS("Failed to get CRC after 6 attempts.\n");
> + ret = -ETIMEDOUT;
> + }
> stop:
> intel_dp_sink_crc_stop(intel_dp);
> return ret;
> --
> 2.7.4
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH v5] drm/i915/psr: Account for sink CRC raciness on some panels
2017-08-15 16:58 ` [PATCH v5] " Jim Bride
@ 2017-08-15 23:41 ` Rodrigo Vivi
2017-08-16 17:32 ` Jim Bride
0 siblings, 1 reply; 5+ messages in thread
From: Rodrigo Vivi @ 2017-08-15 23:41 UTC (permalink / raw)
To: Jim Bride; +Cc: Jani Nikula, intel-gfx, Paulo Zanoni, Rodrigo Vivi
On Tue, Aug 15, 2017 at 9:58 AM, Jim Bride <jim.bride@linux.intel.com> wrote:
> On Wed, Aug 09, 2017 at 01:40:00PM -0700, Jim Bride wrote:
>> According to the eDP spec, when the count field in TEST_SINK_MISC
>> increments then the six bytes of sink CRC information in the DPCD
>> should be valid. Unfortunately, this doesn't seem to be the case
>> on some panels, and as a result we get some incorrect and inconsistent
>> values from the sink CRC DPCD locations at times. This problem exhibits
>> itself more on faster processors (relative failure rates HSW < SKL < KBL.)
>> In order to try and account for this, we try a lot harder to read the sink
>> CRC until we get consistent values twice in a row before returning what we
>> read and delay for a time before trying to read. We still see some
>> occasional failures, but reading the sink CRC is much more reliable,
>> particularly on SKL, with these changes than without.
>>
>> v2: * Reduce number of retries when reading the sink CRC (Jani)
>> * Refactor to minimize changes to the code (Jani)
>> * Rebase
>> v3: * Rebase
>> v4: * Switch from do-while to for loop when reading CRC values (Jani)
>> * Rebase
>> v5: * Checkpatch cleanup and commit message tweaks
>> * Rebase
>> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
>> Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
>> Cc: Jani Nikula <jani.nikula@intel.com>
>
> I think I addressed all previous review comments for this patch. Any
> thoughts?
I suffered a lot with this unreliable sink crcs in the past. As you I tried many
different things like this, but they are still unreliable.
So I believe I'm in favor of one of DK's suggestion:
" On the other hand, since the only consumers of dp sink crc are tests,
why can't the kernel just dump what it reads to debugfs and let the test
deal with erroneous results?
"
So let's keep the kernel doing the right thing by the spec and try to
change test cases to deal with this bad values.
Or let's find some other way to test this without sink crc... and
anyways I believe that we should just drop this patch.
>
> Jim
>
>> Signed-off-by: Jim Bride <jim.bride@linux.intel.com>
>> ---
>> drivers/gpu/drm/i915/intel_dp.c | 32 +++++++++++++++++++++++++++++---
>> 1 file changed, 29 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
>> index 76c8a0b..b64757c 100644
>> --- a/drivers/gpu/drm/i915/intel_dp.c
>> +++ b/drivers/gpu/drm/i915/intel_dp.c
>> @@ -3906,6 +3906,10 @@ int intel_dp_sink_crc(struct intel_dp *intel_dp, u8 *crc)
>> u8 buf;
>> int count, ret;
>> int attempts = 6;
>> + u8 old_crc[6];
>> +
>> + if (crc == NULL)
>> + return -ENOMEM;
>>
>> ret = intel_dp_sink_crc_start(intel_dp);
>> if (ret)
>> @@ -3929,11 +3933,33 @@ int intel_dp_sink_crc(struct intel_dp *intel_dp, u8 *crc)
>> goto stop;
>> }
>>
>> - if (drm_dp_dpcd_read(&intel_dp->aux, DP_TEST_CRC_R_CR, crc, 6) < 0) {
>> - ret = -EIO;
>> - goto stop;
>> + /*
>> + * Sometimes it takes a while for the "real" CRC values to land in
>> + * the DPCD, so try several times until we get two reads in a row
>> + * that are the same. If we're an eDP panel, delay between reads
>> + * for a while since the values take a bit longer to propagate.
>> + */
>> + for (attempts = 0; attempts < 6; attempts++) {
>> + intel_wait_for_vblank(dev_priv, intel_crtc->pipe);
>> +
>> + if (drm_dp_dpcd_read(&intel_dp->aux, DP_TEST_CRC_R_CR,
>> + crc, 6) < 0) {
>> + ret = -EIO;
>> + break;
>> + }
>> +
>> + if (attempts && memcmp(old_crc, crc, 6) == 0)
>> + break;
>> + memcpy(old_crc, crc, 6);
>> +
>> + if (is_edp(intel_dp))
>> + usleep_range(20000, 25000);
>> }
>>
>> + if (attempts == 6) {
>> + DRM_DEBUG_KMS("Failed to get CRC after 6 attempts.\n");
>> + ret = -ETIMEDOUT;
>> + }
>> stop:
>> intel_dp_sink_crc_stop(intel_dp);
>> return ret;
>> --
>> 2.7.4
>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Rodrigo Vivi
Blog: http://blog.vivi.eng.br
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH v5] drm/i915/psr: Account for sink CRC raciness on some panels
2017-08-15 23:41 ` Rodrigo Vivi
@ 2017-08-16 17:32 ` Jim Bride
0 siblings, 0 replies; 5+ messages in thread
From: Jim Bride @ 2017-08-16 17:32 UTC (permalink / raw)
To: Rodrigo Vivi; +Cc: Jani Nikula, intel-gfx, Paulo Zanoni, Rodrigo Vivi
On Tue, Aug 15, 2017 at 04:41:52PM -0700, Rodrigo Vivi wrote:
> On Tue, Aug 15, 2017 at 9:58 AM, Jim Bride <jim.bride@linux.intel.com> wrote:
> > On Wed, Aug 09, 2017 at 01:40:00PM -0700, Jim Bride wrote:
> >> According to the eDP spec, when the count field in TEST_SINK_MISC
> >> increments then the six bytes of sink CRC information in the DPCD
> >> should be valid. Unfortunately, this doesn't seem to be the case
> >> on some panels, and as a result we get some incorrect and inconsistent
> >> values from the sink CRC DPCD locations at times. This problem exhibits
> >> itself more on faster processors (relative failure rates HSW < SKL < KBL.)
> >> In order to try and account for this, we try a lot harder to read the sink
> >> CRC until we get consistent values twice in a row before returning what we
> >> read and delay for a time before trying to read. We still see some
> >> occasional failures, but reading the sink CRC is much more reliable,
> >> particularly on SKL, with these changes than without.
> >>
> >> v2: * Reduce number of retries when reading the sink CRC (Jani)
> >> * Refactor to minimize changes to the code (Jani)
> >> * Rebase
> >> v3: * Rebase
> >> v4: * Switch from do-while to for loop when reading CRC values (Jani)
> >> * Rebase
> >> v5: * Checkpatch cleanup and commit message tweaks
> >> * Rebase
> >> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> >> Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
> >> Cc: Jani Nikula <jani.nikula@intel.com>
> >
> > I think I addressed all previous review comments for this patch. Any
> > thoughts?
>
> I suffered a lot with this unreliable sink crcs in the past. As you I tried many
> different things like this, but they are still unreliable.
>
> So I believe I'm in favor of one of DK's suggestion:
> " On the other hand, since the only consumers of dp sink crc are tests,
> why can't the kernel just dump what it reads to debugfs and let the test
> deal with erroneous results?
> "
> So let's keep the kernel doing the right thing by the spec and try to
> change test cases to deal with this bad values.
Ok. I moved the logic into the IGT library's call for reading sink
crcs.
> Or let's find some other way to test this without sink crc... and
> anyways I believe that we should just drop this patch.
This is the longer-term plan. We need similar tests for PSR 2,
which doesn't support sink crcs, anyhow.
Jim
> >
> > Jim
> >
> >> Signed-off-by: Jim Bride <jim.bride@linux.intel.com>
> >> ---
> >> drivers/gpu/drm/i915/intel_dp.c | 32 +++++++++++++++++++++++++++++---
> >> 1 file changed, 29 insertions(+), 3 deletions(-)
> >>
> >> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> >> index 76c8a0b..b64757c 100644
> >> --- a/drivers/gpu/drm/i915/intel_dp.c
> >> +++ b/drivers/gpu/drm/i915/intel_dp.c
> >> @@ -3906,6 +3906,10 @@ int intel_dp_sink_crc(struct intel_dp *intel_dp, u8 *crc)
> >> u8 buf;
> >> int count, ret;
> >> int attempts = 6;
> >> + u8 old_crc[6];
> >> +
> >> + if (crc == NULL)
> >> + return -ENOMEM;
> >>
> >> ret = intel_dp_sink_crc_start(intel_dp);
> >> if (ret)
> >> @@ -3929,11 +3933,33 @@ int intel_dp_sink_crc(struct intel_dp *intel_dp, u8 *crc)
> >> goto stop;
> >> }
> >>
> >> - if (drm_dp_dpcd_read(&intel_dp->aux, DP_TEST_CRC_R_CR, crc, 6) < 0) {
> >> - ret = -EIO;
> >> - goto stop;
> >> + /*
> >> + * Sometimes it takes a while for the "real" CRC values to land in
> >> + * the DPCD, so try several times until we get two reads in a row
> >> + * that are the same. If we're an eDP panel, delay between reads
> >> + * for a while since the values take a bit longer to propagate.
> >> + */
> >> + for (attempts = 0; attempts < 6; attempts++) {
> >> + intel_wait_for_vblank(dev_priv, intel_crtc->pipe);
> >> +
> >> + if (drm_dp_dpcd_read(&intel_dp->aux, DP_TEST_CRC_R_CR,
> >> + crc, 6) < 0) {
> >> + ret = -EIO;
> >> + break;
> >> + }
> >> +
> >> + if (attempts && memcmp(old_crc, crc, 6) == 0)
> >> + break;
> >> + memcpy(old_crc, crc, 6);
> >> +
> >> + if (is_edp(intel_dp))
> >> + usleep_range(20000, 25000);
> >> }
> >>
> >> + if (attempts == 6) {
> >> + DRM_DEBUG_KMS("Failed to get CRC after 6 attempts.\n");
> >> + ret = -ETIMEDOUT;
> >> + }
> >> stop:
> >> intel_dp_sink_crc_stop(intel_dp);
> >> return ret;
> >> --
> >> 2.7.4
> >>
> >> _______________________________________________
> >> Intel-gfx mailing list
> >> Intel-gfx@lists.freedesktop.org
> >> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
>
>
> --
> Rodrigo Vivi
> Blog: http://blog.vivi.eng.br
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2017-08-16 17:35 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-08-09 20:40 [PATCH v5] drm/i915/psr: Account for sink CRC raciness on some panels Jim Bride
2017-08-09 21:07 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-08-15 16:58 ` [PATCH v5] " Jim Bride
2017-08-15 23:41 ` Rodrigo Vivi
2017-08-16 17:32 ` Jim Bride
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox