* [PATCH] drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-10-31 21:48 ` Manasi Navare
0 siblings, 0 replies; 30+ messages in thread
From: Manasi Navare @ 2019-10-31 21:48 UTC (permalink / raw)
To: intel-gfx, dri-devel; +Cc: Dave Airlie
In case of tiled displays, if we hotplug just one connector,
fbcon currently just selects the preferred mode and if it is
tiled mode then that becomes a problem if rest of the tiles are
not present.
So in the fbdev driver on hotplug when we probe the client modeset,
we we dont find all the connectors for all tiles, then on a connector
with one tile, just fallback to the first available non tiled mode
to display over a single connector.
Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Suggested-by: Dave Airlie <airlied@redhat.com>
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Cc: Dave Airlie <airlied@redhat.com>
Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
---
drivers/gpu/drm/drm_client_modeset.c | 29 ++++++++++++++++++++++++++++
1 file changed, 29 insertions(+)
diff --git a/drivers/gpu/drm/drm_client_modeset.c b/drivers/gpu/drm/drm_client_modeset.c
index 895b73f23079..e28a723587db 100644
--- a/drivers/gpu/drm/drm_client_modeset.c
+++ b/drivers/gpu/drm/drm_client_modeset.c
@@ -114,6 +114,20 @@ drm_client_find_modeset(struct drm_client_dev *client, struct drm_crtc *crtc)
return NULL;
}
+static struct drm_display_mode *
+drm_connector_fallback_non_tiled_mode(struct drm_connector *connector)
+{
+ struct drm_display_mode *mode;
+
+ list_for_each_entry(mode, &connector->modes, head) {
+ if (mode->hdisplay == connector->tile_h_size &&
+ mode->vdisplay == connector->tile_v_size)
+ continue;
+ return mode;
+ }
+ return NULL;
+}
+
static struct drm_display_mode *
drm_connector_has_preferred_mode(struct drm_connector *connector, int width, int height)
{
@@ -348,8 +362,17 @@ static bool drm_client_target_preferred(struct drm_connector **connectors,
struct drm_connector *connector;
u64 conn_configured = 0;
int tile_pass = 0;
+ int num_tiled_conns = 0;
int i;
+ for (i = 0; i < connector_count; i++) {
+ connector = connectors[i];
+ if (!connector->has_tile)
+ continue;
+
+ num_tiled_conns ++;
+ }
+
retry:
for (i = 0; i < connector_count; i++) {
connector = connectors[i];
@@ -394,6 +417,12 @@ static bool drm_client_target_preferred(struct drm_connector **connectors,
connector->base.id, connector->tile_group ? connector->tile_group->id : 0);
modes[i] = drm_connector_has_preferred_mode(connector, width, height);
}
+ if (connector->has_tile &&
+ num_tiled_conns < connector->num_h_tile * connector->num_v_tile) {
+ DRM_DEBUG_KMS("Falling back to non tiled mode on Connector %d\n",
+ connector->base.id);
+ modes[i] = drm_connector_fallback_non_tiled_mode(connector);
+ }
/* No preferred modes, pick one off the list */
if (!modes[i] && !list_empty(&connector->modes)) {
list_for_each_entry(modes[i], &connector->modes, head)
--
2.19.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 30+ messages in thread
* [PATCH] drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-10-31 21:48 ` Manasi Navare
0 siblings, 0 replies; 30+ messages in thread
From: Manasi Navare @ 2019-10-31 21:48 UTC (permalink / raw)
To: intel-gfx, dri-devel; +Cc: Manasi Navare, Dave Airlie
In case of tiled displays, if we hotplug just one connector,
fbcon currently just selects the preferred mode and if it is
tiled mode then that becomes a problem if rest of the tiles are
not present.
So in the fbdev driver on hotplug when we probe the client modeset,
we we dont find all the connectors for all tiles, then on a connector
with one tile, just fallback to the first available non tiled mode
to display over a single connector.
Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Suggested-by: Dave Airlie <airlied@redhat.com>
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Cc: Dave Airlie <airlied@redhat.com>
Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
---
drivers/gpu/drm/drm_client_modeset.c | 29 ++++++++++++++++++++++++++++
1 file changed, 29 insertions(+)
diff --git a/drivers/gpu/drm/drm_client_modeset.c b/drivers/gpu/drm/drm_client_modeset.c
index 895b73f23079..e28a723587db 100644
--- a/drivers/gpu/drm/drm_client_modeset.c
+++ b/drivers/gpu/drm/drm_client_modeset.c
@@ -114,6 +114,20 @@ drm_client_find_modeset(struct drm_client_dev *client, struct drm_crtc *crtc)
return NULL;
}
+static struct drm_display_mode *
+drm_connector_fallback_non_tiled_mode(struct drm_connector *connector)
+{
+ struct drm_display_mode *mode;
+
+ list_for_each_entry(mode, &connector->modes, head) {
+ if (mode->hdisplay == connector->tile_h_size &&
+ mode->vdisplay == connector->tile_v_size)
+ continue;
+ return mode;
+ }
+ return NULL;
+}
+
static struct drm_display_mode *
drm_connector_has_preferred_mode(struct drm_connector *connector, int width, int height)
{
@@ -348,8 +362,17 @@ static bool drm_client_target_preferred(struct drm_connector **connectors,
struct drm_connector *connector;
u64 conn_configured = 0;
int tile_pass = 0;
+ int num_tiled_conns = 0;
int i;
+ for (i = 0; i < connector_count; i++) {
+ connector = connectors[i];
+ if (!connector->has_tile)
+ continue;
+
+ num_tiled_conns ++;
+ }
+
retry:
for (i = 0; i < connector_count; i++) {
connector = connectors[i];
@@ -394,6 +417,12 @@ static bool drm_client_target_preferred(struct drm_connector **connectors,
connector->base.id, connector->tile_group ? connector->tile_group->id : 0);
modes[i] = drm_connector_has_preferred_mode(connector, width, height);
}
+ if (connector->has_tile &&
+ num_tiled_conns < connector->num_h_tile * connector->num_v_tile) {
+ DRM_DEBUG_KMS("Falling back to non tiled mode on Connector %d\n",
+ connector->base.id);
+ modes[i] = drm_connector_fallback_non_tiled_mode(connector);
+ }
/* No preferred modes, pick one off the list */
if (!modes[i] && !list_empty(&connector->modes)) {
list_for_each_entry(modes[i], &connector->modes, head)
--
2.19.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply related [flat|nested] 30+ messages in thread
* [Intel-gfx] [PATCH] drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-10-31 21:48 ` Manasi Navare
0 siblings, 0 replies; 30+ messages in thread
From: Manasi Navare @ 2019-10-31 21:48 UTC (permalink / raw)
To: intel-gfx, dri-devel; +Cc: Dave Airlie
In case of tiled displays, if we hotplug just one connector,
fbcon currently just selects the preferred mode and if it is
tiled mode then that becomes a problem if rest of the tiles are
not present.
So in the fbdev driver on hotplug when we probe the client modeset,
we we dont find all the connectors for all tiles, then on a connector
with one tile, just fallback to the first available non tiled mode
to display over a single connector.
Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Suggested-by: Dave Airlie <airlied@redhat.com>
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Cc: Dave Airlie <airlied@redhat.com>
Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
---
drivers/gpu/drm/drm_client_modeset.c | 29 ++++++++++++++++++++++++++++
1 file changed, 29 insertions(+)
diff --git a/drivers/gpu/drm/drm_client_modeset.c b/drivers/gpu/drm/drm_client_modeset.c
index 895b73f23079..e28a723587db 100644
--- a/drivers/gpu/drm/drm_client_modeset.c
+++ b/drivers/gpu/drm/drm_client_modeset.c
@@ -114,6 +114,20 @@ drm_client_find_modeset(struct drm_client_dev *client, struct drm_crtc *crtc)
return NULL;
}
+static struct drm_display_mode *
+drm_connector_fallback_non_tiled_mode(struct drm_connector *connector)
+{
+ struct drm_display_mode *mode;
+
+ list_for_each_entry(mode, &connector->modes, head) {
+ if (mode->hdisplay == connector->tile_h_size &&
+ mode->vdisplay == connector->tile_v_size)
+ continue;
+ return mode;
+ }
+ return NULL;
+}
+
static struct drm_display_mode *
drm_connector_has_preferred_mode(struct drm_connector *connector, int width, int height)
{
@@ -348,8 +362,17 @@ static bool drm_client_target_preferred(struct drm_connector **connectors,
struct drm_connector *connector;
u64 conn_configured = 0;
int tile_pass = 0;
+ int num_tiled_conns = 0;
int i;
+ for (i = 0; i < connector_count; i++) {
+ connector = connectors[i];
+ if (!connector->has_tile)
+ continue;
+
+ num_tiled_conns ++;
+ }
+
retry:
for (i = 0; i < connector_count; i++) {
connector = connectors[i];
@@ -394,6 +417,12 @@ static bool drm_client_target_preferred(struct drm_connector **connectors,
connector->base.id, connector->tile_group ? connector->tile_group->id : 0);
modes[i] = drm_connector_has_preferred_mode(connector, width, height);
}
+ if (connector->has_tile &&
+ num_tiled_conns < connector->num_h_tile * connector->num_v_tile) {
+ DRM_DEBUG_KMS("Falling back to non tiled mode on Connector %d\n",
+ connector->base.id);
+ modes[i] = drm_connector_fallback_non_tiled_mode(connector);
+ }
/* No preferred modes, pick one off the list */
if (!modes[i] && !list_empty(&connector->modes)) {
list_for_each_entry(modes[i], &connector->modes, head)
--
2.19.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 30+ messages in thread
* ✗ Fi.CI.CHECKPATCH: warning for drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-10-31 23:13 ` Patchwork
0 siblings, 0 replies; 30+ messages in thread
From: Patchwork @ 2019-10-31 23:13 UTC (permalink / raw)
To: Manasi Navare; +Cc: intel-gfx
== Series Details ==
Series: drm/fbdev: Fallback to non tiled mode if all tiles not present
URL : https://patchwork.freedesktop.org/series/68838/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
64383a27c565 drm/fbdev: Fallback to non tiled mode if all tiles not present
-:62: ERROR:SPACING: space prohibited before that '++' (ctx:WxO)
#62: FILE: drivers/gpu/drm/drm_client_modeset.c:373:
+ num_tiled_conns ++;
^
total: 1 errors, 0 warnings, 0 checks, 49 lines checked
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 30+ messages in thread
* [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-10-31 23:13 ` Patchwork
0 siblings, 0 replies; 30+ messages in thread
From: Patchwork @ 2019-10-31 23:13 UTC (permalink / raw)
To: Manasi Navare; +Cc: intel-gfx
== Series Details ==
Series: drm/fbdev: Fallback to non tiled mode if all tiles not present
URL : https://patchwork.freedesktop.org/series/68838/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
64383a27c565 drm/fbdev: Fallback to non tiled mode if all tiles not present
-:62: ERROR:SPACING: space prohibited before that '++' (ctx:WxO)
#62: FILE: drivers/gpu/drm/drm_client_modeset.c:373:
+ num_tiled_conns ++;
^
total: 1 errors, 0 warnings, 0 checks, 49 lines checked
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 30+ messages in thread
* ✓ Fi.CI.BAT: success for drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-10-31 23:41 ` Patchwork
0 siblings, 0 replies; 30+ messages in thread
From: Patchwork @ 2019-10-31 23:41 UTC (permalink / raw)
To: Manasi Navare; +Cc: intel-gfx
== Series Details ==
Series: drm/fbdev: Fallback to non tiled mode if all tiles not present
URL : https://patchwork.freedesktop.org/series/68838/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7234 -> Patchwork_15095
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/index.html
Known issues
------------
Here are the changes found in Patchwork_15095 that come from known issues:
### IGT changes ###
#### Possible fixes ####
* igt@gem_busy@busy-all:
- fi-icl-u3: [DMESG-WARN][1] ([fdo#107724]) -> [PASS][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/fi-icl-u3/igt@gem_busy@busy-all.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/fi-icl-u3/igt@gem_busy@busy-all.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
[fdo#111880]: https://bugs.freedesktop.org/show_bug.cgi?id=111880
[fdo#112096]: https://bugs.freedesktop.org/show_bug.cgi?id=112096
Participating hosts (52 -> 44)
------------------------------
Missing (8): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-pnv-d510 fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_7234 -> Patchwork_15095
CI-20190529: 20190529
CI_DRM_7234: 4163f8c46b6ef75ea32737f08aa3f5fd429a4462 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5255: b21b6a7aaa0db2159f22ee4427804e5a16fe2261 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_15095: 64383a27c565ee7f40d36d69c1265276a10ddfcb @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
64383a27c565 drm/fbdev: Fallback to non tiled mode if all tiles not present
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 30+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-10-31 23:41 ` Patchwork
0 siblings, 0 replies; 30+ messages in thread
From: Patchwork @ 2019-10-31 23:41 UTC (permalink / raw)
To: Manasi Navare; +Cc: intel-gfx
== Series Details ==
Series: drm/fbdev: Fallback to non tiled mode if all tiles not present
URL : https://patchwork.freedesktop.org/series/68838/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7234 -> Patchwork_15095
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/index.html
Known issues
------------
Here are the changes found in Patchwork_15095 that come from known issues:
### IGT changes ###
#### Possible fixes ####
* igt@gem_busy@busy-all:
- fi-icl-u3: [DMESG-WARN][1] ([fdo#107724]) -> [PASS][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/fi-icl-u3/igt@gem_busy@busy-all.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/fi-icl-u3/igt@gem_busy@busy-all.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
[fdo#111880]: https://bugs.freedesktop.org/show_bug.cgi?id=111880
[fdo#112096]: https://bugs.freedesktop.org/show_bug.cgi?id=112096
Participating hosts (52 -> 44)
------------------------------
Missing (8): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-pnv-d510 fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_7234 -> Patchwork_15095
CI-20190529: 20190529
CI_DRM_7234: 4163f8c46b6ef75ea32737f08aa3f5fd429a4462 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5255: b21b6a7aaa0db2159f22ee4427804e5a16fe2261 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_15095: 64383a27c565ee7f40d36d69c1265276a10ddfcb @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
64383a27c565 drm/fbdev: Fallback to non tiled mode if all tiles not present
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 30+ messages in thread
* ✓ Fi.CI.IGT: success for drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-11-02 8:42 ` Patchwork
0 siblings, 0 replies; 30+ messages in thread
From: Patchwork @ 2019-11-02 8:42 UTC (permalink / raw)
To: Manasi Navare; +Cc: intel-gfx
== Series Details ==
Series: drm/fbdev: Fallback to non tiled mode if all tiles not present
URL : https://patchwork.freedesktop.org/series/68838/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7234_full -> Patchwork_15095_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_15095_full:
### IGT changes ###
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@i915_hangman@error-state-capture-rcs0:
- {shard-tglb}: NOTRUN -> [INCOMPLETE][1]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-tglb5/igt@i915_hangman@error-state-capture-rcs0.html
Known issues
------------
Here are the changes found in Patchwork_15095_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_switch@rcs0:
- shard-iclb: [PASS][2] -> [INCOMPLETE][3] ([fdo#107713]) +1 similar issue
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb7/igt@gem_ctx_switch@rcs0.html
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb7/igt@gem_ctx_switch@rcs0.html
* igt@gem_exec_async@concurrent-writes-vebox:
- shard-apl: [PASS][4] -> [INCOMPLETE][5] ([fdo#103927]) +2 similar issues
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-apl1/igt@gem_exec_async@concurrent-writes-vebox.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-apl7/igt@gem_exec_async@concurrent-writes-vebox.html
* igt@gem_exec_basic@basic-vcs1:
- shard-iclb: [PASS][6] -> [SKIP][7] ([fdo#112080]) +8 similar issues
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb2/igt@gem_exec_basic@basic-vcs1.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb5/igt@gem_exec_basic@basic-vcs1.html
* igt@gem_exec_schedule@out-order-bsd2:
- shard-iclb: [PASS][8] -> [SKIP][9] ([fdo#109276]) +12 similar issues
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb2/igt@gem_exec_schedule@out-order-bsd2.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb5/igt@gem_exec_schedule@out-order-bsd2.html
* igt@gem_exec_schedule@pi-ringfull-bsd:
- shard-iclb: [PASS][10] -> [SKIP][11] ([fdo#112146]) +1 similar issue
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb5/igt@gem_exec_schedule@pi-ringfull-bsd.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb1/igt@gem_exec_schedule@pi-ringfull-bsd.html
* igt@gem_ppgtt@blt-vs-render-ctxn:
- shard-glk: [PASS][12] -> [DMESG-WARN][13] ([fdo#105763] / [fdo#106538])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-glk5/igt@gem_ppgtt@blt-vs-render-ctxn.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-glk8/igt@gem_ppgtt@blt-vs-render-ctxn.html
* igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy-gup:
- shard-hsw: [PASS][14] -> [DMESG-WARN][15] ([fdo#111870])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-hsw2/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy-gup.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-hsw2/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy-gup.html
* igt@kms_color@pipe-a-ctm-0-5:
- shard-skl: [PASS][16] -> [DMESG-WARN][17] ([fdo#106107]) +2 similar issues
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-skl7/igt@kms_color@pipe-a-ctm-0-5.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-skl9/igt@kms_color@pipe-a-ctm-0-5.html
* igt@kms_cursor_crc@pipe-a-cursor-dpms:
- shard-kbl: [PASS][18] -> [FAIL][19] ([fdo#103232])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-kbl7/igt@kms_cursor_crc@pipe-a-cursor-dpms.html
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-kbl4/igt@kms_cursor_crc@pipe-a-cursor-dpms.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible:
- shard-skl: [PASS][20] -> [FAIL][21] ([fdo#105363])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-skl1/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-skl10/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
* igt@kms_flip@flip-vs-suspend-interruptible:
- shard-skl: [PASS][22] -> [INCOMPLETE][23] ([fdo#109507])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-skl1/igt@kms_flip@flip-vs-suspend-interruptible.html
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-skl10/igt@kms_flip@flip-vs-suspend-interruptible.html
* igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-pwrite:
- shard-iclb: [PASS][24] -> [FAIL][25] ([fdo#103167]) +3 similar issues
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb5/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-pwrite.html
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb7/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-pwrite.html
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-draw-pwrite:
- shard-glk: [PASS][26] -> [FAIL][27] ([fdo#103167])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-glk1/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-draw-pwrite.html
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-glk5/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-draw-pwrite.html
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-mmap-wc:
- shard-skl: [PASS][28] -> [FAIL][29] ([fdo#103167])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-skl9/igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-mmap-wc.html
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-skl4/igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-mmap-wc.html
* igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min:
- shard-skl: [PASS][30] -> [FAIL][31] ([fdo#108145]) +1 similar issue
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-skl1/igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min.html
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-skl6/igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min.html
* igt@kms_psr@no_drrs:
- shard-iclb: [PASS][32] -> [FAIL][33] ([fdo#108341])
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb4/igt@kms_psr@no_drrs.html
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb1/igt@kms_psr@no_drrs.html
* igt@kms_psr@psr2_basic:
- shard-iclb: [PASS][34] -> [SKIP][35] ([fdo#109441]) +2 similar issues
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb2/igt@kms_psr@psr2_basic.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb4/igt@kms_psr@psr2_basic.html
* igt@kms_vblank@pipe-a-ts-continuation-suspend:
- shard-kbl: [PASS][36] -> [DMESG-WARN][37] ([fdo#108566]) +4 similar issues
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-kbl4/igt@kms_vblank@pipe-a-ts-continuation-suspend.html
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-kbl6/igt@kms_vblank@pipe-a-ts-continuation-suspend.html
* igt@perf@short-reads:
- shard-kbl: [PASS][38] -> [TIMEOUT][39] ([fdo#103183])
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-kbl4/igt@perf@short-reads.html
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-kbl3/igt@perf@short-reads.html
#### Possible fixes ####
* igt@gem_ctx_isolation@vcs1-none:
- shard-iclb: [SKIP][40] ([fdo#109276] / [fdo#112080]) -> [PASS][41] +1 similar issue
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb5/igt@gem_ctx_isolation@vcs1-none.html
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb2/igt@gem_ctx_isolation@vcs1-none.html
* igt@gem_ctx_shared@q-smoketest-default:
- shard-apl: [INCOMPLETE][42] ([fdo#103927]) -> [PASS][43] +1 similar issue
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-apl1/igt@gem_ctx_shared@q-smoketest-default.html
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-apl4/igt@gem_ctx_shared@q-smoketest-default.html
* igt@gem_ctx_switch@vcs1:
- shard-iclb: [SKIP][44] ([fdo#112080]) -> [PASS][45] +5 similar issues
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb8/igt@gem_ctx_switch@vcs1.html
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb4/igt@gem_ctx_switch@vcs1.html
* igt@gem_exec_balancer@smoke:
- shard-iclb: [SKIP][46] ([fdo#110854]) -> [PASS][47]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb3/igt@gem_exec_balancer@smoke.html
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb1/igt@gem_exec_balancer@smoke.html
* igt@gem_exec_create@forked:
- {shard-tglb}: [INCOMPLETE][48] ([fdo#108838] / [fdo#111747]) -> [PASS][49]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-tglb3/igt@gem_exec_create@forked.html
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-tglb8/igt@gem_exec_create@forked.html
* igt@gem_exec_schedule@out-order-bsd:
- shard-iclb: [SKIP][50] ([fdo#112146]) -> [PASS][51]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb2/igt@gem_exec_schedule@out-order-bsd.html
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb5/igt@gem_exec_schedule@out-order-bsd.html
* igt@gem_exec_schedule@preempt-queue-contexts-render:
- {shard-tglb}: [INCOMPLETE][52] ([fdo#111606] / [fdo#111677]) -> [PASS][53]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-tglb6/igt@gem_exec_schedule@preempt-queue-contexts-render.html
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-tglb4/igt@gem_exec_schedule@preempt-queue-contexts-render.html
* igt@gem_sync@basic-all:
- {shard-tglb}: [INCOMPLETE][54] ([fdo#111647]) -> [PASS][55]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-tglb6/igt@gem_sync@basic-all.html
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-tglb4/igt@gem_sync@basic-all.html
* igt@gem_userptr_blits@map-fixed-invalidate-busy:
- shard-hsw: [DMESG-WARN][56] ([fdo#111870]) -> [PASS][57]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-hsw4/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-hsw7/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
* {igt@i915_pm_dc@dc6-psr}:
- shard-iclb: [FAIL][58] ([fdo#110548]) -> [PASS][59]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb6/igt@i915_pm_dc@dc6-psr.html
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb5/igt@i915_pm_dc@dc6-psr.html
* igt@kms_color@pipe-a-ctm-0-25:
- shard-skl: [DMESG-WARN][60] ([fdo#106107]) -> [PASS][61]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-skl8/igt@kms_color@pipe-a-ctm-0-25.html
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-skl10/igt@kms_color@pipe-a-ctm-0-25.html
* igt@kms_cursor_crc@pipe-c-cursor-suspend:
- shard-kbl: [DMESG-WARN][62] ([fdo#108566]) -> [PASS][63] +4 similar issues
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-kbl6/igt@kms_cursor_crc@pipe-c-cursor-suspend.html
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-kbl6/igt@kms_cursor_crc@pipe-c-cursor-suspend.html
* igt@kms_flip@flip-vs-expired-vblank:
- shard-skl: [FAIL][64] ([fdo#105363]) -> [PASS][65]
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-skl7/igt@kms_flip@flip-vs-expired-vblank.html
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-skl6/igt@kms_flip@flip-vs-expired-vblank.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible:
- {shard-tglb}: [INCOMPLETE][66] ([fdo#112031]) -> [PASS][67]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-tglb8/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-tglb4/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
* igt@kms_flip@flip-vs-suspend:
- shard-apl: [DMESG-WARN][68] ([fdo#108566]) -> [PASS][69]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-apl2/igt@kms_flip@flip-vs-suspend.html
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-apl2/igt@kms_flip@flip-vs-suspend.html
* igt@kms_flip@flip-vs-suspend-interruptible:
- shard-snb: [INCOMPLETE][70] ([fdo#105411]) -> [PASS][71]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-snb1/igt@kms_flip@flip-vs-suspend-interruptible.html
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-snb1/igt@kms_flip@flip-vs-suspend-interruptible.html
* igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-pwrite:
- {shard-tglb}: [FAIL][72] ([fdo#103167]) -> [PASS][73] +1 similar issue
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-tglb5/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-pwrite.html
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-tglb1/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-pwrite.html
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-pwrite:
- shard-iclb: [FAIL][74] ([fdo#103167]) -> [PASS][75] +5 similar issues
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb2/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-pwrite.html
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb4/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-pwrite.html
* igt@kms_frontbuffer_tracking@psr-1p-offscren-pri-indfb-draw-blt:
- {shard-tglb}: [INCOMPLETE][76] ([fdo#111747]) -> [PASS][77]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-tglb8/igt@kms_frontbuffer_tracking@psr-1p-offscren-pri-indfb-draw-blt.html
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-tglb8/igt@kms_frontbuffer_tracking@psr-1p-offscren-pri-indfb-draw-blt.html
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-mmap-gtt:
- {shard-tglb}: [INCOMPLETE][78] -> [PASS][79]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-tglb2/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-mmap-gtt.html
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-tglb6/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-mmap-gtt.html
* igt@kms_psr@psr2_primary_mmap_cpu:
- shard-iclb: [SKIP][80] ([fdo#109441]) -> [PASS][81] +3 similar issues
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb5/igt@kms_psr@psr2_primary_mmap_cpu.html
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb2/igt@kms_psr@psr2_primary_mmap_cpu.html
* igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend:
- {shard-tglb}: [INCOMPLETE][82] ([fdo#111850]) -> [PASS][83]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-tglb2/igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend.html
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-tglb2/igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend.html
* igt@prime_busy@hang-bsd2:
- shard-iclb: [SKIP][84] ([fdo#109276]) -> [PASS][85] +15 similar issues
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb6/igt@prime_busy@hang-bsd2.html
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb2/igt@prime_busy@hang-bsd2.html
* igt@prime_vgem@basic-sync-default:
- {shard-tglb}: [INCOMPLETE][86] ([fdo#111930]) -> [PASS][87]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-tglb4/igt@prime_vgem@basic-sync-default.html
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-tglb3/igt@prime_vgem@basic-sync-default.html
#### Warnings ####
* igt@gem_mocs_settings@mocs-isolation-bsd2:
- shard-iclb: [SKIP][88] ([fdo#109276]) -> [FAIL][89] ([fdo#111330])
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb5/igt@gem_mocs_settings@mocs-isolation-bsd2.html
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb2/igt@gem_mocs_settings@mocs-isolation-bsd2.html
* igt@gem_mocs_settings@mocs-reset-bsd2:
- shard-iclb: [FAIL][90] ([fdo#111330]) -> [SKIP][91] ([fdo#109276])
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb4/igt@gem_mocs_settings@mocs-reset-bsd2.html
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb6/igt@gem_mocs_settings@mocs-reset-bsd2.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
[fdo#103183]: https://bugs.freedesktop.org/show_bug.cgi?id=103183
[fdo#103232]: https://bugs.freedesktop.org/show_bug.cgi?id=103232
[fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927
[fdo#105363]: https://bugs.freedesktop.org/show_bug.cgi?id=105363
[fdo#105411]: https://bugs.freedesktop.org/show_bug.cgi?id=105411
[fdo#105763]: https://bugs.freedesktop.org/show_bug.cgi?id=105763
[fdo#106107]: https://bugs.freedesktop.org/show_bug.cgi?id=106107
[fdo#106538]: https://bugs.freedesktop.org/show_bug.cgi?id=106538
[fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#108341]: https://bugs.freedesktop.org/show_bug.cgi?id=108341
[fdo#108566]: https://bugs.freedesktop.org/show_bug.cgi?id=108566
[fdo#108838]: https://bugs.freedesktop.org/show_bug.cgi?id=108838
[fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109507]: https://bugs.freedesktop.org/show_bug.cgi?id=109507
[fdo#110548]: https://bugs.freedesktop.org/show_bug.cgi?id=110548
[fdo#110854]: https://bugs.freedesktop.org/show_bug.cgi?id=110854
[fdo#111330]: https://bugs.freedesktop.org/show_bug.cgi?id=111330
[fdo#111606]: https://bugs.freedesktop.org/show_bug.cgi?id=111606
[fdo#111647]: https://bugs.freedesktop.org/show_bug.cgi?id=111647
[fdo#111677]: https://bugs.freedesktop.org/show_bug.cgi?id=111677
[fdo#111703]: https://bugs.freedesktop.org/show_bug.cgi?id=111703
[fdo#111747]: https://bugs.freedesktop.org/show_bug.cgi?id=111747
[fdo#111831]: https://bugs.freedesktop.org/show_bug.cgi?id=111831
[fdo#111832]: https://bugs.freedesktop.org/show_bug.cgi?id=111832
[fdo#111850]: https://bugs.freedesktop.org/show_bug.cgi?id=111850
[fdo#111870]: https://bugs.freedesktop.org/show_bug.cgi?id=111870
[fdo#111930]: https://bugs.freedesktop.org/show_bug.cgi?id=111930
[fdo#112031]: https://bugs.freedesktop.org/show_bug.cgi?id=112031
[fdo#112080]: https://bugs.freedesktop.org/show_bug.cgi?id=112080
[fdo#112146]: https://bugs.freedesktop.org/show_bug.cgi?id=112146
[fdo#112191]: https://bugs.freedesktop.org/show_bug.cgi?id=112191
Participating hosts (11 -> 11)
------------------------------
No changes in participating ho
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 30+ messages in thread
* [Intel-gfx] ✓ Fi.CI.IGT: success for drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-11-02 8:42 ` Patchwork
0 siblings, 0 replies; 30+ messages in thread
From: Patchwork @ 2019-11-02 8:42 UTC (permalink / raw)
To: Manasi Navare; +Cc: intel-gfx
== Series Details ==
Series: drm/fbdev: Fallback to non tiled mode if all tiles not present
URL : https://patchwork.freedesktop.org/series/68838/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7234_full -> Patchwork_15095_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_15095_full:
### IGT changes ###
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@i915_hangman@error-state-capture-rcs0:
- {shard-tglb}: NOTRUN -> [INCOMPLETE][1]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-tglb5/igt@i915_hangman@error-state-capture-rcs0.html
Known issues
------------
Here are the changes found in Patchwork_15095_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_switch@rcs0:
- shard-iclb: [PASS][2] -> [INCOMPLETE][3] ([fdo#107713]) +1 similar issue
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb7/igt@gem_ctx_switch@rcs0.html
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb7/igt@gem_ctx_switch@rcs0.html
* igt@gem_exec_async@concurrent-writes-vebox:
- shard-apl: [PASS][4] -> [INCOMPLETE][5] ([fdo#103927]) +2 similar issues
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-apl1/igt@gem_exec_async@concurrent-writes-vebox.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-apl7/igt@gem_exec_async@concurrent-writes-vebox.html
* igt@gem_exec_basic@basic-vcs1:
- shard-iclb: [PASS][6] -> [SKIP][7] ([fdo#112080]) +8 similar issues
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb2/igt@gem_exec_basic@basic-vcs1.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb5/igt@gem_exec_basic@basic-vcs1.html
* igt@gem_exec_schedule@out-order-bsd2:
- shard-iclb: [PASS][8] -> [SKIP][9] ([fdo#109276]) +12 similar issues
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb2/igt@gem_exec_schedule@out-order-bsd2.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb5/igt@gem_exec_schedule@out-order-bsd2.html
* igt@gem_exec_schedule@pi-ringfull-bsd:
- shard-iclb: [PASS][10] -> [SKIP][11] ([fdo#112146]) +1 similar issue
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb5/igt@gem_exec_schedule@pi-ringfull-bsd.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb1/igt@gem_exec_schedule@pi-ringfull-bsd.html
* igt@gem_ppgtt@blt-vs-render-ctxn:
- shard-glk: [PASS][12] -> [DMESG-WARN][13] ([fdo#105763] / [fdo#106538])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-glk5/igt@gem_ppgtt@blt-vs-render-ctxn.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-glk8/igt@gem_ppgtt@blt-vs-render-ctxn.html
* igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy-gup:
- shard-hsw: [PASS][14] -> [DMESG-WARN][15] ([fdo#111870])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-hsw2/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy-gup.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-hsw2/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy-gup.html
* igt@kms_color@pipe-a-ctm-0-5:
- shard-skl: [PASS][16] -> [DMESG-WARN][17] ([fdo#106107]) +2 similar issues
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-skl7/igt@kms_color@pipe-a-ctm-0-5.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-skl9/igt@kms_color@pipe-a-ctm-0-5.html
* igt@kms_cursor_crc@pipe-a-cursor-dpms:
- shard-kbl: [PASS][18] -> [FAIL][19] ([fdo#103232])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-kbl7/igt@kms_cursor_crc@pipe-a-cursor-dpms.html
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-kbl4/igt@kms_cursor_crc@pipe-a-cursor-dpms.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible:
- shard-skl: [PASS][20] -> [FAIL][21] ([fdo#105363])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-skl1/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-skl10/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
* igt@kms_flip@flip-vs-suspend-interruptible:
- shard-skl: [PASS][22] -> [INCOMPLETE][23] ([fdo#109507])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-skl1/igt@kms_flip@flip-vs-suspend-interruptible.html
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-skl10/igt@kms_flip@flip-vs-suspend-interruptible.html
* igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-pwrite:
- shard-iclb: [PASS][24] -> [FAIL][25] ([fdo#103167]) +3 similar issues
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb5/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-pwrite.html
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb7/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-pwrite.html
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-draw-pwrite:
- shard-glk: [PASS][26] -> [FAIL][27] ([fdo#103167])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-glk1/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-draw-pwrite.html
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-glk5/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-draw-pwrite.html
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-mmap-wc:
- shard-skl: [PASS][28] -> [FAIL][29] ([fdo#103167])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-skl9/igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-mmap-wc.html
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-skl4/igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-mmap-wc.html
* igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min:
- shard-skl: [PASS][30] -> [FAIL][31] ([fdo#108145]) +1 similar issue
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-skl1/igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min.html
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-skl6/igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min.html
* igt@kms_psr@no_drrs:
- shard-iclb: [PASS][32] -> [FAIL][33] ([fdo#108341])
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb4/igt@kms_psr@no_drrs.html
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb1/igt@kms_psr@no_drrs.html
* igt@kms_psr@psr2_basic:
- shard-iclb: [PASS][34] -> [SKIP][35] ([fdo#109441]) +2 similar issues
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb2/igt@kms_psr@psr2_basic.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb4/igt@kms_psr@psr2_basic.html
* igt@kms_vblank@pipe-a-ts-continuation-suspend:
- shard-kbl: [PASS][36] -> [DMESG-WARN][37] ([fdo#108566]) +4 similar issues
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-kbl4/igt@kms_vblank@pipe-a-ts-continuation-suspend.html
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-kbl6/igt@kms_vblank@pipe-a-ts-continuation-suspend.html
* igt@perf@short-reads:
- shard-kbl: [PASS][38] -> [TIMEOUT][39] ([fdo#103183])
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-kbl4/igt@perf@short-reads.html
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-kbl3/igt@perf@short-reads.html
#### Possible fixes ####
* igt@gem_ctx_isolation@vcs1-none:
- shard-iclb: [SKIP][40] ([fdo#109276] / [fdo#112080]) -> [PASS][41] +1 similar issue
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb5/igt@gem_ctx_isolation@vcs1-none.html
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb2/igt@gem_ctx_isolation@vcs1-none.html
* igt@gem_ctx_shared@q-smoketest-default:
- shard-apl: [INCOMPLETE][42] ([fdo#103927]) -> [PASS][43] +1 similar issue
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-apl1/igt@gem_ctx_shared@q-smoketest-default.html
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-apl4/igt@gem_ctx_shared@q-smoketest-default.html
* igt@gem_ctx_switch@vcs1:
- shard-iclb: [SKIP][44] ([fdo#112080]) -> [PASS][45] +5 similar issues
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb8/igt@gem_ctx_switch@vcs1.html
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb4/igt@gem_ctx_switch@vcs1.html
* igt@gem_exec_balancer@smoke:
- shard-iclb: [SKIP][46] ([fdo#110854]) -> [PASS][47]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb3/igt@gem_exec_balancer@smoke.html
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb1/igt@gem_exec_balancer@smoke.html
* igt@gem_exec_create@forked:
- {shard-tglb}: [INCOMPLETE][48] ([fdo#108838] / [fdo#111747]) -> [PASS][49]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-tglb3/igt@gem_exec_create@forked.html
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-tglb8/igt@gem_exec_create@forked.html
* igt@gem_exec_schedule@out-order-bsd:
- shard-iclb: [SKIP][50] ([fdo#112146]) -> [PASS][51]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb2/igt@gem_exec_schedule@out-order-bsd.html
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb5/igt@gem_exec_schedule@out-order-bsd.html
* igt@gem_exec_schedule@preempt-queue-contexts-render:
- {shard-tglb}: [INCOMPLETE][52] ([fdo#111606] / [fdo#111677]) -> [PASS][53]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-tglb6/igt@gem_exec_schedule@preempt-queue-contexts-render.html
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-tglb4/igt@gem_exec_schedule@preempt-queue-contexts-render.html
* igt@gem_sync@basic-all:
- {shard-tglb}: [INCOMPLETE][54] ([fdo#111647]) -> [PASS][55]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-tglb6/igt@gem_sync@basic-all.html
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-tglb4/igt@gem_sync@basic-all.html
* igt@gem_userptr_blits@map-fixed-invalidate-busy:
- shard-hsw: [DMESG-WARN][56] ([fdo#111870]) -> [PASS][57]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-hsw4/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-hsw7/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
* {igt@i915_pm_dc@dc6-psr}:
- shard-iclb: [FAIL][58] ([fdo#110548]) -> [PASS][59]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb6/igt@i915_pm_dc@dc6-psr.html
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb5/igt@i915_pm_dc@dc6-psr.html
* igt@kms_color@pipe-a-ctm-0-25:
- shard-skl: [DMESG-WARN][60] ([fdo#106107]) -> [PASS][61]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-skl8/igt@kms_color@pipe-a-ctm-0-25.html
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-skl10/igt@kms_color@pipe-a-ctm-0-25.html
* igt@kms_cursor_crc@pipe-c-cursor-suspend:
- shard-kbl: [DMESG-WARN][62] ([fdo#108566]) -> [PASS][63] +4 similar issues
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-kbl6/igt@kms_cursor_crc@pipe-c-cursor-suspend.html
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-kbl6/igt@kms_cursor_crc@pipe-c-cursor-suspend.html
* igt@kms_flip@flip-vs-expired-vblank:
- shard-skl: [FAIL][64] ([fdo#105363]) -> [PASS][65]
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-skl7/igt@kms_flip@flip-vs-expired-vblank.html
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-skl6/igt@kms_flip@flip-vs-expired-vblank.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible:
- {shard-tglb}: [INCOMPLETE][66] ([fdo#112031]) -> [PASS][67]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-tglb8/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-tglb4/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
* igt@kms_flip@flip-vs-suspend:
- shard-apl: [DMESG-WARN][68] ([fdo#108566]) -> [PASS][69]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-apl2/igt@kms_flip@flip-vs-suspend.html
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-apl2/igt@kms_flip@flip-vs-suspend.html
* igt@kms_flip@flip-vs-suspend-interruptible:
- shard-snb: [INCOMPLETE][70] ([fdo#105411]) -> [PASS][71]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-snb1/igt@kms_flip@flip-vs-suspend-interruptible.html
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-snb1/igt@kms_flip@flip-vs-suspend-interruptible.html
* igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-pwrite:
- {shard-tglb}: [FAIL][72] ([fdo#103167]) -> [PASS][73] +1 similar issue
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-tglb5/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-pwrite.html
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-tglb1/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-pwrite.html
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-pwrite:
- shard-iclb: [FAIL][74] ([fdo#103167]) -> [PASS][75] +5 similar issues
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb2/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-pwrite.html
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb4/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-pwrite.html
* igt@kms_frontbuffer_tracking@psr-1p-offscren-pri-indfb-draw-blt:
- {shard-tglb}: [INCOMPLETE][76] ([fdo#111747]) -> [PASS][77]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-tglb8/igt@kms_frontbuffer_tracking@psr-1p-offscren-pri-indfb-draw-blt.html
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-tglb8/igt@kms_frontbuffer_tracking@psr-1p-offscren-pri-indfb-draw-blt.html
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-mmap-gtt:
- {shard-tglb}: [INCOMPLETE][78] -> [PASS][79]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-tglb2/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-mmap-gtt.html
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-tglb6/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-mmap-gtt.html
* igt@kms_psr@psr2_primary_mmap_cpu:
- shard-iclb: [SKIP][80] ([fdo#109441]) -> [PASS][81] +3 similar issues
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb5/igt@kms_psr@psr2_primary_mmap_cpu.html
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb2/igt@kms_psr@psr2_primary_mmap_cpu.html
* igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend:
- {shard-tglb}: [INCOMPLETE][82] ([fdo#111850]) -> [PASS][83]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-tglb2/igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend.html
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-tglb2/igt@kms_vblank@pipe-c-ts-continuation-dpms-suspend.html
* igt@prime_busy@hang-bsd2:
- shard-iclb: [SKIP][84] ([fdo#109276]) -> [PASS][85] +15 similar issues
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb6/igt@prime_busy@hang-bsd2.html
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb2/igt@prime_busy@hang-bsd2.html
* igt@prime_vgem@basic-sync-default:
- {shard-tglb}: [INCOMPLETE][86] ([fdo#111930]) -> [PASS][87]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-tglb4/igt@prime_vgem@basic-sync-default.html
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-tglb3/igt@prime_vgem@basic-sync-default.html
#### Warnings ####
* igt@gem_mocs_settings@mocs-isolation-bsd2:
- shard-iclb: [SKIP][88] ([fdo#109276]) -> [FAIL][89] ([fdo#111330])
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb5/igt@gem_mocs_settings@mocs-isolation-bsd2.html
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb2/igt@gem_mocs_settings@mocs-isolation-bsd2.html
* igt@gem_mocs_settings@mocs-reset-bsd2:
- shard-iclb: [FAIL][90] ([fdo#111330]) -> [SKIP][91] ([fdo#109276])
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7234/shard-iclb4/igt@gem_mocs_settings@mocs-reset-bsd2.html
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/shard-iclb6/igt@gem_mocs_settings@mocs-reset-bsd2.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
[fdo#103183]: https://bugs.freedesktop.org/show_bug.cgi?id=103183
[fdo#103232]: https://bugs.freedesktop.org/show_bug.cgi?id=103232
[fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927
[fdo#105363]: https://bugs.freedesktop.org/show_bug.cgi?id=105363
[fdo#105411]: https://bugs.freedesktop.org/show_bug.cgi?id=105411
[fdo#105763]: https://bugs.freedesktop.org/show_bug.cgi?id=105763
[fdo#106107]: https://bugs.freedesktop.org/show_bug.cgi?id=106107
[fdo#106538]: https://bugs.freedesktop.org/show_bug.cgi?id=106538
[fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#108341]: https://bugs.freedesktop.org/show_bug.cgi?id=108341
[fdo#108566]: https://bugs.freedesktop.org/show_bug.cgi?id=108566
[fdo#108838]: https://bugs.freedesktop.org/show_bug.cgi?id=108838
[fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109507]: https://bugs.freedesktop.org/show_bug.cgi?id=109507
[fdo#110548]: https://bugs.freedesktop.org/show_bug.cgi?id=110548
[fdo#110854]: https://bugs.freedesktop.org/show_bug.cgi?id=110854
[fdo#111330]: https://bugs.freedesktop.org/show_bug.cgi?id=111330
[fdo#111606]: https://bugs.freedesktop.org/show_bug.cgi?id=111606
[fdo#111647]: https://bugs.freedesktop.org/show_bug.cgi?id=111647
[fdo#111677]: https://bugs.freedesktop.org/show_bug.cgi?id=111677
[fdo#111703]: https://bugs.freedesktop.org/show_bug.cgi?id=111703
[fdo#111747]: https://bugs.freedesktop.org/show_bug.cgi?id=111747
[fdo#111831]: https://bugs.freedesktop.org/show_bug.cgi?id=111831
[fdo#111832]: https://bugs.freedesktop.org/show_bug.cgi?id=111832
[fdo#111850]: https://bugs.freedesktop.org/show_bug.cgi?id=111850
[fdo#111870]: https://bugs.freedesktop.org/show_bug.cgi?id=111870
[fdo#111930]: https://bugs.freedesktop.org/show_bug.cgi?id=111930
[fdo#112031]: https://bugs.freedesktop.org/show_bug.cgi?id=112031
[fdo#112080]: https://bugs.freedesktop.org/show_bug.cgi?id=112080
[fdo#112146]: https://bugs.freedesktop.org/show_bug.cgi?id=112146
[fdo#112191]: https://bugs.freedesktop.org/show_bug.cgi?id=112191
Participating hosts (11 -> 11)
------------------------------
No changes in participating ho
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15095/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-11-04 9:18 ` Daniel Vetter
0 siblings, 0 replies; 30+ messages in thread
From: Daniel Vetter @ 2019-11-04 9:18 UTC (permalink / raw)
To: Manasi Navare; +Cc: Dave Airlie, intel-gfx, dri-devel
On Thu, Oct 31, 2019 at 02:48:39PM -0700, Manasi Navare wrote:
> In case of tiled displays, if we hotplug just one connector,
> fbcon currently just selects the preferred mode and if it is
> tiled mode then that becomes a problem if rest of the tiles are
> not present.
> So in the fbdev driver on hotplug when we probe the client modeset,
> we we dont find all the connectors for all tiles, then on a connector
> with one tile, just fallback to the first available non tiled mode
> to display over a single connector.
>
> Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Suggested-by: Dave Airlie <airlied@redhat.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Dave Airlie <airlied@redhat.com>
> Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
Hm, should we mayb have a slight timeout first to wait for the 2nd
connector? Otherwise lots of flickering going on when plugging in one of
these screens ...
-Daniel
> ---
> drivers/gpu/drm/drm_client_modeset.c | 29 ++++++++++++++++++++++++++++
> 1 file changed, 29 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_client_modeset.c b/drivers/gpu/drm/drm_client_modeset.c
> index 895b73f23079..e28a723587db 100644
> --- a/drivers/gpu/drm/drm_client_modeset.c
> +++ b/drivers/gpu/drm/drm_client_modeset.c
> @@ -114,6 +114,20 @@ drm_client_find_modeset(struct drm_client_dev *client, struct drm_crtc *crtc)
> return NULL;
> }
>
> +static struct drm_display_mode *
> +drm_connector_fallback_non_tiled_mode(struct drm_connector *connector)
> +{
> + struct drm_display_mode *mode;
> +
> + list_for_each_entry(mode, &connector->modes, head) {
> + if (mode->hdisplay == connector->tile_h_size &&
> + mode->vdisplay == connector->tile_v_size)
> + continue;
> + return mode;
> + }
> + return NULL;
> +}
> +
> static struct drm_display_mode *
> drm_connector_has_preferred_mode(struct drm_connector *connector, int width, int height)
> {
> @@ -348,8 +362,17 @@ static bool drm_client_target_preferred(struct drm_connector **connectors,
> struct drm_connector *connector;
> u64 conn_configured = 0;
> int tile_pass = 0;
> + int num_tiled_conns = 0;
> int i;
>
> + for (i = 0; i < connector_count; i++) {
> + connector = connectors[i];
> + if (!connector->has_tile)
> + continue;
> +
> + num_tiled_conns ++;
> + }
> +
> retry:
> for (i = 0; i < connector_count; i++) {
> connector = connectors[i];
> @@ -394,6 +417,12 @@ static bool drm_client_target_preferred(struct drm_connector **connectors,
> connector->base.id, connector->tile_group ? connector->tile_group->id : 0);
> modes[i] = drm_connector_has_preferred_mode(connector, width, height);
> }
> + if (connector->has_tile &&
> + num_tiled_conns < connector->num_h_tile * connector->num_v_tile) {
> + DRM_DEBUG_KMS("Falling back to non tiled mode on Connector %d\n",
> + connector->base.id);
> + modes[i] = drm_connector_fallback_non_tiled_mode(connector);
> + }
> /* No preferred modes, pick one off the list */
> if (!modes[i] && !list_empty(&connector->modes)) {
> list_for_each_entry(modes[i], &connector->modes, head)
> --
> 2.19.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-11-04 9:18 ` Daniel Vetter
0 siblings, 0 replies; 30+ messages in thread
From: Daniel Vetter @ 2019-11-04 9:18 UTC (permalink / raw)
To: Manasi Navare; +Cc: Dave Airlie, intel-gfx, dri-devel
On Thu, Oct 31, 2019 at 02:48:39PM -0700, Manasi Navare wrote:
> In case of tiled displays, if we hotplug just one connector,
> fbcon currently just selects the preferred mode and if it is
> tiled mode then that becomes a problem if rest of the tiles are
> not present.
> So in the fbdev driver on hotplug when we probe the client modeset,
> we we dont find all the connectors for all tiles, then on a connector
> with one tile, just fallback to the first available non tiled mode
> to display over a single connector.
>
> Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Suggested-by: Dave Airlie <airlied@redhat.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Dave Airlie <airlied@redhat.com>
> Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
Hm, should we mayb have a slight timeout first to wait for the 2nd
connector? Otherwise lots of flickering going on when plugging in one of
these screens ...
-Daniel
> ---
> drivers/gpu/drm/drm_client_modeset.c | 29 ++++++++++++++++++++++++++++
> 1 file changed, 29 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_client_modeset.c b/drivers/gpu/drm/drm_client_modeset.c
> index 895b73f23079..e28a723587db 100644
> --- a/drivers/gpu/drm/drm_client_modeset.c
> +++ b/drivers/gpu/drm/drm_client_modeset.c
> @@ -114,6 +114,20 @@ drm_client_find_modeset(struct drm_client_dev *client, struct drm_crtc *crtc)
> return NULL;
> }
>
> +static struct drm_display_mode *
> +drm_connector_fallback_non_tiled_mode(struct drm_connector *connector)
> +{
> + struct drm_display_mode *mode;
> +
> + list_for_each_entry(mode, &connector->modes, head) {
> + if (mode->hdisplay == connector->tile_h_size &&
> + mode->vdisplay == connector->tile_v_size)
> + continue;
> + return mode;
> + }
> + return NULL;
> +}
> +
> static struct drm_display_mode *
> drm_connector_has_preferred_mode(struct drm_connector *connector, int width, int height)
> {
> @@ -348,8 +362,17 @@ static bool drm_client_target_preferred(struct drm_connector **connectors,
> struct drm_connector *connector;
> u64 conn_configured = 0;
> int tile_pass = 0;
> + int num_tiled_conns = 0;
> int i;
>
> + for (i = 0; i < connector_count; i++) {
> + connector = connectors[i];
> + if (!connector->has_tile)
> + continue;
> +
> + num_tiled_conns ++;
> + }
> +
> retry:
> for (i = 0; i < connector_count; i++) {
> connector = connectors[i];
> @@ -394,6 +417,12 @@ static bool drm_client_target_preferred(struct drm_connector **connectors,
> connector->base.id, connector->tile_group ? connector->tile_group->id : 0);
> modes[i] = drm_connector_has_preferred_mode(connector, width, height);
> }
> + if (connector->has_tile &&
> + num_tiled_conns < connector->num_h_tile * connector->num_v_tile) {
> + DRM_DEBUG_KMS("Falling back to non tiled mode on Connector %d\n",
> + connector->base.id);
> + modes[i] = drm_connector_fallback_non_tiled_mode(connector);
> + }
> /* No preferred modes, pick one off the list */
> if (!modes[i] && !list_empty(&connector->modes)) {
> list_for_each_entry(modes[i], &connector->modes, head)
> --
> 2.19.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [PATCH] drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-11-04 18:14 ` Daniel Vetter
0 siblings, 0 replies; 30+ messages in thread
From: Daniel Vetter @ 2019-11-04 18:14 UTC (permalink / raw)
To: David Airlie; +Cc: Development, Intel, dri-devel
On Mon, Nov 04, 2019 at 07:48:26PM +1000, David Airlie wrote:
> On Mon, Nov 4, 2019 at 7:18 PM Daniel Vetter <daniel@ffwll.ch> wrote:
> >
> > On Thu, Oct 31, 2019 at 02:48:39PM -0700, Manasi Navare wrote:
> > > In case of tiled displays, if we hotplug just one connector,
> > > fbcon currently just selects the preferred mode and if it is
> > > tiled mode then that becomes a problem if rest of the tiles are
> > > not present.
> > > So in the fbdev driver on hotplug when we probe the client modeset,
> > > we we dont find all the connectors for all tiles, then on a connector
> > > with one tile, just fallback to the first available non tiled mode
> > > to display over a single connector.
> > >
> > > Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > Suggested-by: Dave Airlie <airlied@redhat.com>
> > > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > Cc: Dave Airlie <airlied@redhat.com>
> > > Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
> >
> > Hm, should we mayb have a slight timeout first to wait for the 2nd
> > connector? Otherwise lots of flickering going on when plugging in one of
> > these screens ...
>
> Not really,
>
> There are 3 scenarios with the multi-cable tiled monitors. and
> non-resizeable fbdev.
>
> a) it's plugged in at boot. both cables are detected, fbdev gets a
> full tiled mode.
> b) it's not plugged in at boot, the user starts plugging it in, fbdev
> was inited via the panel or another monitor. fbdev won't resize.
> c) it's half plugged in at boot, then you get a non-tiled mode, and
> fbdev can't resize to tiled anyways.
>
> Also plugging in one of these multi-cable monitors piecemeal is going
> to take multiple seconds for the user to do physical cable plugging.
Uh.
I guess fbdev ftl, oh well.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-11-04 18:14 ` Daniel Vetter
0 siblings, 0 replies; 30+ messages in thread
From: Daniel Vetter @ 2019-11-04 18:14 UTC (permalink / raw)
To: David Airlie; +Cc: Manasi Navare, Development, Intel, dri-devel
On Mon, Nov 04, 2019 at 07:48:26PM +1000, David Airlie wrote:
> On Mon, Nov 4, 2019 at 7:18 PM Daniel Vetter <daniel@ffwll.ch> wrote:
> >
> > On Thu, Oct 31, 2019 at 02:48:39PM -0700, Manasi Navare wrote:
> > > In case of tiled displays, if we hotplug just one connector,
> > > fbcon currently just selects the preferred mode and if it is
> > > tiled mode then that becomes a problem if rest of the tiles are
> > > not present.
> > > So in the fbdev driver on hotplug when we probe the client modeset,
> > > we we dont find all the connectors for all tiles, then on a connector
> > > with one tile, just fallback to the first available non tiled mode
> > > to display over a single connector.
> > >
> > > Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > Suggested-by: Dave Airlie <airlied@redhat.com>
> > > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > Cc: Dave Airlie <airlied@redhat.com>
> > > Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
> >
> > Hm, should we mayb have a slight timeout first to wait for the 2nd
> > connector? Otherwise lots of flickering going on when plugging in one of
> > these screens ...
>
> Not really,
>
> There are 3 scenarios with the multi-cable tiled monitors. and
> non-resizeable fbdev.
>
> a) it's plugged in at boot. both cables are detected, fbdev gets a
> full tiled mode.
> b) it's not plugged in at boot, the user starts plugging it in, fbdev
> was inited via the panel or another monitor. fbdev won't resize.
> c) it's half plugged in at boot, then you get a non-tiled mode, and
> fbdev can't resize to tiled anyways.
>
> Also plugging in one of these multi-cable monitors piecemeal is going
> to take multiple seconds for the user to do physical cable plugging.
Uh.
I guess fbdev ftl, oh well.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-11-04 18:14 ` Daniel Vetter
0 siblings, 0 replies; 30+ messages in thread
From: Daniel Vetter @ 2019-11-04 18:14 UTC (permalink / raw)
To: David Airlie; +Cc: Development, Intel, dri-devel
On Mon, Nov 04, 2019 at 07:48:26PM +1000, David Airlie wrote:
> On Mon, Nov 4, 2019 at 7:18 PM Daniel Vetter <daniel@ffwll.ch> wrote:
> >
> > On Thu, Oct 31, 2019 at 02:48:39PM -0700, Manasi Navare wrote:
> > > In case of tiled displays, if we hotplug just one connector,
> > > fbcon currently just selects the preferred mode and if it is
> > > tiled mode then that becomes a problem if rest of the tiles are
> > > not present.
> > > So in the fbdev driver on hotplug when we probe the client modeset,
> > > we we dont find all the connectors for all tiles, then on a connector
> > > with one tile, just fallback to the first available non tiled mode
> > > to display over a single connector.
> > >
> > > Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > Suggested-by: Dave Airlie <airlied@redhat.com>
> > > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > Cc: Dave Airlie <airlied@redhat.com>
> > > Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
> >
> > Hm, should we mayb have a slight timeout first to wait for the 2nd
> > connector? Otherwise lots of flickering going on when plugging in one of
> > these screens ...
>
> Not really,
>
> There are 3 scenarios with the multi-cable tiled monitors. and
> non-resizeable fbdev.
>
> a) it's plugged in at boot. both cables are detected, fbdev gets a
> full tiled mode.
> b) it's not plugged in at boot, the user starts plugging it in, fbdev
> was inited via the panel or another monitor. fbdev won't resize.
> c) it's half plugged in at boot, then you get a non-tiled mode, and
> fbdev can't resize to tiled anyways.
>
> Also plugging in one of these multi-cable monitors piecemeal is going
> to take multiple seconds for the user to do physical cable plugging.
Uh.
I guess fbdev ftl, oh well.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [PATCH] drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-11-04 21:03 ` Manasi Navare
0 siblings, 0 replies; 30+ messages in thread
From: Manasi Navare @ 2019-11-04 21:03 UTC (permalink / raw)
To: David Airlie; +Cc: Development, Intel, dri-devel
On Mon, Nov 04, 2019 at 07:48:26PM +1000, David Airlie wrote:
> On Mon, Nov 4, 2019 at 7:18 PM Daniel Vetter <daniel@ffwll.ch> wrote:
> >
> > On Thu, Oct 31, 2019 at 02:48:39PM -0700, Manasi Navare wrote:
> > > In case of tiled displays, if we hotplug just one connector,
> > > fbcon currently just selects the preferred mode and if it is
> > > tiled mode then that becomes a problem if rest of the tiles are
> > > not present.
> > > So in the fbdev driver on hotplug when we probe the client modeset,
> > > we we dont find all the connectors for all tiles, then on a connector
> > > with one tile, just fallback to the first available non tiled mode
> > > to display over a single connector.
> > >
> > > Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > Suggested-by: Dave Airlie <airlied@redhat.com>
> > > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > Cc: Dave Airlie <airlied@redhat.com>
> > > Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
> >
> > Hm, should we mayb have a slight timeout first to wait for the 2nd
> > connector? Otherwise lots of flickering going on when plugging in one of
> > these screens ...
>
> Not really,
>
> There are 3 scenarios with the multi-cable tiled monitors. and
> non-resizeable fbdev.
>
> a) it's plugged in at boot. both cables are detected, fbdev gets a
> full tiled mode.
Yes this works as expected
> b) it's not plugged in at boot, the user starts plugging it in, fbdev
> was inited via the panel or another monitor. fbdev won't resize.
> c) it's half plugged in at boot, then you get a non-tiled mode, and
> fbdev can't resize to tiled anyways.
In b and c, when its booted with only 1 cable connected and/or hotplugged only
one cable after boot, I fallback to fisrt available non tiled mode, does that sound good?
>
> Also plugging in one of these multi-cable monitors piecemeal is going
> to take multiple seconds for the user to do physical cable plugging.
So still good with ignoring the second hotplug completely?
However i donno where in the fb helper to stop passing the modeset down
after the drm_fb_helper_hotplug_event()
Any suggestions?
Regards
Manasi
>
> Dave.
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-11-04 21:03 ` Manasi Navare
0 siblings, 0 replies; 30+ messages in thread
From: Manasi Navare @ 2019-11-04 21:03 UTC (permalink / raw)
To: David Airlie; +Cc: Development, Intel, dri-devel
On Mon, Nov 04, 2019 at 07:48:26PM +1000, David Airlie wrote:
> On Mon, Nov 4, 2019 at 7:18 PM Daniel Vetter <daniel@ffwll.ch> wrote:
> >
> > On Thu, Oct 31, 2019 at 02:48:39PM -0700, Manasi Navare wrote:
> > > In case of tiled displays, if we hotplug just one connector,
> > > fbcon currently just selects the preferred mode and if it is
> > > tiled mode then that becomes a problem if rest of the tiles are
> > > not present.
> > > So in the fbdev driver on hotplug when we probe the client modeset,
> > > we we dont find all the connectors for all tiles, then on a connector
> > > with one tile, just fallback to the first available non tiled mode
> > > to display over a single connector.
> > >
> > > Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > Suggested-by: Dave Airlie <airlied@redhat.com>
> > > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > Cc: Dave Airlie <airlied@redhat.com>
> > > Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
> >
> > Hm, should we mayb have a slight timeout first to wait for the 2nd
> > connector? Otherwise lots of flickering going on when plugging in one of
> > these screens ...
>
> Not really,
>
> There are 3 scenarios with the multi-cable tiled monitors. and
> non-resizeable fbdev.
>
> a) it's plugged in at boot. both cables are detected, fbdev gets a
> full tiled mode.
Yes this works as expected
> b) it's not plugged in at boot, the user starts plugging it in, fbdev
> was inited via the panel or another monitor. fbdev won't resize.
> c) it's half plugged in at boot, then you get a non-tiled mode, and
> fbdev can't resize to tiled anyways.
In b and c, when its booted with only 1 cable connected and/or hotplugged only
one cable after boot, I fallback to fisrt available non tiled mode, does that sound good?
>
> Also plugging in one of these multi-cable monitors piecemeal is going
> to take multiple seconds for the user to do physical cable plugging.
So still good with ignoring the second hotplug completely?
However i donno where in the fb helper to stop passing the modeset down
after the drm_fb_helper_hotplug_event()
Any suggestions?
Regards
Manasi
>
> Dave.
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-11-04 21:03 ` Manasi Navare
0 siblings, 0 replies; 30+ messages in thread
From: Manasi Navare @ 2019-11-04 21:03 UTC (permalink / raw)
To: David Airlie; +Cc: Development, Intel, dri-devel
On Mon, Nov 04, 2019 at 07:48:26PM +1000, David Airlie wrote:
> On Mon, Nov 4, 2019 at 7:18 PM Daniel Vetter <daniel@ffwll.ch> wrote:
> >
> > On Thu, Oct 31, 2019 at 02:48:39PM -0700, Manasi Navare wrote:
> > > In case of tiled displays, if we hotplug just one connector,
> > > fbcon currently just selects the preferred mode and if it is
> > > tiled mode then that becomes a problem if rest of the tiles are
> > > not present.
> > > So in the fbdev driver on hotplug when we probe the client modeset,
> > > we we dont find all the connectors for all tiles, then on a connector
> > > with one tile, just fallback to the first available non tiled mode
> > > to display over a single connector.
> > >
> > > Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > Suggested-by: Dave Airlie <airlied@redhat.com>
> > > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > Cc: Dave Airlie <airlied@redhat.com>
> > > Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
> >
> > Hm, should we mayb have a slight timeout first to wait for the 2nd
> > connector? Otherwise lots of flickering going on when plugging in one of
> > these screens ...
>
> Not really,
>
> There are 3 scenarios with the multi-cable tiled monitors. and
> non-resizeable fbdev.
>
> a) it's plugged in at boot. both cables are detected, fbdev gets a
> full tiled mode.
Yes this works as expected
> b) it's not plugged in at boot, the user starts plugging it in, fbdev
> was inited via the panel or another monitor. fbdev won't resize.
> c) it's half plugged in at boot, then you get a non-tiled mode, and
> fbdev can't resize to tiled anyways.
In b and c, when its booted with only 1 cable connected and/or hotplugged only
one cable after boot, I fallback to fisrt available non tiled mode, does that sound good?
>
> Also plugging in one of these multi-cable monitors piecemeal is going
> to take multiple seconds for the user to do physical cable plugging.
So still good with ignoring the second hotplug completely?
However i donno where in the fb helper to stop passing the modeset down
after the drm_fb_helper_hotplug_event()
Any suggestions?
Regards
Manasi
>
> Dave.
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [PATCH] drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-11-06 2:47 ` Dave Airlie
0 siblings, 0 replies; 30+ messages in thread
From: Dave Airlie @ 2019-11-06 2:47 UTC (permalink / raw)
To: Manasi Navare; +Cc: Dave Airlie, Intel Graphics Development, dri-devel
On Fri, 1 Nov 2019 at 07:46, Manasi Navare <manasi.d.navare@intel.com> wrote:
>
> In case of tiled displays, if we hotplug just one connector,
> fbcon currently just selects the preferred mode and if it is
> tiled mode then that becomes a problem if rest of the tiles are
> not present.
> So in the fbdev driver on hotplug when we probe the client modeset,
> we we dont find all the connectors for all tiles, then on a connector
> with one tile, just fallback to the first available non tiled mode
> to display over a single connector.
>
> Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Suggested-by: Dave Airlie <airlied@redhat.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Dave Airlie <airlied@redhat.com>
> Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
> ---
> drivers/gpu/drm/drm_client_modeset.c | 29 ++++++++++++++++++++++++++++
> 1 file changed, 29 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_client_modeset.c b/drivers/gpu/drm/drm_client_modeset.c
> index 895b73f23079..e28a723587db 100644
> --- a/drivers/gpu/drm/drm_client_modeset.c
> +++ b/drivers/gpu/drm/drm_client_modeset.c
> @@ -114,6 +114,20 @@ drm_client_find_modeset(struct drm_client_dev *client, struct drm_crtc *crtc)
> return NULL;
> }
>
> +static struct drm_display_mode *
> +drm_connector_fallback_non_tiled_mode(struct drm_connector *connector)
> +{
> + struct drm_display_mode *mode;
> +
> + list_for_each_entry(mode, &connector->modes, head) {
> + if (mode->hdisplay == connector->tile_h_size &&
> + mode->vdisplay == connector->tile_v_size)
> + continue;
> + return mode;
> + }
> + return NULL;
> +}
> +
> static struct drm_display_mode *
> drm_connector_has_preferred_mode(struct drm_connector *connector, int width, int height)
> {
> @@ -348,8 +362,17 @@ static bool drm_client_target_preferred(struct drm_connector **connectors,
> struct drm_connector *connector;
> u64 conn_configured = 0;
> int tile_pass = 0;
> + int num_tiled_conns = 0;
> int i;
>
> + for (i = 0; i < connector_count; i++) {
> + connector = connectors[i];
> + if (!connector->has_tile)
> + continue;
> +
> + num_tiled_conns ++;
Drop the space before the ++ here. Maybe just make this
if (connectors[i]->has_tile)
num_tiled_conns++;
Reviewed-by: Dave Airlie <airlied@redhat.com>
Otherwise I think this seems fine, though it does beg the question in
my mind of what happens if I get 2 8K monitors, and plug the first
tile of one in, and the second tile of the other in.
Dave.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-11-06 2:47 ` Dave Airlie
0 siblings, 0 replies; 30+ messages in thread
From: Dave Airlie @ 2019-11-06 2:47 UTC (permalink / raw)
To: Manasi Navare; +Cc: Dave Airlie, Intel Graphics Development, dri-devel
On Fri, 1 Nov 2019 at 07:46, Manasi Navare <manasi.d.navare@intel.com> wrote:
>
> In case of tiled displays, if we hotplug just one connector,
> fbcon currently just selects the preferred mode and if it is
> tiled mode then that becomes a problem if rest of the tiles are
> not present.
> So in the fbdev driver on hotplug when we probe the client modeset,
> we we dont find all the connectors for all tiles, then on a connector
> with one tile, just fallback to the first available non tiled mode
> to display over a single connector.
>
> Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Suggested-by: Dave Airlie <airlied@redhat.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Dave Airlie <airlied@redhat.com>
> Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
> ---
> drivers/gpu/drm/drm_client_modeset.c | 29 ++++++++++++++++++++++++++++
> 1 file changed, 29 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_client_modeset.c b/drivers/gpu/drm/drm_client_modeset.c
> index 895b73f23079..e28a723587db 100644
> --- a/drivers/gpu/drm/drm_client_modeset.c
> +++ b/drivers/gpu/drm/drm_client_modeset.c
> @@ -114,6 +114,20 @@ drm_client_find_modeset(struct drm_client_dev *client, struct drm_crtc *crtc)
> return NULL;
> }
>
> +static struct drm_display_mode *
> +drm_connector_fallback_non_tiled_mode(struct drm_connector *connector)
> +{
> + struct drm_display_mode *mode;
> +
> + list_for_each_entry(mode, &connector->modes, head) {
> + if (mode->hdisplay == connector->tile_h_size &&
> + mode->vdisplay == connector->tile_v_size)
> + continue;
> + return mode;
> + }
> + return NULL;
> +}
> +
> static struct drm_display_mode *
> drm_connector_has_preferred_mode(struct drm_connector *connector, int width, int height)
> {
> @@ -348,8 +362,17 @@ static bool drm_client_target_preferred(struct drm_connector **connectors,
> struct drm_connector *connector;
> u64 conn_configured = 0;
> int tile_pass = 0;
> + int num_tiled_conns = 0;
> int i;
>
> + for (i = 0; i < connector_count; i++) {
> + connector = connectors[i];
> + if (!connector->has_tile)
> + continue;
> +
> + num_tiled_conns ++;
Drop the space before the ++ here. Maybe just make this
if (connectors[i]->has_tile)
num_tiled_conns++;
Reviewed-by: Dave Airlie <airlied@redhat.com>
Otherwise I think this seems fine, though it does beg the question in
my mind of what happens if I get 2 8K monitors, and plug the first
tile of one in, and the second tile of the other in.
Dave.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-11-06 2:47 ` Dave Airlie
0 siblings, 0 replies; 30+ messages in thread
From: Dave Airlie @ 2019-11-06 2:47 UTC (permalink / raw)
To: Manasi Navare; +Cc: Dave Airlie, Intel Graphics Development, dri-devel
On Fri, 1 Nov 2019 at 07:46, Manasi Navare <manasi.d.navare@intel.com> wrote:
>
> In case of tiled displays, if we hotplug just one connector,
> fbcon currently just selects the preferred mode and if it is
> tiled mode then that becomes a problem if rest of the tiles are
> not present.
> So in the fbdev driver on hotplug when we probe the client modeset,
> we we dont find all the connectors for all tiles, then on a connector
> with one tile, just fallback to the first available non tiled mode
> to display over a single connector.
>
> Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Suggested-by: Dave Airlie <airlied@redhat.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Dave Airlie <airlied@redhat.com>
> Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
> ---
> drivers/gpu/drm/drm_client_modeset.c | 29 ++++++++++++++++++++++++++++
> 1 file changed, 29 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_client_modeset.c b/drivers/gpu/drm/drm_client_modeset.c
> index 895b73f23079..e28a723587db 100644
> --- a/drivers/gpu/drm/drm_client_modeset.c
> +++ b/drivers/gpu/drm/drm_client_modeset.c
> @@ -114,6 +114,20 @@ drm_client_find_modeset(struct drm_client_dev *client, struct drm_crtc *crtc)
> return NULL;
> }
>
> +static struct drm_display_mode *
> +drm_connector_fallback_non_tiled_mode(struct drm_connector *connector)
> +{
> + struct drm_display_mode *mode;
> +
> + list_for_each_entry(mode, &connector->modes, head) {
> + if (mode->hdisplay == connector->tile_h_size &&
> + mode->vdisplay == connector->tile_v_size)
> + continue;
> + return mode;
> + }
> + return NULL;
> +}
> +
> static struct drm_display_mode *
> drm_connector_has_preferred_mode(struct drm_connector *connector, int width, int height)
> {
> @@ -348,8 +362,17 @@ static bool drm_client_target_preferred(struct drm_connector **connectors,
> struct drm_connector *connector;
> u64 conn_configured = 0;
> int tile_pass = 0;
> + int num_tiled_conns = 0;
> int i;
>
> + for (i = 0; i < connector_count; i++) {
> + connector = connectors[i];
> + if (!connector->has_tile)
> + continue;
> +
> + num_tiled_conns ++;
Drop the space before the ++ here. Maybe just make this
if (connectors[i]->has_tile)
num_tiled_conns++;
Reviewed-by: Dave Airlie <airlied@redhat.com>
Otherwise I think this seems fine, though it does beg the question in
my mind of what happens if I get 2 8K monitors, and plug the first
tile of one in, and the second tile of the other in.
Dave.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-11-06 2:50 ` Dave Airlie
0 siblings, 0 replies; 30+ messages in thread
From: Dave Airlie @ 2019-11-06 2:50 UTC (permalink / raw)
To: Manasi Navare; +Cc: David Airlie, Development, Intel, dri-devel
On Tue, 5 Nov 2019 at 07:00, Manasi Navare <manasi.d.navare@intel.com> wrote:
>
> On Mon, Nov 04, 2019 at 07:48:26PM +1000, David Airlie wrote:
> > On Mon, Nov 4, 2019 at 7:18 PM Daniel Vetter <daniel@ffwll.ch> wrote:
> > >
> > > On Thu, Oct 31, 2019 at 02:48:39PM -0700, Manasi Navare wrote:
> > > > In case of tiled displays, if we hotplug just one connector,
> > > > fbcon currently just selects the preferred mode and if it is
> > > > tiled mode then that becomes a problem if rest of the tiles are
> > > > not present.
> > > > So in the fbdev driver on hotplug when we probe the client modeset,
> > > > we we dont find all the connectors for all tiles, then on a connector
> > > > with one tile, just fallback to the first available non tiled mode
> > > > to display over a single connector.
> > > >
> > > > Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > > Suggested-by: Dave Airlie <airlied@redhat.com>
> > > > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > > Cc: Dave Airlie <airlied@redhat.com>
> > > > Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
> > >
> > > Hm, should we mayb have a slight timeout first to wait for the 2nd
> > > connector? Otherwise lots of flickering going on when plugging in one of
> > > these screens ...
> >
> > Not really,
> >
> > There are 3 scenarios with the multi-cable tiled monitors. and
> > non-resizeable fbdev.
> >
> > a) it's plugged in at boot. both cables are detected, fbdev gets a
> > full tiled mode.
>
> Yes this works as expected
>
> > b) it's not plugged in at boot, the user starts plugging it in, fbdev
> > was inited via the panel or another monitor. fbdev won't resize.
> > c) it's half plugged in at boot, then you get a non-tiled mode, and
> > fbdev can't resize to tiled anyways.
>
> In b and c, when its booted with only 1 cable connected and/or hotplugged only
> one cable after boot, I fallback to fisrt available non tiled mode, does that sound good?
>
> >
> > Also plugging in one of these multi-cable monitors piecemeal is going
> > to take multiple seconds for the user to do physical cable plugging.
>
> So still good with ignoring the second hotplug completely?
> However i donno where in the fb helper to stop passing the modeset down
> after the drm_fb_helper_hotplug_event()
I don't think you can ignore it completely. I think you just have to
make the mode picking logic pick the right answer somehow.
So you can tell if width/height are going to be lower than the tiled
mode size, and in that case just don't enable the secondary tile.
Dave.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-11-06 2:50 ` Dave Airlie
0 siblings, 0 replies; 30+ messages in thread
From: Dave Airlie @ 2019-11-06 2:50 UTC (permalink / raw)
To: Manasi Navare; +Cc: David Airlie, Development, Intel, dri-devel
On Tue, 5 Nov 2019 at 07:00, Manasi Navare <manasi.d.navare@intel.com> wrote:
>
> On Mon, Nov 04, 2019 at 07:48:26PM +1000, David Airlie wrote:
> > On Mon, Nov 4, 2019 at 7:18 PM Daniel Vetter <daniel@ffwll.ch> wrote:
> > >
> > > On Thu, Oct 31, 2019 at 02:48:39PM -0700, Manasi Navare wrote:
> > > > In case of tiled displays, if we hotplug just one connector,
> > > > fbcon currently just selects the preferred mode and if it is
> > > > tiled mode then that becomes a problem if rest of the tiles are
> > > > not present.
> > > > So in the fbdev driver on hotplug when we probe the client modeset,
> > > > we we dont find all the connectors for all tiles, then on a connector
> > > > with one tile, just fallback to the first available non tiled mode
> > > > to display over a single connector.
> > > >
> > > > Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > > Suggested-by: Dave Airlie <airlied@redhat.com>
> > > > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > > Cc: Dave Airlie <airlied@redhat.com>
> > > > Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
> > >
> > > Hm, should we mayb have a slight timeout first to wait for the 2nd
> > > connector? Otherwise lots of flickering going on when plugging in one of
> > > these screens ...
> >
> > Not really,
> >
> > There are 3 scenarios with the multi-cable tiled monitors. and
> > non-resizeable fbdev.
> >
> > a) it's plugged in at boot. both cables are detected, fbdev gets a
> > full tiled mode.
>
> Yes this works as expected
>
> > b) it's not plugged in at boot, the user starts plugging it in, fbdev
> > was inited via the panel or another monitor. fbdev won't resize.
> > c) it's half plugged in at boot, then you get a non-tiled mode, and
> > fbdev can't resize to tiled anyways.
>
> In b and c, when its booted with only 1 cable connected and/or hotplugged only
> one cable after boot, I fallback to fisrt available non tiled mode, does that sound good?
>
> >
> > Also plugging in one of these multi-cable monitors piecemeal is going
> > to take multiple seconds for the user to do physical cable plugging.
>
> So still good with ignoring the second hotplug completely?
> However i donno where in the fb helper to stop passing the modeset down
> after the drm_fb_helper_hotplug_event()
I don't think you can ignore it completely. I think you just have to
make the mode picking logic pick the right answer somehow.
So you can tell if width/height are going to be lower than the tiled
mode size, and in that case just don't enable the secondary tile.
Dave.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [PATCH] drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-11-06 11:34 ` Daniel Stone
0 siblings, 0 replies; 30+ messages in thread
From: Daniel Stone @ 2019-11-06 11:34 UTC (permalink / raw)
To: Dave Airlie; +Cc: Dave Airlie, Intel Graphics Development, dri-devel
Hi,
On Wed, 6 Nov 2019 at 02:47, Dave Airlie <airlied@gmail.com> wrote:
> Otherwise I think this seems fine, though it does beg the question in
> my mind of what happens if I get 2 8K monitors, and plug the first
> tile of one in, and the second tile of the other in.
Honestly in that case I think 'you get to literally keep both pieces'
is a reasonable answer.
Cheers,
Daniel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-11-06 11:34 ` Daniel Stone
0 siblings, 0 replies; 30+ messages in thread
From: Daniel Stone @ 2019-11-06 11:34 UTC (permalink / raw)
To: Dave Airlie
Cc: Manasi Navare, Dave Airlie, Intel Graphics Development, dri-devel
Hi,
On Wed, 6 Nov 2019 at 02:47, Dave Airlie <airlied@gmail.com> wrote:
> Otherwise I think this seems fine, though it does beg the question in
> my mind of what happens if I get 2 8K monitors, and plug the first
> tile of one in, and the second tile of the other in.
Honestly in that case I think 'you get to literally keep both pieces'
is a reasonable answer.
Cheers,
Daniel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-11-06 11:34 ` Daniel Stone
0 siblings, 0 replies; 30+ messages in thread
From: Daniel Stone @ 2019-11-06 11:34 UTC (permalink / raw)
To: Dave Airlie; +Cc: Dave Airlie, Intel Graphics Development, dri-devel
Hi,
On Wed, 6 Nov 2019 at 02:47, Dave Airlie <airlied@gmail.com> wrote:
> Otherwise I think this seems fine, though it does beg the question in
> my mind of what happens if I get 2 8K monitors, and plug the first
> tile of one in, and the second tile of the other in.
Honestly in that case I think 'you get to literally keep both pieces'
is a reasonable answer.
Cheers,
Daniel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [PATCH] drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-11-06 20:37 ` Manasi Navare
0 siblings, 0 replies; 30+ messages in thread
From: Manasi Navare @ 2019-11-06 20:37 UTC (permalink / raw)
To: Dave Airlie; +Cc: Dave Airlie, Intel Graphics Development, dri-devel
On Wed, Nov 06, 2019 at 12:47:16PM +1000, Dave Airlie wrote:
> On Fri, 1 Nov 2019 at 07:46, Manasi Navare <manasi.d.navare@intel.com> wrote:
> >
> > In case of tiled displays, if we hotplug just one connector,
> > fbcon currently just selects the preferred mode and if it is
> > tiled mode then that becomes a problem if rest of the tiles are
> > not present.
> > So in the fbdev driver on hotplug when we probe the client modeset,
> > we we dont find all the connectors for all tiles, then on a connector
> > with one tile, just fallback to the first available non tiled mode
> > to display over a single connector.
> >
> > Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Suggested-by: Dave Airlie <airlied@redhat.com>
> > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Cc: Dave Airlie <airlied@redhat.com>
> > Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
> > ---
> > drivers/gpu/drm/drm_client_modeset.c | 29 ++++++++++++++++++++++++++++
> > 1 file changed, 29 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/drm_client_modeset.c b/drivers/gpu/drm/drm_client_modeset.c
> > index 895b73f23079..e28a723587db 100644
> > --- a/drivers/gpu/drm/drm_client_modeset.c
> > +++ b/drivers/gpu/drm/drm_client_modeset.c
> > @@ -114,6 +114,20 @@ drm_client_find_modeset(struct drm_client_dev *client, struct drm_crtc *crtc)
> > return NULL;
> > }
> >
> > +static struct drm_display_mode *
> > +drm_connector_fallback_non_tiled_mode(struct drm_connector *connector)
> > +{
> > + struct drm_display_mode *mode;
> > +
> > + list_for_each_entry(mode, &connector->modes, head) {
> > + if (mode->hdisplay == connector->tile_h_size &&
> > + mode->vdisplay == connector->tile_v_size)
> > + continue;
> > + return mode;
> > + }
> > + return NULL;
> > +}
> > +
> > static struct drm_display_mode *
> > drm_connector_has_preferred_mode(struct drm_connector *connector, int width, int height)
> > {
> > @@ -348,8 +362,17 @@ static bool drm_client_target_preferred(struct drm_connector **connectors,
> > struct drm_connector *connector;
> > u64 conn_configured = 0;
> > int tile_pass = 0;
> > + int num_tiled_conns = 0;
> > int i;
> >
> > + for (i = 0; i < connector_count; i++) {
> > + connector = connectors[i];
> > + if (!connector->has_tile)
> > + continue;
> > +
> > + num_tiled_conns ++;
>
> Drop the space before the ++ here. Maybe just make this
>
> if (connectors[i]->has_tile)
> num_tiled_conns++;
Sure will modify like above and add your r-b afterwards.
Thank you so much for your review.
This only covers the hotplug case with 1 connector hotplugged and need to still
modify the fb dev code to ignore the second hotplug which I cant seem to figure out how
to avoid the second hotplug from going through a modeset and retain the first modeset on screen.
Also I will send a follow up patch to fallback to first non tiled mode in case of connected boot.
But its okay for that to be separate patch than this right?
Regards
Manasi
>
> Reviewed-by: Dave Airlie <airlied@redhat.com>
>
> Otherwise I think this seems fine, though it does beg the question in
> my mind of what happens if I get 2 8K monitors, and plug the first
> tile of one in, and the second tile of the other in.
>
> Dave.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-11-06 20:37 ` Manasi Navare
0 siblings, 0 replies; 30+ messages in thread
From: Manasi Navare @ 2019-11-06 20:37 UTC (permalink / raw)
To: Dave Airlie; +Cc: Dave Airlie, Intel Graphics Development, dri-devel
On Wed, Nov 06, 2019 at 12:47:16PM +1000, Dave Airlie wrote:
> On Fri, 1 Nov 2019 at 07:46, Manasi Navare <manasi.d.navare@intel.com> wrote:
> >
> > In case of tiled displays, if we hotplug just one connector,
> > fbcon currently just selects the preferred mode and if it is
> > tiled mode then that becomes a problem if rest of the tiles are
> > not present.
> > So in the fbdev driver on hotplug when we probe the client modeset,
> > we we dont find all the connectors for all tiles, then on a connector
> > with one tile, just fallback to the first available non tiled mode
> > to display over a single connector.
> >
> > Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Suggested-by: Dave Airlie <airlied@redhat.com>
> > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Cc: Dave Airlie <airlied@redhat.com>
> > Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
> > ---
> > drivers/gpu/drm/drm_client_modeset.c | 29 ++++++++++++++++++++++++++++
> > 1 file changed, 29 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/drm_client_modeset.c b/drivers/gpu/drm/drm_client_modeset.c
> > index 895b73f23079..e28a723587db 100644
> > --- a/drivers/gpu/drm/drm_client_modeset.c
> > +++ b/drivers/gpu/drm/drm_client_modeset.c
> > @@ -114,6 +114,20 @@ drm_client_find_modeset(struct drm_client_dev *client, struct drm_crtc *crtc)
> > return NULL;
> > }
> >
> > +static struct drm_display_mode *
> > +drm_connector_fallback_non_tiled_mode(struct drm_connector *connector)
> > +{
> > + struct drm_display_mode *mode;
> > +
> > + list_for_each_entry(mode, &connector->modes, head) {
> > + if (mode->hdisplay == connector->tile_h_size &&
> > + mode->vdisplay == connector->tile_v_size)
> > + continue;
> > + return mode;
> > + }
> > + return NULL;
> > +}
> > +
> > static struct drm_display_mode *
> > drm_connector_has_preferred_mode(struct drm_connector *connector, int width, int height)
> > {
> > @@ -348,8 +362,17 @@ static bool drm_client_target_preferred(struct drm_connector **connectors,
> > struct drm_connector *connector;
> > u64 conn_configured = 0;
> > int tile_pass = 0;
> > + int num_tiled_conns = 0;
> > int i;
> >
> > + for (i = 0; i < connector_count; i++) {
> > + connector = connectors[i];
> > + if (!connector->has_tile)
> > + continue;
> > +
> > + num_tiled_conns ++;
>
> Drop the space before the ++ here. Maybe just make this
>
> if (connectors[i]->has_tile)
> num_tiled_conns++;
Sure will modify like above and add your r-b afterwards.
Thank you so much for your review.
This only covers the hotplug case with 1 connector hotplugged and need to still
modify the fb dev code to ignore the second hotplug which I cant seem to figure out how
to avoid the second hotplug from going through a modeset and retain the first modeset on screen.
Also I will send a follow up patch to fallback to first non tiled mode in case of connected boot.
But its okay for that to be separate patch than this right?
Regards
Manasi
>
> Reviewed-by: Dave Airlie <airlied@redhat.com>
>
> Otherwise I think this seems fine, though it does beg the question in
> my mind of what happens if I get 2 8K monitors, and plug the first
> tile of one in, and the second tile of the other in.
>
> Dave.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-11-06 20:37 ` Manasi Navare
0 siblings, 0 replies; 30+ messages in thread
From: Manasi Navare @ 2019-11-06 20:37 UTC (permalink / raw)
To: Dave Airlie; +Cc: Dave Airlie, Intel Graphics Development, dri-devel
On Wed, Nov 06, 2019 at 12:47:16PM +1000, Dave Airlie wrote:
> On Fri, 1 Nov 2019 at 07:46, Manasi Navare <manasi.d.navare@intel.com> wrote:
> >
> > In case of tiled displays, if we hotplug just one connector,
> > fbcon currently just selects the preferred mode and if it is
> > tiled mode then that becomes a problem if rest of the tiles are
> > not present.
> > So in the fbdev driver on hotplug when we probe the client modeset,
> > we we dont find all the connectors for all tiles, then on a connector
> > with one tile, just fallback to the first available non tiled mode
> > to display over a single connector.
> >
> > Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Suggested-by: Dave Airlie <airlied@redhat.com>
> > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Cc: Dave Airlie <airlied@redhat.com>
> > Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
> > ---
> > drivers/gpu/drm/drm_client_modeset.c | 29 ++++++++++++++++++++++++++++
> > 1 file changed, 29 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/drm_client_modeset.c b/drivers/gpu/drm/drm_client_modeset.c
> > index 895b73f23079..e28a723587db 100644
> > --- a/drivers/gpu/drm/drm_client_modeset.c
> > +++ b/drivers/gpu/drm/drm_client_modeset.c
> > @@ -114,6 +114,20 @@ drm_client_find_modeset(struct drm_client_dev *client, struct drm_crtc *crtc)
> > return NULL;
> > }
> >
> > +static struct drm_display_mode *
> > +drm_connector_fallback_non_tiled_mode(struct drm_connector *connector)
> > +{
> > + struct drm_display_mode *mode;
> > +
> > + list_for_each_entry(mode, &connector->modes, head) {
> > + if (mode->hdisplay == connector->tile_h_size &&
> > + mode->vdisplay == connector->tile_v_size)
> > + continue;
> > + return mode;
> > + }
> > + return NULL;
> > +}
> > +
> > static struct drm_display_mode *
> > drm_connector_has_preferred_mode(struct drm_connector *connector, int width, int height)
> > {
> > @@ -348,8 +362,17 @@ static bool drm_client_target_preferred(struct drm_connector **connectors,
> > struct drm_connector *connector;
> > u64 conn_configured = 0;
> > int tile_pass = 0;
> > + int num_tiled_conns = 0;
> > int i;
> >
> > + for (i = 0; i < connector_count; i++) {
> > + connector = connectors[i];
> > + if (!connector->has_tile)
> > + continue;
> > +
> > + num_tiled_conns ++;
>
> Drop the space before the ++ here. Maybe just make this
>
> if (connectors[i]->has_tile)
> num_tiled_conns++;
Sure will modify like above and add your r-b afterwards.
Thank you so much for your review.
This only covers the hotplug case with 1 connector hotplugged and need to still
modify the fb dev code to ignore the second hotplug which I cant seem to figure out how
to avoid the second hotplug from going through a modeset and retain the first modeset on screen.
Also I will send a follow up patch to fallback to first non tiled mode in case of connected boot.
But its okay for that to be separate patch than this right?
Regards
Manasi
>
> Reviewed-by: Dave Airlie <airlied@redhat.com>
>
> Otherwise I think this seems fine, though it does beg the question in
> my mind of what happens if I get 2 8K monitors, and plug the first
> tile of one in, and the second tile of the other in.
>
> Dave.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-11-06 23:54 ` Manasi Navare
0 siblings, 0 replies; 30+ messages in thread
From: Manasi Navare @ 2019-11-06 23:54 UTC (permalink / raw)
To: Dave Airlie; +Cc: David Airlie, Development, Intel, dri-devel
On Wed, Nov 06, 2019 at 12:50:21PM +1000, Dave Airlie wrote:
> On Tue, 5 Nov 2019 at 07:00, Manasi Navare <manasi.d.navare@intel.com> wrote:
> >
> > On Mon, Nov 04, 2019 at 07:48:26PM +1000, David Airlie wrote:
> > > On Mon, Nov 4, 2019 at 7:18 PM Daniel Vetter <daniel@ffwll.ch> wrote:
> > > >
> > > > On Thu, Oct 31, 2019 at 02:48:39PM -0700, Manasi Navare wrote:
> > > > > In case of tiled displays, if we hotplug just one connector,
> > > > > fbcon currently just selects the preferred mode and if it is
> > > > > tiled mode then that becomes a problem if rest of the tiles are
> > > > > not present.
> > > > > So in the fbdev driver on hotplug when we probe the client modeset,
> > > > > we we dont find all the connectors for all tiles, then on a connector
> > > > > with one tile, just fallback to the first available non tiled mode
> > > > > to display over a single connector.
> > > > >
> > > > > Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > > > Suggested-by: Dave Airlie <airlied@redhat.com>
> > > > > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > > > Cc: Dave Airlie <airlied@redhat.com>
> > > > > Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
> > > >
> > > > Hm, should we mayb have a slight timeout first to wait for the 2nd
> > > > connector? Otherwise lots of flickering going on when plugging in one of
> > > > these screens ...
> > >
> > > Not really,
> > >
> > > There are 3 scenarios with the multi-cable tiled monitors. and
> > > non-resizeable fbdev.
> > >
> > > a) it's plugged in at boot. both cables are detected, fbdev gets a
> > > full tiled mode.
> >
> > Yes this works as expected
> >
> > > b) it's not plugged in at boot, the user starts plugging it in, fbdev
> > > was inited via the panel or another monitor. fbdev won't resize.
> > > c) it's half plugged in at boot, then you get a non-tiled mode, and
> > > fbdev can't resize to tiled anyways.
> >
> > In b and c, when its booted with only 1 cable connected and/or hotplugged only
> > one cable after boot, I fallback to fisrt available non tiled mode, does that sound good?
> >
> > >
> > > Also plugging in one of these multi-cable monitors piecemeal is going
> > > to take multiple seconds for the user to do physical cable plugging.
> >
> > So still good with ignoring the second hotplug completely?
> > However i donno where in the fb helper to stop passing the modeset down
> > after the drm_fb_helper_hotplug_event()
>
> I don't think you can ignore it completely. I think you just have to
> make the mode picking logic pick the right answer somehow.
>
> So you can tell if width/height are going to be lower than the tiled
> mode size, and in that case just don't enable the secondary tile.
>
Ithink this tiled monitor is behaving in a way where if there are two ports connected,
on the reciever end it tries to join the outputs and if there is no output or a different output
other than tiled mode then it cant display anything so the moment i connect the second port,
it expects the full tiled output but since no modes on second connector, it doesnt display anytjing goes into power save
It almost makes me rethink our logic of falling back to the non tiled mode for the first hotplug since atleast this monitor
displays the single tile across the whole monitor by stretching it out and then after connecting second connector it can ideally
go back to a full tiled display
Thoughts?
Manasi
> Dave.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/fbdev: Fallback to non tiled mode if all tiles not present
@ 2019-11-06 23:54 ` Manasi Navare
0 siblings, 0 replies; 30+ messages in thread
From: Manasi Navare @ 2019-11-06 23:54 UTC (permalink / raw)
To: Dave Airlie; +Cc: David Airlie, Development, Intel, dri-devel
On Wed, Nov 06, 2019 at 12:50:21PM +1000, Dave Airlie wrote:
> On Tue, 5 Nov 2019 at 07:00, Manasi Navare <manasi.d.navare@intel.com> wrote:
> >
> > On Mon, Nov 04, 2019 at 07:48:26PM +1000, David Airlie wrote:
> > > On Mon, Nov 4, 2019 at 7:18 PM Daniel Vetter <daniel@ffwll.ch> wrote:
> > > >
> > > > On Thu, Oct 31, 2019 at 02:48:39PM -0700, Manasi Navare wrote:
> > > > > In case of tiled displays, if we hotplug just one connector,
> > > > > fbcon currently just selects the preferred mode and if it is
> > > > > tiled mode then that becomes a problem if rest of the tiles are
> > > > > not present.
> > > > > So in the fbdev driver on hotplug when we probe the client modeset,
> > > > > we we dont find all the connectors for all tiles, then on a connector
> > > > > with one tile, just fallback to the first available non tiled mode
> > > > > to display over a single connector.
> > > > >
> > > > > Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > > > Suggested-by: Dave Airlie <airlied@redhat.com>
> > > > > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > > > Cc: Dave Airlie <airlied@redhat.com>
> > > > > Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
> > > >
> > > > Hm, should we mayb have a slight timeout first to wait for the 2nd
> > > > connector? Otherwise lots of flickering going on when plugging in one of
> > > > these screens ...
> > >
> > > Not really,
> > >
> > > There are 3 scenarios with the multi-cable tiled monitors. and
> > > non-resizeable fbdev.
> > >
> > > a) it's plugged in at boot. both cables are detected, fbdev gets a
> > > full tiled mode.
> >
> > Yes this works as expected
> >
> > > b) it's not plugged in at boot, the user starts plugging it in, fbdev
> > > was inited via the panel or another monitor. fbdev won't resize.
> > > c) it's half plugged in at boot, then you get a non-tiled mode, and
> > > fbdev can't resize to tiled anyways.
> >
> > In b and c, when its booted with only 1 cable connected and/or hotplugged only
> > one cable after boot, I fallback to fisrt available non tiled mode, does that sound good?
> >
> > >
> > > Also plugging in one of these multi-cable monitors piecemeal is going
> > > to take multiple seconds for the user to do physical cable plugging.
> >
> > So still good with ignoring the second hotplug completely?
> > However i donno where in the fb helper to stop passing the modeset down
> > after the drm_fb_helper_hotplug_event()
>
> I don't think you can ignore it completely. I think you just have to
> make the mode picking logic pick the right answer somehow.
>
> So you can tell if width/height are going to be lower than the tiled
> mode size, and in that case just don't enable the secondary tile.
>
Ithink this tiled monitor is behaving in a way where if there are two ports connected,
on the reciever end it tries to join the outputs and if there is no output or a different output
other than tiled mode then it cant display anything so the moment i connect the second port,
it expects the full tiled output but since no modes on second connector, it doesnt display anytjing goes into power save
It almost makes me rethink our logic of falling back to the non tiled mode for the first hotplug since atleast this monitor
displays the single tile across the whole monitor by stretching it out and then after connecting second connector it can ideally
go back to a full tiled display
Thoughts?
Manasi
> Dave.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 30+ messages in thread
end of thread, other threads:[~2019-11-06 23:54 UTC | newest]
Thread overview: 30+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-31 21:48 [PATCH] drm/fbdev: Fallback to non tiled mode if all tiles not present Manasi Navare
2019-10-31 21:48 ` [Intel-gfx] " Manasi Navare
2019-10-31 21:48 ` Manasi Navare
2019-10-31 23:13 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-10-31 23:13 ` [Intel-gfx] " Patchwork
2019-10-31 23:41 ` ✓ Fi.CI.BAT: success " Patchwork
2019-10-31 23:41 ` [Intel-gfx] " Patchwork
2019-11-02 8:42 ` ✓ Fi.CI.IGT: " Patchwork
2019-11-02 8:42 ` [Intel-gfx] " Patchwork
2019-11-04 9:18 ` [Intel-gfx] [PATCH] " Daniel Vetter
2019-11-04 9:18 ` Daniel Vetter
[not found] ` <CAMwc25oYjL3K7dcikX-oM_Y4ZP1ZRwUDKvsKO69vg81ZU6Xg8A@mail.gmail.com>
2019-11-04 18:14 ` Daniel Vetter
2019-11-04 18:14 ` [Intel-gfx] " Daniel Vetter
2019-11-04 18:14 ` Daniel Vetter
2019-11-04 21:03 ` Manasi Navare
2019-11-04 21:03 ` [Intel-gfx] " Manasi Navare
2019-11-04 21:03 ` Manasi Navare
2019-11-06 2:50 ` Dave Airlie
2019-11-06 2:50 ` Dave Airlie
2019-11-06 23:54 ` Manasi Navare
2019-11-06 23:54 ` Manasi Navare
2019-11-06 2:47 ` Dave Airlie
2019-11-06 2:47 ` [Intel-gfx] " Dave Airlie
2019-11-06 2:47 ` Dave Airlie
2019-11-06 11:34 ` Daniel Stone
2019-11-06 11:34 ` [Intel-gfx] " Daniel Stone
2019-11-06 11:34 ` Daniel Stone
2019-11-06 20:37 ` Manasi Navare
2019-11-06 20:37 ` [Intel-gfx] " Manasi Navare
2019-11-06 20:37 ` Manasi Navare
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.