On Fri, Mar 13, 2026 at 04:56:29PM +0000, Conor Dooley wrote: > On Fri, Mar 13, 2026 at 04:20:44PM +0100, Michael Riesch via B4 Relay wrote: > > From: Michael Riesch > > > > Add documentation for the Rockchip RK3588 Video Capture (VICAP) unit. > > > > Signed-off-by: Michael Riesch > > --- > > .../bindings/media/rockchip,rk3588-vicap.yaml | 256 +++++++++++++++++++++ > > MAINTAINERS | 1 + > > 2 files changed, 257 insertions(+) > > > > diff --git a/Documentation/devicetree/bindings/media/rockchip,rk3588-vicap.yaml b/Documentation/devicetree/bindings/media/rockchip,rk3588-vicap.yaml > > new file mode 100644 > > index 000000000000..7fd4214921cb > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/media/rockchip,rk3588-vicap.yaml > > @@ -0,0 +1,256 @@ > > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) > > +%YAML 1.2 > > +--- > > +$id: http://devicetree.org/schemas/media/rockchip,rk3588-vicap.yaml# > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > + > > +title: Rockchip RK3588 Video Capture (VICAP) > > + > > +maintainers: > > + - Michael Riesch > > + > > +description: > > + The Rockchip RK3588 Video Capture (VICAP) block features a digital video > > + port (DVP, a parallel video interface) and six MIPI CSI-2 ports. It receives > > + the data from camera sensors, video decoders, or other companion ICs and > > + transfers it into system main memory by AXI bus and/or passes it to the image > > + signal processing (ISP) blocks. > > + > > +properties: > > + compatible: > > + enum: > > + - rockchip,rk3588-vicap > > Curious why this cannot share a binding with the existing 3568-vicap. > Looks pretty similar binding wise at least. > If it's an entirely different architecture or whatever, please mention > that in your commit message. Looking further, it's using the same driver too...