mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-28 10:41:38 -04:00
drm: Perform basic sanity checks on probed modes
Make sure the timings of probed modes at least pass some very basic sanity checks. The checks include: - clock,hdisplay,vdisplay are non zero - sync pulse fits within the blanking period - htotal,vtotal are big enough I have not checked all the drivers to see if the modes the generate might violate these constraints. I'm hoping not, because that would mean either abandoning the idea of doing this from the core code, or fixing the drivers. I'm not entirely sure about limiting the sync pulse to the blanking period. Intel hardware doesn't support such things, but some other hardware might. However at least HDMI doesn't allow having sync pulse edges within the active period, so I'm thinking the check is probably OK to have in the common code. Signed-off-by: Ville Syrjälä <[email protected]> Reviewed-by: Alex Deucher <[email protected]> Signed-off-by: Daniel Vetter <[email protected]>
This commit is contained in:
parent
05acaec334
commit
abc0b1447d
3 changed files with 37 additions and 1 deletions
|
|
@ -217,6 +217,7 @@ bool drm_mode_equal_no_clocks_no_stereo(const struct drm_display_mode *mode1,
|
|||
const struct drm_display_mode *mode2);
|
||||
|
||||
/* for use by the crtc helper probe functions */
|
||||
enum drm_mode_status drm_mode_validate_basic(const struct drm_display_mode *mode);
|
||||
enum drm_mode_status drm_mode_validate_size(const struct drm_display_mode *mode,
|
||||
int maxX, int maxY);
|
||||
void drm_mode_prune_invalid(struct drm_device *dev,
|
||||
|
|
|
|||
Loading…
Reference in a new issue