[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <zdpszrr7lhe6bvnq3ullwet3pzfidnhfo3wlvfbljnu7q4j2z6@3romukxqjyvd>
Date: Mon, 7 Oct 2024 17:00:32 +0300
From: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
To: Jonathan Marek <jonathan@...ek.ca>
Cc: linux-arm-msm@...r.kernel.org, Bjorn Andersson <andersson@...nel.org>,
Mathieu Poirier <mathieu.poirier@...aro.org>, Sricharan Ramabadhran <quic_srichara@...cinc.com>,
Arun Kumar Neelakantam <quic_aneela@...cinc.com>,
"open list:REMOTE PROCESSOR MESSAGING (RPMSG) SUBSYSTEM" <linux-remoteproc@...r.kernel.org>, open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] rpmsg: glink: use only lower 16-bits of param2 for
CMD_OPEN name length
On Mon, Oct 07, 2024 at 09:19:05AM GMT, Jonathan Marek wrote:
> On 10/7/24 9:16 AM, Dmitry Baryshkov wrote:
> > On Mon, Oct 07, 2024 at 12:47:22AM GMT, Jonathan Marek wrote:
> > > The name len field of the CMD_OPEN packet is only 16-bits and the upper
> > > 16-bits of "param2" are a different field, which can be nonzero in certain
> > > situations, and CMD_OPEN packets can be unexpectedly dropped because of
> > > this.
> >
> > Any idea about the upper 16 bits? Should we care about that data too?
> >
>
> Its a "prio" value, it should be OK to ignore it.
Could you please document it in the commit message and in a comment next
to the qcom_glink_rx_defer() call?
--
With best wishes
Dmitry
Powered by blists - more mailing lists