Displaying 5 results from an estimated 5 matches for "unlock_eptdev".
2020 Jun 18
2
[PATCH v3 5/5] vhost: add an RPMsg API
...ADDR_ANY) {
+ printk("%s: got client address %#x from first rx!\n", __func__, addr);
+ rpdev->dst = addr;
+ }
+
skb = alloc_skb(len, GFP_ATOMIC);
if (!skb)
return -ENOMEM;
@@ -235,6 +240,12 @@ static ssize_t rpmsg_eptdev_write(struct file *filp, const char __user *buf,
goto unlock_eptdev;
}
+ if (eptdev->rpdev->dst == RPMSG_ADDR_ANY) {
+ ret = -EPIPE;
+ WARN(1, "Cannot write first on server, must wait for client!\n");
+ goto unlock_eptdev;
+ }
+
if (filp->f_flags & O_NONBLOCK)
ret = rpmsg_trysend(eptdev->ept, kbuf, len);
else
diff --git a/sam...
2020 Jun 18
2
[PATCH v3 5/5] vhost: add an RPMsg API
...ADDR_ANY) {
+ printk("%s: got client address %#x from first rx!\n", __func__, addr);
+ rpdev->dst = addr;
+ }
+
skb = alloc_skb(len, GFP_ATOMIC);
if (!skb)
return -ENOMEM;
@@ -235,6 +240,12 @@ static ssize_t rpmsg_eptdev_write(struct file *filp, const char __user *buf,
goto unlock_eptdev;
}
+ if (eptdev->rpdev->dst == RPMSG_ADDR_ANY) {
+ ret = -EPIPE;
+ WARN(1, "Cannot write first on server, must wait for client!\n");
+ goto unlock_eptdev;
+ }
+
if (filp->f_flags & O_NONBLOCK)
ret = rpmsg_trysend(eptdev->ept, kbuf, len);
else
diff --git a/sam...
2020 Jun 18
0
[PATCH v3 5/5] vhost: add an RPMsg API
...nt address %#x from first rx!\n", __func__, addr);
> + rpdev->dst = addr;
> + }
> +
> skb = alloc_skb(len, GFP_ATOMIC);
> if (!skb)
> return -ENOMEM;
> @@ -235,6 +240,12 @@ static ssize_t rpmsg_eptdev_write(struct file *filp, const char __user *buf,
> goto unlock_eptdev;
> }
>
> + if (eptdev->rpdev->dst == RPMSG_ADDR_ANY) {
> + ret = -EPIPE;
> + WARN(1, "Cannot write first on server, must wait for client!\n");
> + goto unlock_eptdev;
> + }
> +
> if (filp->f_flags & O_NONBLOCK)
> ret = rpmsg_trysend(e...
2020 Jun 17
2
[PATCH v3 5/5] vhost: add an RPMsg API
On Wed, May 27, 2020 at 08:05:41PM +0200, Guennadi Liakhovetski wrote:
> Linux supports running the RPMsg protocol over the VirtIO transport
> protocol, but currently there is only support for VirtIO clients and
> no support for a VirtIO server. This patch adds a vhost-based RPMsg
> server implementation.
This looks really useful, but why is it implemented as an API and not as
a real
2020 Jun 17
2
[PATCH v3 5/5] vhost: add an RPMsg API
On Wed, May 27, 2020 at 08:05:41PM +0200, Guennadi Liakhovetski wrote:
> Linux supports running the RPMsg protocol over the VirtIO transport
> protocol, but currently there is only support for VirtIO clients and
> no support for a VirtIO server. This patch adds a vhost-based RPMsg
> server implementation.
This looks really useful, but why is it implemented as an API and not as
a real