dt-bindings: display/ti: Add optional property to set memory bandwidth limit

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 <[e-mail]>
Acked-by: Rob Herring <[e-mail]>
Signed-off-by: Tomi Valkeinen <[e-mail]>

Documentation/devicetree/bindings/display/ti/ti,dra7-dss.txt

···
 - 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
+
+
 HDMI
 ----
 

Documentation/devicetree/bindings/display/ti/ti,omap2-dss.txt

···
 - ti,hwmods: "dss_dispc"
 - interrupts: the DISPC interrupt
 
+Optional properties:
+- max-memory-bandwidth: Input memory (from main memory to dispc) bandwidth limit
+			in bytes per second
+
 
 RFBI
 ----

Documentation/devicetree/bindings/display/ti/ti,omap3-dss.txt

···
 - 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
+
 
 RFBI
 ----

Documentation/devicetree/bindings/display/ti/ti,omap4-dss.txt

···
 - 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
+
 
 RFBI
 ----

Documentation/devicetree/bindings/display/ti/ti,omap5-dss.txt

···
 - 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
+
 
 RFBI
 ----