[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1596086296-28529-2-git-send-email-deesin@codeaurora.org>
Date: Thu, 30 Jul 2020 10:48:11 +0530
From: Deepak Kumar Singh <deesin@...eaurora.org>
To: bjorn.andersson@...aro.org, clew@...eaurora.org
Cc: mathieu.poirier@...aro.org, linux-arm-msm@...r.kernel.org,
linux-remoteproc@...r.kernel.org, linux-kernel@...r.kernel.org,
Konstantin Dorfman <kdorfman@...eaurora.org>,
Deepak Kumar Singh <deesin@...eaurora.org>
Subject: [PATCH V1 1/6] rpmsg: glink: fix destroy channel endpoint logic
From: Konstantin Dorfman <kdorfman@...eaurora.org>
When rpmsg client driver destroys last channel endpoint, remove rpmsg
device is triggered. In both cases (destroy endpoint and remove device)
a glink close command sent to the remote peer.
This change, when for removing rpmsg device endpoint already destroyed
will avoid sending second glink close command.
Signed-off-by: Konstantin Dorfman <kdorfman@...eaurora.org>
Signed-off-by: Deepak Kumar Singh <deesin@...eaurora.org>
---
drivers/rpmsg/qcom_glink_native.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/rpmsg/qcom_glink_native.c b/drivers/rpmsg/qcom_glink_native.c
index 1995f5b..2668c66 100644
--- a/drivers/rpmsg/qcom_glink_native.c
+++ b/drivers/rpmsg/qcom_glink_native.c
@@ -1210,6 +1210,10 @@ static void qcom_glink_destroy_ept(struct rpmsg_endpoint *ept)
unsigned long flags;
spin_lock_irqsave(&channel->recv_lock, flags);
+ if (!channel->ept.cb) {
+ spin_unlock_irqrestore(&channel->recv_lock, flags);
+ return;
+ }
channel->ept.cb = NULL;
spin_unlock_irqrestore(&channel->recv_lock, flags);
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
Powered by blists - more mailing lists