On Tue, 29 Sep 2020, Rob Herring wrote: > > index 000000000000..ce02e425692e > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/remoteproc/xilinx,zynqmp-r5-remoteproc.yaml > > @@ -0,0 +1,120 @@ > > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) > > +%YAML 1.2 > > +--- > > +$id: "http://devicetree.org/schemas/remoteproc/xilinx,zynqmp-r5-remoteproc.yaml#"; > > +$schema: "http://devicetree.org/meta-schemas/core.yaml#"; > > + > > +title: Xilinx R5 remote processor controller bindings > > + > > +description: > > + This document defines the binding for the remoteproc component that loads and > > + boots firmwares on the Xilinx Zynqmp and Versal family chipset. > > + > > + Note that the Linux has global addressing view of the R5-related memory (TCM) > > + so the absolute address ranges are provided in TCM reg's. > > blank line needed. > > TCMs specifically I'm concerned about how they are represented in system > DT and here... So far I have been keeping the TCMs in system DT as regular nodes under /amba. E.g.: tcm: tcm@ffe00000 { compatible = "mmio-sram"; reg = <0x0 0xffe00000 0x0 0x10000>; }; (I am not sure if "mmio-sram" is the right compatible.)
