All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Jackson <ajax@redhat.com>
To: ville.syrjala@linux.intel.com
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/edid: Add CEA modes before inferred modes
Date: Tue, 12 May 2015 12:18:53 -0400	[thread overview]
Message-ID: <1431447533.24748.0.camel@redhat.com> (raw)
In-Reply-To: <1431096307-20966-1-git-send-email-ville.syrjala@linux.intel.com>

On Fri, 2015-05-08 at 17:45 +0300, ville.syrjala@linux.intel.com wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> Currently we're adding CEA modes after the inferred modes, which 
> means
> we might get multiple modes that are very close to each other, but
> slightly different, which seems a bit silly. That's because duplicate
> mode check that occurs when adding inferred modes would not consider
> CEA modes as potential duplicates. Reverse the order so that CEA
> modes get added before inferred modes, and are thus considered 
> potential
> duplicates.
> 
> Or as ajax put it on irc:
> "< ajax> the point of the "pick a timing formula" heuristic was to
> generate something the sink could _likely_ sink.  if it tells us
> timings it can sink explicitly then second-guessing seems dumb."
> 
> Cc: Adam Jackson <ajax@redhat.com>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

Reviewed-by: Adam Jackson <ajax@redhat.com>

- ajax
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

      parent reply	other threads:[~2015-05-12 16:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08 14:45 [PATCH] drm/edid: Add CEA modes before inferred modes ville.syrjala
2015-05-11  9:24 ` Daniel Vetter
2015-05-12 16:18 ` Adam Jackson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1431447533.24748.0.camel@redhat.com \
    --to=ajax@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ville.syrjala@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.