The Xilinx framebuffer IP relies on Xilinx Platform Studio and the ISE Design Suite, both of which were discontinued years ago.
Driver support for the controller is removed by the preceding patch. Keep the bindings in sync by removing the corresponding Xilinx framebuffer description. Signed-off-by: Radhey Shyam Pandey <[email protected]> --- Documentation/devicetree/bindings/xilinx.txt | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/Documentation/devicetree/bindings/xilinx.txt b/Documentation/devicetree/bindings/xilinx.txt index a1a2cde7b7d8..935700073216 100644 --- a/Documentation/devicetree/bindings/xilinx.txt +++ b/Documentation/devicetree/bindings/xilinx.txt @@ -1,18 +1,5 @@ Bindings for specific devices: - i) Xilinx ML300 Framebuffer - - Simple framebuffer device from the ML300 reference design (also on the - ML403 reference design as well as others). - - Optional properties: - - resolution = <xres yres> : pixel resolution of framebuffer. Some - implementations use a different resolution. - Default is <d#640 d#480> - - virt-resolution = <xvirt yvirt> : Size of framebuffer in memory. - Default is <d#1024 d#480>. - - rotate-display (empty) : rotate display 180 degrees. - v) Xilinx hwicap Xilinx hwicap devices provide access to the configuration logic -- 2.44.4
