From: Jianping <jianping.li@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: srini@kernel.org, amahesh@qti.qualcomm.com, arnd@arndb.de,
Greg KH <gregkh@linuxfoundation.org>,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>
Subject: Re: [PATCH] fastrpc: Reduce log level for DSP info and reserved memory messages
Date: Tue, 4 Aug 2026 14:41:05 +0800 [thread overview]
Message-ID: <68a09a71-9b34-4219-a5aa-eba3467a2ae1@oss.qualcomm.com> (raw)
In-Reply-To: <cg526ebtmnboqpw5aabwrtmoc7fhnvc57dmjax5zltcjonnazv@pynuwgpx3bi5>
在 2026/5/18 7:08, Dmitry Baryshkov 写道:
> On Thu, May 14, 2026 at 02:28:25PM +0800, Jianping Li wrote:
>> On some platforms (e.g. QCS615 Talos), fastrpc may temporarily fail
>> to retrieve DSP attributes during boot, resulting in repeated
>
> temporarily? What does it mean? Should there be any sync with the DSP,
> letting the FastRPC driver know when it's safe to retrieve the
> information?
Hi Dmitry,
Thanks for the review.
You are right, "temporarily during boot" is not an accurate description.
After further investigation, the message is not tied specifically to
boot timing.
I can reproduce it at any time by manually starting adsprpcd on QCS615
Talos:
# adsprpcd
which results in repeated:
Error: dsp information is incorrect err: -1
The failure originates from the DSP capability query path, where the DSP
side returns an error while handling the request.
This feature is not currently available on Talos adsp.
Therefore my intention is not to hide a boot synchronization problem,
but to reduce console noise for a condition that appears to be
platform-specific and non-fatal.
I'll update the commit message to describe the issue more accurately in
the next version.
Thanks,
Jianping
>
>> "Error: dsp information is incorrect" messages printed on the
>> console.
>>
>> These messages are observed continuously during boot when metadata
>> flashing is enabled as part of RC releases, causing unnecessary
>> log noise.
>>
>> Similarly, the absence of reserved DMA memory is a valid
>> configuration and does not represent an error condition.
>>
>> Since these scenarios are expected and do not indicate a failure,
>> downgrade the log level from dev_err/dev_info to dev_dbg to avoid
>> flooding the console.
>>
>> No functional change intended.
>>
>> Signed-off-by: Jianping Li <jianping.li@oss.qualcomm.com>
>> ---
>> drivers/misc/fastrpc.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
next prev parent reply other threads:[~2026-08-04 6:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 6:28 Jianping Li
2026-05-17 23:08 ` Dmitry Baryshkov
2026-07-03 8:31 ` Jianping Li
2026-07-04 0:12 ` Dmitry Baryshkov
2026-08-04 6:41 ` Jianping [this message]
2026-08-25 6:47 ` Ekansh Gupta
2026-08-26 8:41 ` Jianping Li
2026-08-27 4:47 ` Ekansh Gupta
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=68a09a71-9b34-4219-a5aa-eba3467a2ae1@oss.qualcomm.com \
--to=jianping.li@oss.qualcomm.com \
--cc=amahesh@qti.qualcomm.com \
--cc=arnd@arndb.de \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ekansh.gupta@oss.qualcomm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srini@kernel.org \
/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
all inboxes | Powered by JetHome®