Commit 1915d7fa authored by Tomi Valkeinen's avatar Tomi Valkeinen

drm/omap: fix maximum sizes

We define max width and height in mode_config to 2048. These maximums
affect many things, which are independent and depend on platform. We
need to do more fine grained checks in the code paths for each
component, and so the maximum values in mode_config should just be "big
enough" to cover all use cases.

Change the maximum width & height to 8192.
Signed-off-by: default avatarTomi Valkeinen <tomi.valkeinen@ti.com>
parent 7c009851
...@@ -310,11 +310,14 @@ static int omap_modeset_init(struct drm_device *dev) ...@@ -310,11 +310,14 @@ static int omap_modeset_init(struct drm_device *dev)
dev->mode_config.min_width = 8; dev->mode_config.min_width = 8;
dev->mode_config.min_height = 2; dev->mode_config.min_height = 2;
/* note: eventually will need some cpu_is_omapXYZ() type stuff here /*
* to fill in these limits properly on different OMAP generations.. * Note: these values are used for multiple independent things:
* connector mode filtering, buffer sizes, crtc sizes...
* Use big enough values here to cover all use cases, and do more
* specific checking in the respective code paths.
*/ */
dev->mode_config.max_width = 2048; dev->mode_config.max_width = 8192;
dev->mode_config.max_height = 2048; dev->mode_config.max_height = 8192;
dev->mode_config.funcs = &omap_mode_config_funcs; dev->mode_config.funcs = &omap_mode_config_funcs;
dev->mode_config.helper_private = &omap_mode_config_helper_funcs; dev->mode_config.helper_private = &omap_mode_config_helper_funcs;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment