On Fri, Oct 20, 2017 at 04:12:56PM +0300, Peter Ujfalusi wrote: > max-memory-bandwidth can be used to specify the maximum bandwidth dispc > can use when reading display data from main memory. > > In some SoC (am437x for example) we have memory bandwidth limitation > which causes underflow in the display subsystem. > > Signed-off-by: Peter Ujfalusi <peter.ujfalusi@xxxxxx> > --- > Documentation/devicetree/bindings/display/ti/ti,dra7-dss.txt | 5 +++++ > Documentation/devicetree/bindings/display/ti/ti,omap2-dss.txt | 4 ++++ > Documentation/devicetree/bindings/display/ti/ti,omap3-dss.txt | 4 ++++ > Documentation/devicetree/bindings/display/ti/ti,omap4-dss.txt | 4 ++++ > Documentation/devicetree/bindings/display/ti/ti,omap5-dss.txt | 4 ++++ > 5 files changed, 21 insertions(+) > > diff --git a/Documentation/devicetree/bindings/display/ti/ti,dra7-dss.txt b/Documentation/devicetree/bindings/display/ti/ti,dra7-dss.txt > index c30f9ec189ed..91279f1060fe 100644 > --- a/Documentation/devicetree/bindings/display/ti/ti,dra7-dss.txt > +++ b/Documentation/devicetree/bindings/display/ti/ti,dra7-dss.txt > @@ -47,6 +47,11 @@ Required properties: > - clocks: handle to fclk > - clock-names: "fck" > > +Optional properties: > +- max-memory-bandwidth: Input memory (from main memory to dispc) bandwidth limit > + in bytes per second Can we move this to a common location since we already have the same prop for ARM pl11x. Rob -- 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
