[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <58305f4d-fbcb-44cc-053c-d30f4ca082e7@quicinc.com>
Date: Fri, 7 Apr 2023 15:35:49 -0700
From: Chris Lew <quic_clew@...cinc.com>
To: Bjorn Andersson <quic_bjorande@...cinc.com>,
Bjorn Andersson <andersson@...nel.org>,
Mathieu Poirier <mathieu.poirier@...aro.org>
CC: <linux-arm-msm@...r.kernel.org>,
<linux-remoteproc@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] rpmsg: glink: Wait for intent after intent request
On 3/27/2023 7:46 AM, Bjorn Andersson wrote:
> When written it was assumed that upon requesting an intent, the intent
> would arrive followed by an intent request acknowledgement. But this is
> not always the case, in which case the current implementation would
> request yet another intent and when that is acknowledged find the first
> received intent - if the remote didn't run out of memory and failed the
> second request...
>
> Bjorn Andersson (2):
> rpmsg: glink: Transition intent request signaling to wait queue
> rpmsg: glink: Wait for intent, not just request ack
>
> drivers/rpmsg/qcom_glink_native.c | 37 ++++++++++++++++++++++---------
> 1 file changed, 26 insertions(+), 11 deletions(-)
>
Reviewed-by: Chris Lew <quic_clew@...cinc.com>
Powered by blists - more mailing lists