From: Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>
To: <robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<michal.simek@amd.com>, <deller@gmx.de>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-fbdev@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>, <git@amd.com>,
Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>
Subject: [PATCH 2/2] dt-bindings: xilinx: Remove description for framebuffer IP
Date: Fri, 6 Nov 2026 22:39:02 +0530 [thread overview]
Message-ID: <20261106170902.3656809-3-radhey.shyam.pandey@amd.com> (raw)
In-Reply-To: <20261106170902.3656809-1-radhey.shyam.pandey@amd.com>
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 <radhey.shyam.pandey@amd.com>
---
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
next prev parent reply other threads:[~2026-11-06 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 17:09 [PATCH 0/2] fbdev: remove the Xilinx framebuffer driver Radhey Shyam Pandey
2026-11-06 17:09 ` [PATCH 1/2] fbdev: xilinxfb: remove the driver Radhey Shyam Pandey
2026-11-06 17:09 ` Radhey Shyam Pandey [this message]
2026-11-09 7:29 ` [PATCH 0/2] fbdev: remove the Xilinx framebuffer driver Michal Simek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261106170902.3656809-3-radhey.shyam.pandey@amd.com \
--to=radhey.shyam.pandey@amd.com \
--cc=conor+dt@kernel.org \
--cc=deller@gmx.de \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=git@amd.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®