[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210629150002.8050-1-phil.chang@mediatek.com>
Date: Tue, 29 Jun 2021 23:00:02 +0800
From: Phil Chang <phil.chang@...iatek.com>
To: <linux-remoteproc@...r.kernel.org>
CC: <ohad@...ery.com>, <bjorn.andersson@...aro.org>,
<mathieu.poirier@...aro.org>, <matthias.bgg@...il.com>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-mediatek@...ts.infradead.org>, <yj.chiang@...iatek.com>,
<mark-pk.tsai@...iatek.com>, <weiting.tsai@...iatek.com>,
Phil Chang <phil.chang@...iatek.com>
Subject: [PATCH] remoteproc: export rproc re/unregister to virtio device APIs
In some case, the remote processor already boot up on previous state,
but still need register to virtio device, so that exported those APIs.
Signed-off-by: Phil Chang <phil.chang@...iatek.com>
Signed-off-by: YJ chiang <yj.chiang@...iatek.com>
---
Hi
In our case, the remote processor is already boot up in u-boot,
we don't want to boot again or load fw in driver but register to virtio
device for rpmsg. so that needs those API exported.
Furthermore, the rproc_vq_interrupt is exported, so those functions
should be exported also.
thanks
drivers/remoteproc/remoteproc_virtio.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/remoteproc/remoteproc_virtio.c b/drivers/remoteproc/remoteproc_virtio.c
index 0cc617f76068..e23658a76f5e 100644
--- a/drivers/remoteproc/remoteproc_virtio.c
+++ b/drivers/remoteproc/remoteproc_virtio.c
@@ -425,6 +425,7 @@ int rproc_add_virtio_dev(struct rproc_vdev *rvdev, int id)
out:
return ret;
}
+EXPORT_SYMBOL(rproc_add_virtio_dev);
/**
* rproc_remove_virtio_dev() - remove an rproc-induced virtio device
@@ -440,3 +441,4 @@ int rproc_remove_virtio_dev(struct device *dev, void *data)
unregister_virtio_device(vdev);
return 0;
}
+EXPORT_SYMBOL(rproc_remove_virtio_dev);
--
2.18.0
Powered by blists - more mailing lists