On Fri, Aug 31, 2018 at 05:01:48PM +0300, Georgi Djakov wrote: > On some Qualcomm SoCs, there is a remote processor, which controls some of > the Network-On-Chip interconnect resources. Other CPUs express their needs > by communicating with this processor. Add a driver to handle communication > with this remote processor.
I don't think you should have a binding nor a separate driver for this. It's not actually an interconnect provider, so it doesn't belong in bindings/interconnect. And it just looks like abuse of DT to instantiate some driver. All the driver amounts to is a 1 function wrapper for RPM_KEY_BW messages. Can't this be part of the parent? Rob
