Separate panel orientation property creating and value setting
Subsystems (6)
v10 cover Separate panel orientation property creating and value setting
Some drivers, eg. mtk_drm and msm_drm, rely on the panel to set the orientation. Panel calls drm_connector_set_panel_orientation() to create orientation property and sets the value. However, connector properties can't be created after drm_dev_register() is called. The goal is to separate the orientation property creation, so drm drivers can create it earlier before drm_dev_register().
After this series, drm_connector_set_panel_orientation() works like before. It won't affect existing callers of drm_connector_set_panel_orientation(). The only difference is that some drm drivers can call drm_connector_init_panel_orientation_property() earlier.
Hsin-Yi Wang (4):
gpu: drm: separate panel orientation property creating and value
setting
drm/mediatek: init panel orientation property drm/msm: init panel orientation property
arm64: dts: mt8183: Add panel rotation
.../arm64/boot/dts/mediatek/mt8183-kukui.dtsi | 1 + drivers/gpu/drm/drm_connector.c | 58 ++++++++++++++----- drivers/gpu/drm/mediatek/mtk_dsi.c | 7 +++ drivers/gpu/drm/msm/dsi/dsi_manager.c | 4 ++ include/drm/drm_connector.h | 2 + 5 files changed, 59 insertions(+), 13 deletions(-)
Signature · 1 line
2.36.1.124.g0e6072fb45-goog
PATCH v10 1/4 gpu: drm: separate panel orientation property creating and value setting
drm_dev_register() sets connector->registration_state to DRM_CONNECTOR_REGISTERED and dev->registered to true. If drm_connector_set_panel_orientation() is first called after drm_dev_register(), it will fail several checks and results in following warning.
Add a function to create panel orientation property and set default value to UNKNOWN, so drivers can call this function to init the property earlier , and let the panel set the real value later.
[ 4.480976] ------------[ cut here ]------------ [ 4.485603] WARNING: CPU: 5 PID: 369 at drivers/gpu/drm/drm_mode_object.c:45 __drm_mode_object_add+0xb4/0xbc <snip> [ 4.609772] Call trace: [ 4.612208] __drm_mode_object_add+0xb4/0xbc [ 4.616466] drm_mode_object_add+0x20/0x2c [ 4.620552] drm_property_create+0xdc/0x174 [ 4.624723] drm_property_create_enum+0x34/0x98 [ 4.629241] drm_connector_set_panel_orientation+0x64/0xa0 [ 4.634716] boe_panel_get_modes+0x88/0xd8 [ 4.638802] drm_panel_get_modes+0x2c/0x48 [ 4.642887] panel_bridge_get_modes+0x1c/0x28 [ 4.647233] drm_bridge_connector_get_modes+0xa0/0xd4 [ 4.652273] drm_helper_probe_single_connector_modes+0x218/0x700 [ 4.658266] drm_mode_getconnector+0x1b4/0x45c [ 4.662699] drm_ioctl_kernel+0xac/0x128 [ 4.666611] drm_ioctl+0x268/0x410 [ 4.670002] drm_compat_ioctl+0xdc/0xf0 [ 4.673829] __arm64_compat_sys_ioctl+0xc8/0x100 [ 4.678436] el0_svc_common+0xf4/0x1c0 [ 4.682174] do_el0_svc_compat+0x28/0x3c [ 4.686088] el0_svc_compat+0x10/0x1c [ 4.689738] el0_sync_compat_handler+0xa8/0xcc [ 4.694171] el0_sync_compat+0x178/0x180 [ 4.698082] ---[ end trace b4f2db9d9c88610b ]--- [ 4.702721] ------------[ cut here ]------------ [ 4.707329] WARNING: CPU: 5 PID: 369 at drivers/gpu/drm/drm_mode_object.c:243 drm_object_attach_property+0x48/0xb8 <snip> [ 4.833830] Call trace: [ 4.836266] drm_object_attach_property+0x48/0xb8 [ 4.840958] drm_connector_set_panel_orientation+0x84/0xa0 [ 4.846432] boe_panel_get_modes+0x88/0xd8 [ 4.850516] drm_panel_get_modes+0x2c/0x48 [ 4.854600] panel_bridge_get_modes+0x1c/0x28 [ 4.858946] drm_bridge_connector_get_modes+0xa0/0xd4 [ 4.863984] drm_helper_probe_single_connector_modes+0x218/0x700 [ 4.869978] drm_mode_getconnector+0x1b4/0x45c [ 4.874410] drm_ioctl_kernel+0xac/0x128 [ 4.878320] drm_ioctl+0x268/0x410 [ 4.881711] drm_compat_ioctl+0xdc/0xf0 [ 4.885536] __arm64_compat_sys_ioctl+0xc8/0x100 [ 4.890142] el0_svc_common+0xf4/0x1c0 [ 4.893879] do_el0_svc_compat+0x28/0x3c [ 4.897791] el0_svc_compat+0x10/0x1c [ 4.901441] el0_sync_compat_handler+0xa8/0xcc [ 4.905873] el0_sync_compat+0x178/0x180 [ 4.909783] ---[ end trace b4f2db9d9c88610c ]---
---v9->v10: rebase to latest linux-next.
v9: https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/
v8: https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/
v7: https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/
--- drivers/gpu/drm/drm_connector.c | 58 +++++++++++++++++++++++++-------- include/drm/drm_connector.h | 2 ++ 2 files changed, 47 insertions(+), 13 deletions(-)
drivers/gpu/drm/drm_connector.c +45 -13
@@ -1252,7 +1252,7 @@ static const struct drm_prop_enum_list dp_colorspaces[] = {* INPUT_PROP_DIRECT) will still map 1:1 to the actual LCD panel * coordinates, so if userspace rotates the picture to adjust for * the orientation it must also apply the same transformation to the -* touchscreen input coordinates. This property is initialized by calling +* touchscreen input coordinates. This property value is set by calling * drm_connector_set_panel_orientation() or * drm_connector_set_panel_orientation_with_quirk() *
@@ -2310,8 +2310,8 @@ EXPORT_SYMBOL(drm_connector_set_vrr_capable_property);* @connector: connector for which to set the panel-orientation property. * @panel_orientation: drm_panel_orientation value to set * -* This function sets the connector's panel_orientation and attaches -* a "panel orientation" property to the connector. +* This function sets the connector's panel_orientation value. If the property +* doesn't exist, it will try to create one. * * Calling this function on a connector where the panel_orientation has * already been set is a no-op (e.g. the orientation has been overridden with
@@ -2343,18 +2343,13 @@ int drm_connector_set_panel_orientation( prop = dev->mode_config.panel_orientation_property;if (!prop) { - prop =drm_property_create_enum (dev,DRM_MODE_PROP_IMMUTABLE , -"panel orientation" , - drm_panel_orientation_enum_list, -ARRAY_SIZE (drm_panel_orientation_enum_list)); -if (!prop) +if (drm_connector_init_panel_orientation_property (connector) <0 )return -ENOMEM ; - - dev->mode_config.panel_orientation_property = prop; + prop = dev->mode_config.panel_orientation_property; } -drm_object_attach_property (&connector->base, prop, - info->panel_orientation); +drm_object_property_set_value (&connector->base, prop, + info->panel_orientation);return 0 ; }EXPORT_SYMBOL (drm_connector_set_panel_orientation);
@@ -2362,7 +2357,7 @@ EXPORT_SYMBOL(drm_connector_set_panel_orientation);/** * drm_connector_set_panel_orientation_with_quirk - set the * connector's panel_orientation after checking for quirks -* @connector: connector for which to init the panel-orientation property. +* @connector: connector for which to set the panel-orientation property. * @panel_orientation: drm_panel_orientation value to set * @width: width in pixels of the panel, used for panel quirk detection * @height: height in pixels of the panel, used for panel quirk detection
@@ -2389,6 +2384,43 @@ int drm_connector_set_panel_orientation_with_quirk( }EXPORT_SYMBOL (drm_connector_set_panel_orientation_with_quirk); +/** +* drm_connector_init_panel_orientation_property - +* create the connector's panel orientation property +* +* This function attaches a "panel orientation" property to the connector +* and initializes its value to DRM_MODE_PANEL_ORIENTATION_UNKNOWN. +* +* The value of the property can be set by drm_connector_set_panel_orientation() +* or drm_connector_set_panel_orientation_with_quirk() later. +* +* Returns: +* Zero on success, negative errno on failure. +*/ +int drm_connector_init_panel_orientation_property ( +struct drm_connector *connector) +{ +struct drm_device *dev = connector->dev; +struct drm_property *prop; + +if (dev->mode_config.panel_orientation_property) +return 0 ; + + prop =drm_property_create_enum (dev,DRM_MODE_PROP_IMMUTABLE , +"panel orientation" , + drm_panel_orientation_enum_list, +ARRAY_SIZE (drm_panel_orientation_enum_list)); +if (!prop) +return -ENOMEM ; + + dev->mode_config.panel_orientation_property = prop; +drm_object_attach_property (&connector->base, prop, +DRM_MODE_PANEL_ORIENTATION_UNKNOWN ); + +return 0 ; +} +EXPORT_SYMBOL (drm_connector_init_panel_orientation_property); +static const struct drm_prop_enum_list privacy_screen_enum[] = { {PRIVACY_SCREEN_DISABLED ,"Disabled" }, {PRIVACY_SCREEN_ENABLED ,"Enabled" },
include/drm/drm_connector.h +2 -0
@@ -1802,6 +1802,8 @@ int drm_connector_set_panel_orientation_with_quirk(struct drm_connector *connector, enum drm_panel_orientation panel_orientation, int width, int height); +int drm_connector_init_panel_orientation_property ( +struct drm_connector *connector);int drm_connector_attach_max_bpc_property (struct drm_connector *connector,int min,int max);void drm_connector_create_privacy_screen_properties (struct drm_connector *conn);
Signature · 1 line
2.36.1.124.g0e6072fb45-goog
Re: [PATCH v10 1/4] gpu: drm: separate panel orientation property creating and value setting
Hi,
Quoted 152 lines · Hsin-Yi Wang
drm_dev_register()setsconnector->registration_statetoDRM_CONNECTOR_REGISTEREDanddev->registeredto true. Ifdrm_connector_set_panel_orientation()is first called afterdrm_dev_register(), it will fail several checks and results in following warning.Add a function to create panel orientation property and set default value to UNKNOWN, so drivers can call this function to init the property earlier , and let the panel set the real value later.
[ 4.480976] ------------[ cut here ]------------ [ 4.485603] WARNING: CPU: 5 PID: 369 at drivers/gpu/drm/drm_mode_object.c:45 __drm_mode_object_add+0xb4/0xbc <snip> [ 4.609772] Call trace: [ 4.612208] __drm_mode_object_add+0xb4/0xbc [ 4.616466] drm_mode_object_add+0x20/0x2c [ 4.620552] drm_property_create+0xdc/0x174 [ 4.624723] drm_property_create_enum+0x34/0x98 [ 4.629241] drm_connector_set_panel_orientation+0x64/0xa0 [ 4.634716] boe_panel_get_modes+0x88/0xd8 [ 4.638802] drm_panel_get_modes+0x2c/0x48 [ 4.642887] panel_bridge_get_modes+0x1c/0x28 [ 4.647233] drm_bridge_connector_get_modes+0xa0/0xd4 [ 4.652273] drm_helper_probe_single_connector_modes+0x218/0x700 [ 4.658266] drm_mode_getconnector+0x1b4/0x45c [ 4.662699] drm_ioctl_kernel+0xac/0x128 [ 4.666611] drm_ioctl+0x268/0x410 [ 4.670002] drm_compat_ioctl+0xdc/0xf0 [ 4.673829] __arm64_compat_sys_ioctl+0xc8/0x100 [ 4.678436] el0_svc_common+0xf4/0x1c0 [ 4.682174] do_el0_svc_compat+0x28/0x3c [ 4.686088] el0_svc_compat+0x10/0x1c [ 4.689738] el0_sync_compat_handler+0xa8/0xcc [ 4.694171] el0_sync_compat+0x178/0x180 [ 4.698082] ---[ end trace b4f2db9d9c88610b ]--- [ 4.702721] ------------[ cut here ]------------ [ 4.707329] WARNING: CPU: 5 PID: 369 at drivers/gpu/drm/drm_mode_object.c:243 drm_object_attach_property+0x48/0xb8 <snip> [ 4.833830] Call trace: [ 4.836266] drm_object_attach_property+0x48/0xb8 [ 4.840958] drm_connector_set_panel_orientation+0x84/0xa0 [ 4.846432] boe_panel_get_modes+0x88/0xd8 [ 4.850516] drm_panel_get_modes+0x2c/0x48 [ 4.854600] panel_bridge_get_modes+0x1c/0x28 [ 4.858946] drm_bridge_connector_get_modes+0xa0/0xd4 [ 4.863984] drm_helper_probe_single_connector_modes+0x218/0x700 [ 4.869978] drm_mode_getconnector+0x1b4/0x45c [ 4.874410] drm_ioctl_kernel+0xac/0x128 [ 4.878320] drm_ioctl+0x268/0x410 [ 4.881711] drm_compat_ioctl+0xdc/0xf0 [ 4.885536] __arm64_compat_sys_ioctl+0xc8/0x100 [ 4.890142] el0_svc_common+0xf4/0x1c0 [ 4.893879] do_el0_svc_compat+0x28/0x3c [ 4.897791] el0_svc_compat+0x10/0x1c [ 4.901441] el0_sync_compat_handler+0xa8/0xcc [ 4.905873] el0_sync_compat+0x178/0x180 [ 4.909783] ---[ end trace b4f2db9d9c88610c ]---Signed-off-by Hsin-Yi Wang <[email protected]>Reviewed-by Sean Paul <[email protected]>---
v9->v10: rebase to latest linux-next.
v9: https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/
v8: https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/
v7: https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/--- drivers/gpu/drm/drm_connector.c | 58 +++++++++++++++++++++++++-------- include/drm/drm_connector.h | 2 ++ 2 files changed, 47 insertions(+), 13 deletions(-)drivers/gpu/drm/drm_connector.c +30
-13@@ -1252,7 +1252,7 @@ static const struct drm_prop_enum_list dp_colorspaces[] = {* INPUT_PROP_DIRECT) will still map 1:1 to the actual LCD panel * coordinates, so if userspace rotates the picture to adjust for * the orientation it must also apply the same transformation to the -* touchscreen input coordinates. This property is initialized by calling +* touchscreen input coordinates. This property value is set by calling * drm_connector_set_panel_orientation() or * drm_connector_set_panel_orientation_with_quirk() * @@ -2310,8 +2310,8 @@ EXPORT_SYMBOL(drm_connector_set_vrr_capable_property);* @connector: connector for which to set the panel-orientation property. * @panel_orientation: drm_panel_orientation value to set * -* This function sets the connector's panel_orientation and attaches -* a "panel orientation" property to the connector. +* This function sets the connector's panel_orientation value. If the property +* doesn't exist, it will try to create one. * * Calling this function on a connector where the panel_orientation has * already been set is a no-op (e.g. the orientation has been overridden with @@ -2343,18 +2343,13 @@ int drm_connector_set_panel_orientation( prop = dev->mode_config.panel_orientation_property;if (!prop) { - prop =drm_property_create_enum (dev,DRM_MODE_PROP_IMMUTABLE , -"panel orientation" , - drm_panel_orientation_enum_list, -ARRAY_SIZE (drm_panel_orientation_enum_list)); -if (!prop) +if (drm_connector_init_panel_orientation_property (connector) <0 )return -ENOMEM ; - - dev->mode_config.panel_orientation_property = prop; + prop = dev->mode_config.panel_orientation_property; } -drm_object_attach_property (&connector->base, prop, - info->panel_orientation); +drm_object_property_set_value (&connector->base, prop, + info->panel_orientation);return 0 ; }EXPORT_SYMBOL (drm_connector_set_panel_orientation);@@ -2362,7 +2357,7 @@ EXPORT_SYMBOL(drm_connector_set_panel_orientation);/** * drm_connector_set_panel_orientation_with_quirk - set the * connector's panel_orientation after checking for quirks -* @connector: connector for which to init the panel-orientation property. +* @connector: connector for which to set the panel-orientation property. * @panel_orientation: drm_panel_orientation value to set * @width: width in pixels of the panel, used for panel quirk detection * @height: height in pixels of the panel, used for panel quirk detection @@ -2389,6 +2384,43 @@ int drm_connector_set_panel_orientation_with_quirk( }EXPORT_SYMBOL (drm_connector_set_panel_orientation_with_quirk); +/** +* drm_connector_init_panel_orientation_property - +* create the connector's panel orientation property +* +* This function attaches a "panel orientation" property to the connector +* and initializes its value to DRM_MODE_PANEL_ORIENTATION_UNKNOWN. +* +* The value of the property can be set by drm_connector_set_panel_orientation() +* or drm_connector_set_panel_orientation_with_quirk() later. +* +* Returns: +* Zero on success, negative errno on failure. +*/ +int drm_connector_init_panel_orientation_property ( +struct drm_connector *connector) +{ +struct drm_device *dev = connector->dev; +struct drm_property *prop; + +if (dev->mode_config.panel_orientation_property) +return 0 ; +
drivers/gpu/drm/drm_connector.c int drm_connector_set_panel_orientation_with_quirk( · line 2418
Quoted 10 lines
drivers/gpu/drm/drm_connector.c +10
-0+ prop =drm_property_create_enum (dev,DRM_MODE_PROP_IMMUTABLE , +"panel orientation" , + drm_panel_orientation_enum_list, +ARRAY_SIZE (drm_panel_orientation_enum_list)); +if (!prop) +return -ENOMEM ; + + dev->mode_config.panel_orientation_property = prop; +drm_object_attach_property (&connector->base, prop, +DRM_MODE_PANEL_ORIENTATION_UNKNOWN );
DRM_MODE_PANEL_ORIENTATION_UNKNOWN is -1 which is not a valid value for an enum. IOW when the panel-orientation is DRM_MODE_PANEL_ORIENTATION_UNKNOWN then the property should not be created on the drm-connector object at all.
Which brings us back to what I said in reply to the coverletter, it seems that you have a probe ordering problem here; and fixing that issue would make this patch-set unnecessary.
Regards,
Hans
Quoted 21 lines
drivers/gpu/drm/drm_connector.c +5
-0+ +return 0 ; +} +EXPORT_SYMBOL (drm_connector_init_panel_orientation_property); +static const struct drm_prop_enum_list privacy_screen_enum[] = { {PRIVACY_SCREEN_DISABLED ,"Disabled" }, {PRIVACY_SCREEN_ENABLED ,"Enabled" },include/drm/drm_connector.h +2
-0@@ -1802,6 +1802,8 @@ int drm_connector_set_panel_orientation_with_quirk(struct drm_connector *connector, enum drm_panel_orientation panel_orientation, int width, int height); +int drm_connector_init_panel_orientation_property ( +struct drm_connector *connector);int drm_connector_attach_max_bpc_property (struct drm_connector *connector,int min,int max);void drm_connector_create_privacy_screen_properties (struct drm_connector *conn);
Re: [PATCH v10 1/4] gpu: drm: separate panel orientation property creating and value setting
Hi,
Quoted 161 lines · Hans de Goede
Hi,
Quoted 158 lines · Hsin-Yi Wang
drm_dev_register()setsconnector->registration_statetoDRM_CONNECTOR_REGISTEREDanddev->registeredto true. Ifdrm_connector_set_panel_orientation()is first called afterdrm_dev_register(), it will fail several checks and results in following warning.Add a function to create panel orientation property and set default value to UNKNOWN, so drivers can call this function to init the property earlier , and let the panel set the real value later.
[ 4.480976] ------------[ cut here ]------------ [ 4.485603] WARNING: CPU: 5 PID: 369 at drivers/gpu/drm/drm_mode_object.c:45 __drm_mode_object_add+0xb4/0xbc <snip> [ 4.609772] Call trace: [ 4.612208] __drm_mode_object_add+0xb4/0xbc [ 4.616466] drm_mode_object_add+0x20/0x2c [ 4.620552] drm_property_create+0xdc/0x174 [ 4.624723] drm_property_create_enum+0x34/0x98 [ 4.629241] drm_connector_set_panel_orientation+0x64/0xa0 [ 4.634716] boe_panel_get_modes+0x88/0xd8 [ 4.638802] drm_panel_get_modes+0x2c/0x48 [ 4.642887] panel_bridge_get_modes+0x1c/0x28 [ 4.647233] drm_bridge_connector_get_modes+0xa0/0xd4 [ 4.652273] drm_helper_probe_single_connector_modes+0x218/0x700 [ 4.658266] drm_mode_getconnector+0x1b4/0x45c [ 4.662699] drm_ioctl_kernel+0xac/0x128 [ 4.666611] drm_ioctl+0x268/0x410 [ 4.670002] drm_compat_ioctl+0xdc/0xf0 [ 4.673829] __arm64_compat_sys_ioctl+0xc8/0x100 [ 4.678436] el0_svc_common+0xf4/0x1c0 [ 4.682174] do_el0_svc_compat+0x28/0x3c [ 4.686088] el0_svc_compat+0x10/0x1c [ 4.689738] el0_sync_compat_handler+0xa8/0xcc [ 4.694171] el0_sync_compat+0x178/0x180 [ 4.698082] ---[ end trace b4f2db9d9c88610b ]--- [ 4.702721] ------------[ cut here ]------------ [ 4.707329] WARNING: CPU: 5 PID: 369 at drivers/gpu/drm/drm_mode_object.c:243 drm_object_attach_property+0x48/0xb8 <snip> [ 4.833830] Call trace: [ 4.836266] drm_object_attach_property+0x48/0xb8 [ 4.840958] drm_connector_set_panel_orientation+0x84/0xa0 [ 4.846432] boe_panel_get_modes+0x88/0xd8 [ 4.850516] drm_panel_get_modes+0x2c/0x48 [ 4.854600] panel_bridge_get_modes+0x1c/0x28 [ 4.858946] drm_bridge_connector_get_modes+0xa0/0xd4 [ 4.863984] drm_helper_probe_single_connector_modes+0x218/0x700 [ 4.869978] drm_mode_getconnector+0x1b4/0x45c [ 4.874410] drm_ioctl_kernel+0xac/0x128 [ 4.878320] drm_ioctl+0x268/0x410 [ 4.881711] drm_compat_ioctl+0xdc/0xf0 [ 4.885536] __arm64_compat_sys_ioctl+0xc8/0x100 [ 4.890142] el0_svc_common+0xf4/0x1c0 [ 4.893879] do_el0_svc_compat+0x28/0x3c [ 4.897791] el0_svc_compat+0x10/0x1c [ 4.901441] el0_sync_compat_handler+0xa8/0xcc [ 4.905873] el0_sync_compat+0x178/0x180 [ 4.909783] ---[ end trace b4f2db9d9c88610c ]---Signed-off-by Hsin-Yi Wang <[email protected]>Reviewed-by Sean Paul <[email protected]>---
v9->v10: rebase to latest linux-next.
v9: https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/
v8: https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/
v7: https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/--- drivers/gpu/drm/drm_connector.c | 58 +++++++++++++++++++++++++-------- include/drm/drm_connector.h | 2 ++ 2 files changed, 47 insertions(+), 13 deletions(-)drivers/gpu/drm/drm_connector.c +36
-13@@ -1252,7 +1252,7 @@ static const struct drm_prop_enum_list dp_colorspaces[] = {* INPUT_PROP_DIRECT) will still map 1:1 to the actual LCD panel * coordinates, so if userspace rotates the picture to adjust for * the orientation it must also apply the same transformation to the -* touchscreen input coordinates. This property is initialized by calling +* touchscreen input coordinates. This property value is set by calling * drm_connector_set_panel_orientation() or * drm_connector_set_panel_orientation_with_quirk() * @@ -2310,8 +2310,8 @@ EXPORT_SYMBOL(drm_connector_set_vrr_capable_property);* @connector: connector for which to set the panel-orientation property. * @panel_orientation: drm_panel_orientation value to set * -* This function sets the connector's panel_orientation and attaches -* a "panel orientation" property to the connector. +* This function sets the connector's panel_orientation value. If the property +* doesn't exist, it will try to create one. * * Calling this function on a connector where the panel_orientation has * already been set is a no-op (e.g. the orientation has been overridden with @@ -2343,18 +2343,13 @@ int drm_connector_set_panel_orientation( prop = dev->mode_config.panel_orientation_property;if (!prop) { - prop =drm_property_create_enum (dev,DRM_MODE_PROP_IMMUTABLE , -"panel orientation" , - drm_panel_orientation_enum_list, -ARRAY_SIZE (drm_panel_orientation_enum_list)); -if (!prop) +if (drm_connector_init_panel_orientation_property (connector) <0 )return -ENOMEM ; - - dev->mode_config.panel_orientation_property = prop; + prop = dev->mode_config.panel_orientation_property; } -drm_object_attach_property (&connector->base, prop, - info->panel_orientation); +drm_object_property_set_value (&connector->base, prop, + info->panel_orientation);return 0 ; }EXPORT_SYMBOL (drm_connector_set_panel_orientation);@@ -2362,7 +2357,7 @@ EXPORT_SYMBOL(drm_connector_set_panel_orientation);/** * drm_connector_set_panel_orientation_with_quirk - set the * connector's panel_orientation after checking for quirks -* @connector: connector for which to init the panel-orientation property. +* @connector: connector for which to set the panel-orientation property. * @panel_orientation: drm_panel_orientation value to set * @width: width in pixels of the panel, used for panel quirk detection * @height: height in pixels of the panel, used for panel quirk detection @@ -2389,6 +2384,43 @@ int drm_connector_set_panel_orientation_with_quirk( }EXPORT_SYMBOL (drm_connector_set_panel_orientation_with_quirk); +/** +* drm_connector_init_panel_orientation_property - +* create the connector's panel orientation property +* +* This function attaches a "panel orientation" property to the connector +* and initializes its value to DRM_MODE_PANEL_ORIENTATION_UNKNOWN. +* +* The value of the property can be set by drm_connector_set_panel_orientation() +* or drm_connector_set_panel_orientation_with_quirk() later. +* +* Returns: +* Zero on success, negative errno on failure. +*/ +int drm_connector_init_panel_orientation_property ( +struct drm_connector *connector) +{ +struct drm_device *dev = connector->dev; +struct drm_property *prop; + +if (dev->mode_config.panel_orientation_property) +return 0 ; + + prop =drm_property_create_enum (dev,DRM_MODE_PROP_IMMUTABLE , +"panel orientation" , + drm_panel_orientation_enum_list, +ARRAY_SIZE (drm_panel_orientation_enum_list)); +if (!prop) +return -ENOMEM ;
Quoted 8 lines
drivers/gpu/drm/drm_connector.c int drm_connector_set_panel_orientation_with_quirk( · line 2418
Quoted 4 lines
drivers/gpu/drm/drm_connector.c +4
-0+ + dev->mode_config.panel_orientation_property = prop; +drm_object_attach_property (&connector->base, prop, +DRM_MODE_PANEL_ORIENTATION_UNKNOWN );
DRM_MODE_PANEL_ORIENTATION_UNKNOWNis -1 which is not a valid value for an enum. IOW when the panel-orientation isDRM_MODE_PANEL_ORIENTATION_UNKNOWNthen the property should not be created on the drm-connector object at all.
p.s. note that the original drm_connector_set_panel_orientation() avoids ever creating the property when the orientation is unknown because of this bit of code near the top of the function:
/* Don't attach the property if the orientation is unknown */
if (panel_orientation == DRM_MODE_PANEL_ORIENTATION_UNKNOWN)
return 0;Quoted 3 lines
Which brings us back to what I said in reply to the coverletter, it seems that you have a probe ordering problem here; and fixing that issue would make this patch-set unnecessary.
Regards,
Hans
Quoted 21 lines
Quoted 21 lines
drivers/gpu/drm/drm_connector.c +5
-0+ +return 0 ; +} +EXPORT_SYMBOL (drm_connector_init_panel_orientation_property); +static const struct drm_prop_enum_list privacy_screen_enum[] = { {PRIVACY_SCREEN_DISABLED ,"Disabled" }, {PRIVACY_SCREEN_ENABLED ,"Enabled" },include/drm/drm_connector.h +2
-0@@ -1802,6 +1802,8 @@ int drm_connector_set_panel_orientation_with_quirk(struct drm_connector *connector, enum drm_panel_orientation panel_orientation, int width, int height); +int drm_connector_init_panel_orientation_property ( +struct drm_connector *connector);int drm_connector_attach_max_bpc_property (struct drm_connector *connector,int min,int max);void drm_connector_create_privacy_screen_properties (struct drm_connector *conn);
PATCH v10 2/4 drm/mediatek: init panel orientation property
In reply to Hsin-Yi WangInit panel orientation property after connector is initialized. Let the panel driver decides the orientation value later.
--- drivers/gpu/drm/mediatek/mtk_dsi.c | 7 +++++++ 1 file changed, 7 insertions(+)
drivers/gpu/drm/mediatek/mtk_dsi.c +7 -0
@@ -822,6 +822,13 @@ static int mtk_dsi_encoder_init(struct drm_device *drm, struct mtk_dsi *dsi) ret =PTR_ERR (dsi->connector); goto err_cleanup_encoder; } + + ret =drm_connector_init_panel_orientation_property (dsi->connector); +if (ret) { +DRM_ERROR ("Unable to init panel orientation\n" ); + goto err_cleanup_encoder; + } +drm_connector_attach_encoder (dsi->connector, &dsi->encoder);return 0 ;
Signature · 1 line
2.36.1.124.g0e6072fb45-goog
PATCH v10 3/4 drm/msm: init panel orientation property
In reply to Hsin-Yi WangInit panel orientation property after connector is initialized. Let the panel driver decides the orientation value later.
--- drivers/gpu/drm/msm/dsi/dsi_manager.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/gpu/drm/msm/dsi/dsi_manager.c +4 -0
@@ -669,6 +669,10 @@ struct drm_connector *msm_dsi_manager_connector_init(u8 id) connector->interlace_allowed =0 ; connector->doublescan_allowed =0 ; + ret =drm_connector_init_panel_orientation_property (connector); +if (ret) + goto fail; +drm_connector_attach_encoder (connector, msm_dsi->encoder); ret =msm_dsi_manager_panel_init (connector, id);
Signature · 1 line
2.36.1.124.g0e6072fb45-goog
PATCH v10 4/4 arm64: dts: mt8183: Add panel rotation
In reply to Hsin-Yi Wangkrane, kakadu, and kodama boards have a default panel rotation.
--- arch/arm64/boot/dts/mediatek/mt8183-kukui.dtsi | 1 + 1 file changed, 1 insertion(+)
arch/arm64/boot/dts/mediatek/mt8183-kukui.dtsi +1 -0
@@ -276,6 +276,7 @@ panel: panel@0 { avee-supply = <&ppvarp_lcd>; pp1800-supply = <&pp1800_lcd>; backlight = <&backlight_lcd0>; + rotation = <270>; port { panel_in: endpoint { remote-endpoint = <&dsi_out>;
Signature · 1 line
2.36.1.124.g0e6072fb45-goog
Patchwork
CI[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Separate panel orientation property creating and value setting (rev2)
In reply to Hsin-Yi Wang== Series Details ==
== Series Details ==
Series: Separate panel orientation property creating and value setting (rev2)
URL : https://patchwork.freedesktop.org/series/101530/
State : warning
== Summary ==
Error: dim checkpatch failedbf8654ee2da6 gpu: drm: separate panel orientation property creating and value setting -:130: WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#130: FILE: drivers/gpu/drm/drm_connector.c:2389:
+ * ^Icreate the connector's panel orientation property$
-:141: CHECK:OPEN_ENDED_LINE: Lines should not end with a '(' #141: FILE: drivers/gpu/drm/drm_connector.c:2400:
+int drm_connector_init_panel_orientation_property(
-:147: ERROR:SPACING: space required before the open parenthesis '(' #147: FILE: drivers/gpu/drm/drm_connector.c:2406:
+ if(dev->mode_config.panel_orientation_property)
-:151: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis #151: FILE: drivers/gpu/drm/drm_connector.c:2410:
+ prop = drm_property_create_enum(dev, DRM_MODE_PROP_IMMUTABLE,
+ "panel orientation",
-:176: CHECK:OPEN_ENDED_LINE: Lines should not end with a '(' #176: FILE: include/drm/drm_connector.h:1805:
+int drm_connector_init_panel_orientation_property(
total: 1 errors, 1 warnings, 3 checks, 99 lines checked fb63fbb19c0d drm/mediatek: init panel orientation property 24e07972d2f3 drm/msm: init panel orientation property 205b521cb9de arm64: dts: mt8183: Add panel rotation
Patchwork
CI[Intel-gfx] ✗ Fi.CI.SPARSE: warning for Separate panel orientation property creating and value setting (rev2)
In reply to Hsin-Yi Wang== Series Details ==
== Series Details ==
Series: Separate panel orientation property creating and value setting (rev2)
URL : https://patchwork.freedesktop.org/series/101530/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
Hi,
Quoted 6 lines · Hsin-Yi Wang
Some drivers, eg.
mtk_drmandmsm_drm, rely on the panel to set the orientation. Panel callsdrm_connector_set_panel_orientation()to create orientation property and sets the value. However, connector properties can't be created afterdrm_dev_register()is called. The goal is to separate the orientation property creation, so drm drivers can create it earlier beforedrm_dev_register().
Sorry for jumping in pretty late in the discussion (based on the v10 I seem to have missed this before).
This sounds to me like the real issue here is that drm_dev_register() is getting called too early?
To me it seems sensible to delay calling drm_dev_register() and thus allowing userspace to start detecting available displays + features until after the panel has been probed.
I see a devicetree patch in this series, so I guess that the panel is described in devicetree. Especially in the case of devicetree I would expect the kernel to have enough info to do the right thing and make sure the panel is probed before calling drm_dev_register() ?
Regards,
Hans
Quoted 21 lines
After this series,
drm_connector_set_panel_orientation()works like before. It won't affect existing callers ofdrm_connector_set_panel_orientation(). The only difference is that some drm drivers can calldrm_connector_init_panel_orientation_property()earlier.Hsin-Yi Wang (4):
gpu: drm: separate panel orientation property creating and value
setting
drm/mediatek: init panel orientation property drm/msm: init panel orientation property
arm64: dts: mt8183: Add panel rotation.../arm64/boot/dts/mediatek/mt8183-kukui.dtsi | 1 + drivers/gpu/drm/drm_connector.c | 58 ++++++++++++++----- drivers/gpu/drm/mediatek/mtk_dsi.c | 7 +++ drivers/gpu/drm/msm/dsi/dsi_manager.c | 4 ++ include/drm/drm_connector.h | 2 + 5 files changed, 59 insertions(+), 13 deletions(-)
Quoted 11 lines · Hans de Goede
Hi,
Quoted 6 lines · Hsin-Yi Wang
Some drivers, eg.
mtk_drmandmsm_drm, rely on the panel to set the orientation. Panel callsdrm_connector_set_panel_orientation()to create orientation property and sets the value. However, connector properties can't be created afterdrm_dev_register()is called. The goal is to separate the orientation property creation, so drm drivers can create it earlier beforedrm_dev_register().
Quoted 6 lines
Sorry for jumping in pretty late in the discussion (based on the v10 I seem to have missed this before).
This sounds to me like the real issue here is that
drm_dev_register()is getting called too early?
Right.
Quoted 4 lines
To me it seems sensible to delay calling
drm_dev_register()and thus allowing userspace to start detecting available displays + features until after the panel has been probed.
Most panels set this value very late, in .get_modes callback (since it is when the connector is known), though the value was known during panel probe.
I think we can also let drm check if they have remote panel nodes: If there is a panel and the panel sets the orientation, let the drm read this value and set the property. Does this workflow sound reasonable?
The corresponding patch to implement this:
https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/
Thanks
Quoted 35 lines
I see a devicetree patch in this series, so I guess that the panel is described in devicetree. Especially in the case of devicetree I would expect the kernel to have enough info to do the right thing and make sure the panel is probed before calling
drm_dev_register()?Regards,
Hans
Quoted 21 lines
After this series,
drm_connector_set_panel_orientation()works like before. It won't affect existing callers ofdrm_connector_set_panel_orientation(). The only difference is that some drm drivers can calldrm_connector_init_panel_orientation_property()earlier.Hsin-Yi Wang (4):
gpu: drm: separate panel orientation property creating and value
setting
drm/mediatek: init panel orientation property drm/msm: init panel orientation property
arm64: dts: mt8183: Add panel rotation.../arm64/boot/dts/mediatek/mt8183-kukui.dtsi | 1 + drivers/gpu/drm/drm_connector.c | 58 ++++++++++++++----- drivers/gpu/drm/mediatek/mtk_dsi.c | 7 +++ drivers/gpu/drm/msm/dsi/dsi_manager.c | 4 ++ include/drm/drm_connector.h | 2 + 5 files changed, 59 insertions(+), 13 deletions(-)
Hi,
Quoted 20 lines · Hsin-Yi Wang
Quoted 11 lines · Hans de Goede
Hi,
Quoted 6 lines · Hsin-Yi Wang
Some drivers, eg.
mtk_drmandmsm_drm, rely on the panel to set the orientation. Panel callsdrm_connector_set_panel_orientation()to create orientation property and sets the value. However, connector properties can't be created afterdrm_dev_register()is called. The goal is to separate the orientation property creation, so drm drivers can create it earlier beforedrm_dev_register().Quoted 6 lines
Sorry for jumping in pretty late in the discussion (based on the v10 I seem to have missed this before).
This sounds to me like the real issue here is that
drm_dev_register()is getting called too early?Right.
Quoted 8 lines
Quoted 4 lines
To me it seems sensible to delay calling
drm_dev_register()and thus allowing userspace to start detecting available displays + features until after the panel has been probed.Most panels set this value very late, in .get_modes callback (since it is when the connector is known), though the value was known during panel probe.
Hmm I would expect the main drm/kms driver to register the drm_connector object after probing the panel, right ?
So maybe this is a problem with the panel API? How about adding separate callback to the panel API to get the orientation, which the main drm/kms driver can then call before registering the connector ?
And then have the main drm/kms driver call drm_connector_set_panel_orientation() with the returned orientation on the connecter before registering it.
The new get_orientation callback for the panel should of course be optional (IOW amy be NULL), so we probably want a small helper for drivers using panel (sub)drivers to take care of the process of getting the panel orientation from the panel (if supported) and then setting it on the connector.
Quoted 6 lines
I think we can also let drm check if they have remote panel nodes: If there is a panel and the panel sets the orientation, let the drm read this value and set the property. Does this workflow sound reasonable?
The corresponding patch to implement this:
https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/
That is a suprisingly small patch (which is good). I guess that my suggestion to add a new panel driver callback to get the orientation would be a bit bigget then this. Still I think that that would be a bit cleaner, as it would also solve this for cases where the orientation comes from the panel itself (through say some EDID extenstion) rather then from devicetree.
Still I think either way should be acceptable upstream.
Opinions from other drm devs on the above are very much welcome!
Your small patch nicely avoids the probe ordering problem, so it is much better then this patch series.
Regards,
Hans
Quoted 39 lines
Thanks
Quoted 35 lines
I see a devicetree patch in this series, so I guess that the panel is described in devicetree. Especially in the case of devicetree I would expect the kernel to have enough info to do the right thing and make sure the panel is probed before calling
drm_dev_register()?Regards,
Hans
Quoted 21 lines
After this series,
drm_connector_set_panel_orientation()works like before. It won't affect existing callers ofdrm_connector_set_panel_orientation(). The only difference is that some drm drivers can calldrm_connector_init_panel_orientation_property()earlier.Hsin-Yi Wang (4):
gpu: drm: separate panel orientation property creating and value
setting
drm/mediatek: init panel orientation property drm/msm: init panel orientation property
arm64: dts: mt8183: Add panel rotation.../arm64/boot/dts/mediatek/mt8183-kukui.dtsi | 1 + drivers/gpu/drm/drm_connector.c | 58 ++++++++++++++----- drivers/gpu/drm/mediatek/mtk_dsi.c | 7 +++ drivers/gpu/drm/msm/dsi/dsi_manager.c | 4 ++ include/drm/drm_connector.h | 2 + 5 files changed, 59 insertions(+), 13 deletions(-)
Quoted 44 lines · Hans de Goede
Hi,
Quoted 20 lines · Hsin-Yi Wang
Quoted 11 lines · Hans de Goede
Hi,
Quoted 6 lines · Hsin-Yi Wang
Some drivers, eg.
mtk_drmandmsm_drm, rely on the panel to set the orientation. Panel callsdrm_connector_set_panel_orientation()to create orientation property and sets the value. However, connector properties can't be created afterdrm_dev_register()is called. The goal is to separate the orientation property creation, so drm drivers can create it earlier beforedrm_dev_register().Quoted 6 lines
Sorry for jumping in pretty late in the discussion (based on the v10 I seem to have missed this before).
This sounds to me like the real issue here is that
drm_dev_register()is getting called too early?Right.
Quoted 8 lines
Quoted 4 lines
To me it seems sensible to delay calling
drm_dev_register()and thus allowing userspace to start detecting available displays + features until after the panel has been probed.Most panels set this value very late, in .get_modes callback (since it is when the connector is known), though the value was known during panel probe.
Hmm I would expect the main drm/kms driver to register the
drm_connectorobject after probing the panel, right ?So maybe this is a problem with the panel API? How about adding separate callback to the panel API to get the orientation, which the main drm/kms driver can then call before registering the connector ?
And then have the main drm/kms driver call
drm_connector_set_panel_orientation()with the returned orientation on the connecter before registering it.
Quoted 6 lines
The new
get_orientationcallback for the panel should of course be optional (IOW amy be NULL), so we probably want a small helper for drivers using panel (sub)drivers to take care of the process of getting the panel orientation from the panel (if supported) and then setting it on the connector.
Hi Hans,
Thanks for the suggestion. I've sent a new version for this:
https://patchwork.kernel.org/project/dri-devel/patch/[email protected]/
Panel can implement the optional callback to return the orientation property, while drm/kms driver will call a drm API to get the value then they can call drm_connector_set_panel_orientation(). Panel .get_mode will still call drm_connector_set_panel_orientation() but now it will be a no-op as the value was set by drm/kms driver previously.
This is similar to the small patch below:
https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/
But it's now using the panel API.
Quoted 68 lines
Quoted 7 lines
I think we can also let drm check if they have remote panel nodes: If there is a panel and the panel sets the orientation, let the drm read this value and set the property. Does this workflow sound reasonable?
The corresponding patch to implement this:
https://patchwork.kernel.org/project/linux-mediatek/patch/[email protected]/That is a suprisingly small patch (which is good). I guess that my suggestion to add a new panel driver callback to get the orientation would be a bit bigget then this. Still I think that that would be a bit cleaner, as it would also solve this for cases where the orientation comes from the panel itself (through say some EDID extenstion) rather then from devicetree.
Still I think either way should be acceptable upstream.
Opinions from other drm devs on the above are very much welcome!
Your small patch nicely avoids the probe ordering problem, so it is much better then this patch series.
Regards,
Hans
Quoted 39 lines
Thanks
Quoted 35 lines
I see a devicetree patch in this series, so I guess that the panel is described in devicetree. Especially in the case of devicetree I would expect the kernel to have enough info to do the right thing and make sure the panel is probed before calling
drm_dev_register()?Regards,
Hans
Quoted 21 lines
After this series,
drm_connector_set_panel_orientation()works like before. It won't affect existing callers ofdrm_connector_set_panel_orientation(). The only difference is that some drm drivers can calldrm_connector_init_panel_orientation_property()earlier.Hsin-Yi Wang (4):
gpu: drm: separate panel orientation property creating and value
setting
drm/mediatek: init panel orientation property drm/msm: init panel orientation property
arm64: dts: mt8183: Add panel rotation.../arm64/boot/dts/mediatek/mt8183-kukui.dtsi | 1 + drivers/gpu/drm/drm_connector.c | 58 ++++++++++++++----- drivers/gpu/drm/mediatek/mtk_dsi.c | 7 +++ drivers/gpu/drm/msm/dsi/dsi_manager.c | 4 ++ include/drm/drm_connector.h | 2 + 5 files changed, 59 insertions(+), 13 deletions(-)
Patchwork
CI[Intel-gfx] ✗ Fi.CI.BAT: failure for Separate panel orientation property creating and value setting (rev2)
In reply to Hsin-Yi Wang== Series Details ==
== Series Details ==
Series: Separate panel orientation property creating and value setting (rev2)
URL : https://patchwork.freedesktop.org/series/101530/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11705 -> Patchwork_101530v2
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_101530v2 absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_101530v2, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/index.html
Participating hosts (42 -> 46)
------------------------------
Additional (4): bat-dg2-8 fi-rkl-11600 fi-bsw-nick fi-tgl-u2
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_101530v2:
### IGT changes ###
#### Possible regressions ####
* igt@prime_self_import@basic-with_one_bo_two_files:
- fi-kbl-soraka: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11705/fi-kbl-soraka/igt@prime_self_import@basic-with_one_bo_two_files.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-kbl-soraka/igt@prime_self_import@basic-with_one_bo_two_files.html
Known issues
------------
Here are the changes found in Patchwork_101530v2 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_huc_copy@huc-copy:
- fi-tgl-u2: NOTRUN -> [SKIP][3] ([i915#2190])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-tgl-u2/igt@[email protected]
- fi-rkl-11600: NOTRUN -> [SKIP][4] ([i915#2190])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-rkl-11600/igt@[email protected]
* igt@gem_lmem_swapping@basic:
- fi-rkl-11600: NOTRUN -> [SKIP][5] ([i915#4613]) +3 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-rkl-11600/igt@[email protected]
* igt@gem_lmem_swapping@parallel-random-engines:
- fi-bsw-nick: NOTRUN -> [SKIP][6] ([fdo#109271]) +48 similar issues
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-bsw-nick/igt@[email protected]
* igt@gem_tiled_pread_basic:
- fi-rkl-11600: NOTRUN -> [SKIP][7] ([i915#3282])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-rkl-11600/igt@gem_tiled_pread_basic.html
* igt@i915_pm_backlight@basic-brightness:
- fi-rkl-11600: NOTRUN -> [SKIP][8] ([i915#3012])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-rkl-11600/igt@[email protected]
* igt@i915_selftest@live@gem:
- fi-blb-e6850: NOTRUN -> [DMESG-FAIL][9] ([i915#4528])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-blb-e6850/igt@i915_selftest@[email protected]
* igt@i915_selftest@live@hangcheck:
- bat-dg1-6: [PASS][10] -> [DMESG-FAIL][11] ([i915#4494] / [i915#4957])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11705/bat-dg1-6/igt@i915_selftest@[email protected]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/bat-dg1-6/igt@i915_selftest@[email protected]
* igt@i915_suspend@basic-s2idle-without-i915:
- fi-bdw-gvtdvm: NOTRUN -> [INCOMPLETE][12] ([i915#4817])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-bdw-gvtdvm/igt@[email protected]
* igt@i915_suspend@basic-s3-without-i915:
- fi-rkl-11600: NOTRUN -> [INCOMPLETE][13] ([i915#5982])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-rkl-11600/igt@[email protected]
* igt@kms_chamelium@hdmi-edid-read:
- fi-tgl-u2: NOTRUN -> [SKIP][14] ([fdo#109284] / [fdo#111827]) +7 similar issues
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-tgl-u2/igt@[email protected]
- fi-rkl-11600: NOTRUN -> [SKIP][15] ([fdo#111827]) +7 similar issues
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-rkl-11600/igt@[email protected]
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-bsw-nick: NOTRUN -> [SKIP][16] ([fdo#109271] / [fdo#111827]) +8 similar issues
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-bsw-nick/igt@[email protected]
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy:
- fi-tgl-u2: NOTRUN -> [SKIP][17] ([i915#4103]) +1 similar issue
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-tgl-u2/igt@[email protected]
- fi-rkl-11600: NOTRUN -> [SKIP][18] ([i915#4070] / [i915#4103]) +1 similar issue
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-rkl-11600/igt@[email protected]
* igt@kms_flip@basic-flip-vs-modeset@a-edp1:
- fi-tgl-u2: NOTRUN -> [DMESG-WARN][19] ([i915#402]) +2 similar issues
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-tgl-u2/igt@kms_flip@[email protected]
* igt@kms_flip@basic-flip-vs-modeset@b-edp1:
- bat-adlp-4: [PASS][20] -> [DMESG-WARN][21] ([i915#3576]) +1 similar issue
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11705/bat-adlp-4/igt@kms_flip@[email protected]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/bat-adlp-4/igt@kms_flip@[email protected]
* igt@kms_force_connector_basic@force-load-detect:
- fi-tgl-u2: NOTRUN -> [SKIP][22] ([fdo#109285])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-tgl-u2/igt@[email protected]
- fi-rkl-11600: NOTRUN -> [SKIP][23] ([fdo#109285] / [i915#4098])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-rkl-11600/igt@[email protected]
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
- fi-rkl-11600: NOTRUN -> [SKIP][24] ([i915#4070] / [i915#533])
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-rkl-11600/igt@[email protected]
* igt@kms_psr@primary_page_flip:
- fi-rkl-11600: NOTRUN -> [SKIP][25] ([i915#1072]) +3 similar issues
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-rkl-11600/igt@kms_psr@primary_page_flip.html
* igt@kms_setmode@basic-clone-single-crtc:
- fi-rkl-11600: NOTRUN -> [SKIP][26] ([i915#3555] / [i915#4098])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-rkl-11600/igt@[email protected]
- fi-tgl-u2: NOTRUN -> [SKIP][27] ([i915#3555])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-tgl-u2/igt@[email protected]
* igt@prime_vgem@basic-read:
- fi-rkl-11600: NOTRUN -> [SKIP][28] ([fdo#109295] / [i915#3291] / [i915#3708]) +2 similar issues
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-rkl-11600/igt@[email protected]
* igt@prime_vgem@basic-userptr:
- fi-tgl-u2: NOTRUN -> [SKIP][29] ([fdo#109295] / [i915#3301])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-tgl-u2/igt@[email protected]
- fi-rkl-11600: NOTRUN -> [SKIP][30] ([fdo#109295] / [i915#3301] / [i915#3708])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-rkl-11600/igt@[email protected]
#### Possible fixes ####
* igt@i915_selftest@live@coherency:
- {bat-dg2-9}: [DMESG-WARN][31] ([i915#5763]) -> [PASS][32] +5 similar issues
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11705/bat-dg2-9/igt@i915_selftest@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/bat-dg2-9/igt@i915_selftest@[email protected]
* igt@i915_selftest@live@execlists:
- fi-bdw-gvtdvm: [INCOMPLETE][33] ([i915#2940] / [i915#5801]) -> [PASS][34]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11705/fi-bdw-gvtdvm/igt@i915_selftest@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-bdw-gvtdvm/igt@i915_selftest@[email protected]
* igt@i915_selftest@live@requests:
- fi-blb-e6850: [DMESG-FAIL][35] ([i915#4528]) -> [PASS][36]
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11705/fi-blb-e6850/igt@i915_selftest@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/fi-blb-e6850/igt@i915_selftest@[email protected]
* igt@kms_busy@basic@flip:
- bat-adlp-4: [DMESG-WARN][37] ([i915#3576]) -> [PASS][38] +1 similar issue
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11705/bat-adlp-4/igt@kms_busy@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/bat-adlp-4/igt@kms_busy@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109284]: https://bugs.freedesktop.org/show_bug.cgi?id=109284
[fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
[fdo#109295]: https://bugs.freedesktop.org/show_bug.cgi?id=109295
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2575]: https://gitlab.freedesktop.org/drm/intel/issues/2575
[i915#2582]: https://gitlab.freedesktop.org/drm/intel/issues/2582
[i915#2940]: https://gitlab.freedesktop.org/drm/intel/issues/2940
[i915#3012]: https://gitlab.freedesktop.org/drm/intel/issues/3012
[i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282
[i915#3291]: https://gitlab.freedesktop.org/drm/intel/issues/3291
[i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3576]: https://gitlab.freedesktop.org/drm/intel/issues/3576
[i915#3708]: https://gitlab.freedesktop.org/drm/intel/issues/3708
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#4070]: https://gitlab.freedesktop.org/drm/intel/issues/4070
[i915#4098]: https://gitlab.freedesktop.org/drm/intel/issues/4098
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4494]: https://gitlab.freedesktop.org/drm/intel/issues/4494
[i915#4528]: https://gitlab.freedesktop.org/drm/intel/issues/4528
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4817]: https://gitlab.freedesktop.org/drm/intel/issues/4817
[i915#4957]: https://gitlab.freedesktop.org/drm/intel/issues/4957
[i915#5122]: https://gitlab.freedesktop.org/drm/intel/issues/5122
[i915#5171]: https://gitlab.freedesktop.org/drm/intel/issues/5171
[i915#5174]: https://gitlab.freedesktop.org/drm/intel/issues/5174
[i915#5181]: https://gitlab.freedesktop.org/drm/intel/issues/5181
[i915#5190]: https://gitlab.freedesktop.org/drm/intel/issues/5190
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#5606]: https://gitlab.freedesktop.org/drm/intel/issues/5606
[i915#5703]: https://gitlab.freedesktop.org/drm/intel/issues/5703
[i915#5763]: https://gitlab.freedesktop.org/drm/intel/issues/5763
[i915#5775]: https://gitlab.freedesktop.org/drm/intel/issues/5775
[i915#5801]: https://gitlab.freedesktop.org/drm/intel/issues/5801
[i915#5903]: https://gitlab.freedesktop.org/drm/intel/issues/5903
[i915#5982]: https://gitlab.freedesktop.org/drm/intel/issues/5982
Build changes
-------------
* Linux: CI_DRM_11705 -> Patchwork_101530v2
CI-20190529: 20190529
CI_DRM_11705: 18a2e6dbca526f996da04741cf5ef169e810a50e @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6495: 7e2033da45f024a0348e6034fcb7f70a91b80ee9 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_101530v2: 18a2e6dbca526f996da04741cf5ef169e810a50e @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
01d561b9bb95 arm64: dts: mt8183: Add panel rotation21530cae4fa3 drm/msm: init panel orientation propertya026c392838a drm/mediatek: init panel orientation propertyd1faead57b36 gpu: drm: separate panel orientation property creating and value setting
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_101530v2/index.html