On Tue, May 26, 2020 at 11:40 AM Ben Levinsky <BLEVINSK@xxxxxxxxxx> wrote: > > Hi Rob, > > The Xilinx R5 Remoteproc driver has been around for a long time -- admittedly we should have upstreamed it long ago. The driver in the current form is using an "classic" remoteproc device tree node as described here. I would rather not have 2 possible bindings to maintain. If there's been no rush to upstream this til now, then it can wait longer. > > I am working with Stefano to come up with an appropriate System Device Tree representation but it is not going to be ready right away. Our preference would be to upstream the remoteproc node and driver in their current forms while system device tree is maturing. There's obviously going to still need to be some sort of description of the interface between cores, but this has parts that obviously conflict with what's getting defined for system DT. The TCMs are the most obvious. If you can remove (or hardcode in the driver) what conflicts, then perhaps this can be upstreamed now. Rob
