From: Barry Song <21cnbao@gmail.com>
To: ohad@wizery.com, rusty@rustcorp.com.au, mst@redhat.com,
linux-kernel@vger.kernel.org
Cc: workgroup.linux@csr.com, Wei Chen <Wei.Chen@csr.com>,
Barry Song <Baohua.Song@csr.com>
Subject: [PATCH 1/2] drivers:remoteproc:support predefined vq notifyid
Date: Tue, 3 Mar 2015 20:02:45 +0800 [thread overview]
Message-ID: <1425384165-4684-1-git-send-email-21cnbao@gmail.com> (raw)
From: Wei Chen <Wei.Chen@csr.com>
In current rproc use scenario, the vq notifyid
will be allocated by Linux, and write back this
notifyid to RSC table to tell DSP.
But in some scenarios, we might meet the DSP
predefined the vq notifyid. In these scenarios,
the rproc have to read predefined vq notifyid
from RSC table, and then request a same notifyid
in Linux side.
Signed-off-by: Wei Chen <Wei.Chen@csr.com>
Signed-off-by: Barry Song <Baohua.Song@csr.com>
---
drivers/remoteproc/remoteproc_core.c | 16 +++++++++++-----
1 file changed, 11 insertions(+), 5 deletions(-)
diff --git a/drivers/remoteproc/remoteproc_core.c b/drivers/remoteproc/remoteproc_core.c
index 3cd85a6..f9709b6 100644
--- a/drivers/remoteproc/remoteproc_core.c
+++ b/drivers/remoteproc/remoteproc_core.c
@@ -197,7 +197,7 @@ int rproc_alloc_vring(struct rproc_vdev *rvdev, int i)
struct fw_rsc_vdev *rsc;
dma_addr_t dma;
void *va;
- int ret, size, notifyid;
+ int ret, size, notifyid, pre_nid;
/* actual size of vring (in bytes) */
size = PAGE_ALIGN(vring_size(rvring->len, rvring->align));
@@ -213,11 +213,16 @@ int rproc_alloc_vring(struct rproc_vdev *rvdev, int i)
}
/*
+ * read predefined notifyids (via resource table)
+ */
+ rsc = (void *)rproc->table_ptr + rvdev->rsc_offset;
+ pre_nid = rsc->vring[i].notifyid;
+
+ /*
* Assign an rproc-wide unique index for this vring
* TODO: assign a notifyid for rvdev updates as well
- * TODO: support predefined notifyids (via resource table)
*/
- ret = idr_alloc(&rproc->notifyids, rvring, 0, 0, GFP_KERNEL);
+ ret = idr_alloc(&rproc->notifyids, rvring, pre_nid, 0, GFP_KERNEL);
if (ret < 0) {
dev_err(dev, "idr_alloc failed: %d\n", ret);
dma_free_coherent(dev->parent, size, va, dma);
@@ -238,9 +243,10 @@ int rproc_alloc_vring(struct rproc_vdev *rvdev, int i)
* set up the iommu. In this case the device address (da) will
* hold the physical address and not the device address.
*/
- rsc = (void *)rproc->table_ptr + rvdev->rsc_offset;
rsc->vring[i].da = dma;
- rsc->vring[i].notifyid = notifyid;
+ /* If notifyid is not predefined, write back to rsc */
+ if (!pre_nid)
+ rsc->vring[i].notifyid = notifyid;
return 0;
}
--
1.9.1
reply other threads:[~2015-03-03 12:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1425384165-4684-1-git-send-email-21cnbao@gmail.com \
--to=21cnbao@gmail.com \
--cc=Baohua.Song@csr.com \
--cc=Wei.Chen@csr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=ohad@wizery.com \
--cc=rusty@rustcorp.com.au \
--cc=workgroup.linux@csr.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®