From: Chris Lew <quic_clew@quicinc.com>
To: Bjorn Andersson <quic_bjorande@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: Alex Elder <elder@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-msm@vger.kernel.org>,
<linux-remoteproc@vger.kernel.org>
Subject: Re: [PATCH 1/4] soc: qcom: aoss: Move length requirements from caller
Date: Mon, 31 Jul 2023 14:29:44 -0700 [thread overview]
Message-ID: <e4592feb-3878-b0eb-61e4-fb6dfc358e1a@quicinc.com> (raw)
In-Reply-To: <20230731041013.2950307-2-quic_bjorande@quicinc.com>
On 7/30/2023 9:10 PM, Bjorn Andersson wrote:
> diff --git a/drivers/soc/qcom/qcom_aoss.c b/drivers/soc/qcom/qcom_aoss.c
> /* The message RAM only implements 32-bit accesses */
> __iowrite32_copy(qmp->msgram + qmp->offset + sizeof(u32),
> - data, len / sizeof(u32));
> - writel(len, qmp->msgram + qmp->offset);
> + buf, sizeof(buf) / sizeof(u32));
> + writel(sizeof(buf), qmp->msgram + qmp->offset);
>
Looks like we are telling the firmware the packet size will always be
QMP_MSG_LEN?
This should be ok but might be a problem when debugging. The AOSS
firmware only logs size of the message instead of the full string
because of memory constraints.
We would normally match the firmware and host logs based on size, but
won't be able to differentiate this way with a fixed size.
next prev parent reply other threads:[~2023-07-31 21:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 4:10 [PATCH 0/4] soc: qcom: aoss: Introduce debugfs interface and cleanup things Bjorn Andersson
2023-07-31 4:10 ` [PATCH 1/4] soc: qcom: aoss: Move length requirements from caller Bjorn Andersson
2023-07-31 15:10 ` Simon Horman
2023-07-31 21:29 ` Chris Lew [this message]
2023-07-31 23:10 ` Bjorn Andersson
2023-07-31 23:46 ` Chris Lew
2023-07-31 4:10 ` [PATCH 2/4] soc: qcom: aoss: Add debugfs interface for sending messages Bjorn Andersson
2023-07-31 8:15 ` Konrad Dybcio
2023-07-31 16:01 ` Bjorn Andersson
2023-07-31 8:21 ` Andrew Lunn
2023-07-31 15:39 ` Bjorn Andersson
2023-08-01 8:45 ` Andrew Lunn
2023-07-31 15:08 ` Simon Horman
2023-08-01 4:41 ` Pavan Kondeti
2023-07-31 4:10 ` [PATCH 3/4] soc: qcom: aoss: Format string in qmp_send() Bjorn Andersson
2023-07-31 8:20 ` Konrad Dybcio
2023-07-31 4:10 ` [PATCH 4/4] soc: qcom: aoss: Tidy up qmp_send() callers Bjorn Andersson
2023-07-31 8:23 ` Konrad Dybcio
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e4592feb-3878-b0eb-61e4-fb6dfc358e1a@quicinc.com \
--to=quic_clew@quicinc.com \
--cc=andersson@kernel.org \
--cc=davem@davemloft.net \
--cc=elder@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=quic_bjorande@quicinc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox