Attach detach ops are needed to connect to remote processor that is running before remoteproc driver is probed. Implement remoteproc framework ops that enables such use case on AMD-Xilinx platforms. Remote processor can also use On Chip sram Memory (OCM) for various purpose. For example, for fast code execution or data access compare to DDR memory. Such sram region is made available to remoteproc nodes via "sram" property. Add support in driver to parse and use OCM memory via sram property. Changes in v2: - Fix following sparse warnings drivers/remoteproc/xlnx_r5_remoteproc.c:827:21: sparse: expected struct rsc_tbl_data *rsc_data_va drivers/remoteproc/xlnx_r5_remoteproc.c:844:18: sparse: expected struct resource_table *rsc_addr drivers/remoteproc/xlnx_r5_remoteproc.c:898:24: sparse: expected void volatile [noderef] __iomem *addr drivers/remoteproc/xlnx_r5_remoteproc.c:995:26: sparse: warning: Using plain integer as NULL pointer Tanmay Shah (2): drivers: remoteproc: xlnx: add attach detach support drivers: remoteproc: xlnx: add sram support drivers/remoteproc/xlnx_r5_remoteproc.c | 385 +++++++++++++++++++++++- 1 file changed, 380 insertions(+), 5 deletions(-) base-commit: c8d8f841e95bcc07ac8c5621fc171a24f1fd5cdb -- 2.25.1
