On Mon, Nov 30, 2015 at 01:02:59PM -0500, Adam Jackson wrote:
> On Thu, 2015-11-26 at 19:01 +0200, Ville Syrjälä wrote:
> > On Mon, Nov 16, 2015 at 09:05:12PM +0200, ville.syrjala at linux.intel.com
> > wrote:
> > > From: Ville Syrjälä
> > >
> > > Rather than using drm_match_cea_mode() to
On Thu, 2015-11-26 at 19:01 +0200, Ville Syrjälä wrote:
> On Mon, Nov 16, 2015 at 09:05:12PM +0200, ville.syrjala at linux.intel.com
> wrote:
> > From: Ville Syrjälä
> >
> > Rather than using drm_match_cea_mode() to see if the EDID detailed
> > timings are supposed to represent one of the
On Mon, Nov 16, 2015 at 09:05:12PM +0200, ville.syrjala at linux.intel.com
wrote:
> From: Ville Syrjälä
>
> Rather than using drm_match_cea_mode() to see if the EDID detailed
> timings are supposed to represent one of the CEA/HDMI modes, add a
> special version of that function that takes in
From: Ville Syrjälä
Rather than using drm_match_cea_mode() to see if the EDID detailed
timings are supposed to represent one of the CEA/HDMI modes, add a
special version of that function that takes in an explicit clock
tolerance value (in kHz). When looking at