On 30/11/17 14:12, Peter Ujfalusi wrote: > Hi, > > Changes since v2: > - Rebased on drm-next (v2 was based on drm-next and my > 'drm/omap: Module parameter for display order configuration' series, thus it > was not applying cleanly. > - Added Acked-by from Rob to the dt-binding changes > > Changes since v1: > - Use the crtc->mode_valid and not connector->mode_valid as the limit is really > posed by the 'crtc' (DISPC) > - Bandwidth calculation changed: do the calculation in place + extended comment > - looked for better place to document the max-memory-bandwidth, but > can not find any suitable document. Creating a new txt file for only one > property did not seemed feasable. > > This series will add simple memory bandwidth limit support to reject modes > which, if used with one plane in full size would fail the limit. > > Regards, > Peter > --- > Peter Ujfalusi (3): > dt-bindings: display/ti: Add optional property to set memory bandwidth > limit > drm/omap: dss: Add support for reporting memory bandwidth limitation > drm/omap: Filter displays mode based on bandwidth limit > > .../devicetree/bindings/display/ti/ti,dra7-dss.txt | 5 +++ > .../bindings/display/ti/ti,omap2-dss.txt | 4 +++ > .../bindings/display/ti/ti,omap3-dss.txt | 4 +++ > .../bindings/display/ti/ti,omap4-dss.txt | 4 +++ > .../bindings/display/ti/ti,omap5-dss.txt | 4 +++ > drivers/gpu/drm/omapdrm/dss/dispc.c | 13 ++++++++ > drivers/gpu/drm/omapdrm/dss/omapdss.h | 2 ++ > drivers/gpu/drm/omapdrm/omap_crtc.c | 37 ++++++++++++++++++++++ > drivers/gpu/drm/omapdrm/omap_drv.c | 5 +++ > drivers/gpu/drm/omapdrm/omap_drv.h | 3 ++ > 10 files changed, 81 insertions(+) > Thanks, I have applied this series. Tomi -- Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
