rpmsg: fix rpmsg_virtio_get_tx_payload_buffer error

wyr-7 · wyr-7 · commit 8cbaffdd9668 · 2024-10-09T20:08:48.000+08:00
If rpmsg_virtio_notify_wait returns RPMSG_SUCCESS, we don't call
rpmsg_virtio_get_tx_buffer.

Signed-off-by: Yongrong Wang &lt;wangyongrong@xiaomi.com&gt;
diff --git a/lib/rpmsg/rpmsg_virtio.c b/lib/rpmsg/rpmsg_virtio.c
@@ -390,11 +390,9 @@ static void *rpmsg_virtio_get_tx_payload_buffer(struct rpmsg_device *rdev,
 		 * use metal_sleep_usec() method by default.
 		 */
 		status = rpmsg_virtio_notify_wait(rvdev, rvdev->rvq);
-		if (status == RPMSG_EOPNOTSUPP) {
+		if (status != RPMSG_SUCCESS) {
 			metal_sleep_usec(RPMSG_TICKS_PER_INTERVAL);
 			tick_count--;
-		} else if (status == RPMSG_SUCCESS) {
-			break;
 		}
 	}
 

Original file line number	Diff line number	Diff line change
`@@ -390,11 +390,9 @@ static void rpmsg_virtio_get_tx_payload_buffer(struct rpmsg_device rdev,`
`390`	`390`	`* use metal_sleep_usec() method by default.`
`391`	`391`	`*/`
`392`	`392`	`status = rpmsg_virtio_notify_wait(rvdev, rvdev->rvq);`
`393`		`- if (status == RPMSG_EOPNOTSUPP) {`
	`393`	`+ if (status != RPMSG_SUCCESS) {`
`394`	`394`	`metal_sleep_usec(RPMSG_TICKS_PER_INTERVAL);`
`395`	`395`	`tick_count--;`
`396`		`- } else if (status == RPMSG_SUCCESS) {`
`397`		`- break;`
`398`	`396`	`}`
`399`	`397`	`}`
`400`	`398`