On Fri, Oct 30, 2026 at 04:37:35PM +0800, Adam Azuddin wrote: > The RA8875 is an SPI-connected TFT display controller by RAiO > Technology Inc. It supports display resolutions of up to 800x480. > > Assisted-by: LLM
You can drop this. > Signed-off-by: Adam Azuddin <[email protected]> > --- > .../bindings/display/panel/raio,ra8875.yaml | 87 +++++++++++++++++++ > .../devicetree/bindings/vendor-prefixes.yaml | 2 + > 2 files changed, 89 insertions(+) > create mode 100644 > Documentation/devicetree/bindings/display/panel/raio,ra8875.yaml > > diff --git a/Documentation/devicetree/bindings/display/panel/raio,ra8875.yaml > b/Documentation/devicetree/bindings/display/panel/raio,ra8875.yaml > new file mode 100644 > index 000000000000..661398bda0ee > --- /dev/null > +++ b/Documentation/devicetree/bindings/display/panel/raio,ra8875.yaml > @@ -0,0 +1,87 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/display/panel/raio,ra8875.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: RAiO RA8875 Display Controller > + > +maintainers: > + - Adam Azuddin <[email protected]> > + > +description: > + The RA8875 is a TFT LCD controller for panels up to 800x480 pixels. > + It can be connected to the host via 8080/6800 parallel interface, > + SPI or I2C. > + > +allOf: > + - $ref: panel-common.yaml# > + - $ref: /schemas/spi/spi-peripheral-props.yaml# > + > +properties: > + compatible: > + const: raio,ra8875 > + > + reg: > + maxItems: 1 > + > + vdd-supply: > + description: > + 3.3 V supply for the IO pins, the oscillator IO pins, the ADC pins > + and the internal LDO. The 1.8 V core rail is generated internally. > + > + reset-gpios: > + description: > + GPIO connected to the active-low RST# pin. Optional, since the board > + may instead use an RC reset circuit. > + maxItems: 1 > + > + interrupts: > + description: > + INT# pin, active low. Signals RA8875 interrupt events such as touch > + panel, key scan, DMA, BTE and font access completion. Optional, since > + the host can poll the interrupt status register instead. Last sentence is not correct. What driver can do is here less relevant. Question is whether hardware datasheet allows interrupt being not connected. > + maxItems: 1 > + > +required: > + - compatible > + - reg > + - display-timings > + - vdd-supply Best regards, Krzysztof
