On Thu, May 28, 2015 at 07:19:51PM +0100, Damien Lespiau wrote: > On Fri, May 22, 2015 at 11:22:34AM +0300, Mika Kahola wrote: > > From: Ville Syrjälä <ville.syrjala@xxxxxxxxxxxxxxx> > > > > Print a warning if we fall through the .get_display_clock_speed() function > > pointer setup. We end up assuming a 133MHz cdclk which should mean that > > at least we avoid any 0 deivisions and whatnot. But this could at least > > help remind people that they have to provide this function for new platforms. > > > > Signed-off-by: Ville Syrjälä <ville.syrjala@xxxxxxxxxxxxxxx> > > > > v2: Rebased to the latest > > v3: Rebased to the latest > > > > Reviewed-by: Mika Kahola <mika.kahola@xxxxxxxxx> > > Reviewed-by: Damien Lespiau <damien.lespiau@xxxxxxxxx> Merged up to this one here, with the sob section of commit messages aligned to what we usually do. Thanks, Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
