Skip to content

Commit

Permalink
drm/edid: Do drm_dmt_modes_for_range() for all range descriptor types
Browse files Browse the repository at this point in the history
EDID 1.4 retcons the meaning of the "GTF feature" bit to mean "is
continuous frequency", and moves the set of supported timing formulas
into the range descriptor itself.  In any event, the range descriptor
can act as a filter on the DMT list without regard to a specific timing
formula.

Signed-off-by: Adam Jackson <ajax@redhat.com>
Tested-by: Takashi Iwai <tiwai@suse.de>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
  • Loading branch information
Adam Jackson authored and Dave Airlie committed Apr 20, 2012
1 parent 6201ee3 commit cb21aaf
Showing 1 changed file with 6 additions and 5 deletions.
11 changes: 6 additions & 5 deletions drivers/gpu/drm/drm_edid.c
Original file line number Diff line number Diff line change
Expand Up @@ -1042,12 +1042,13 @@ do_inferred_modes(struct detailed_timing *timing, void *c)
{
struct detailed_mode_closure *closure = c;
struct detailed_non_pixel *data = &timing->data.other_data;
int gtf = (closure->edid->features & DRM_EDID_FEATURE_DEFAULT_GTF);

if (gtf && data->type == EDID_DETAIL_MONITOR_RANGE)
closure->modes += drm_dmt_modes_for_range(closure->connector,
closure->edid,
timing);
if (data->type != EDID_DETAIL_MONITOR_RANGE)
return;

closure->modes += drm_dmt_modes_for_range(closure->connector,
closure->edid,
timing);
}

static int
Expand Down

0 comments on commit cb21aaf

Please sign in to comment.