Hi Boris, Am Donnerstag, den 26.02.2015, 14:51 +0100 schrieb Boris Brezillon: > Hi Philipp, > > On Mon, 23 Feb 2015 15:04:32 +0100 > Philipp Zabel <p.zabel at pengutronix.de> wrote: > > > Hi Thierry, > > > > do you have any further thoughts on this? > > > > Am Dienstag, den 03.02.2015, 14:30 +0100 schrieb Thierry Reding: > > > On Thu, Dec 11, 2014 at 06:32:44PM +0100, Philipp Zabel wrote: > > > > Many panel data sheets additionally to typical values list allowed > > > > ranges for > > > > timings such as hsync/vsync lengths, porches, and the pixel clock rate. > > > > These > > > > can be stored in a struct display_timing, to be used by an encoder > > > > mode_fixup > > > > callback to clamp user provided timing values or to validate > > > > workarounds for > > > > clock source limitations. > > > > > > > > This patch adds a new drm_panel_funcs callback that returns the panels' > > > > available display_timing entries. > > Anthony recently noticed that the edt_etm0700g0dh6 panel he's > connecting on his sama5 board defines typical timings that are not > supported by Atmel's display controller. > This patch could help us deal with such cases. > Could you keep me (and Anthony) in Cc of your future versions ?
Will do. regards Philipp
