From: Srinivas Kandagatla <srini@kernel.org>
To: Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>,
Jianping Li <jianping.li@oss.qualcomm.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
quic_chennak@quicinc.com
Subject: Re: [PATCH v2] misc: fastrpc: Reduce console noise from expected DSP info, reserved memory and session messages
Date: Mon, 14 Sep 2026 09:12:47 +0100 [thread overview]
Message-ID: <178937356713.258680.1119640361942817879.b4-ty@kernel.org> (raw)
In-Reply-To: <20260907070356.509-1-jianping.li@oss.qualcomm.com>
On Mon, 07 Sep 2026 15:03:56 +0800, Jianping Li wrote:
> On some platforms the DSP firmware does not support the fastrpc
> capability/attribute query. The DSP side returns an error (err: -1)
> while handling the request, so fastrpc_get_info_from_dsp() does not
> return DSP_UNSUPPORTED_API but a generic error, and the "else if (err)"
> branch in fastrpc_get_info_from_kernel() is taken.
>
> cctx->valid_attributes is therefore never set and every open()/query
> re-prints the same "dsp information is incorrect" line. This is not
> tied to boot timing: it can be reproduced at any time by manually
> starting adsprpcd. On RC builds with metadata flashing enabled several
> clients come up and flood the console.
>
> [...]
Applied, thanks!
[1/1] misc: fastrpc: Reduce console noise from expected DSP info, reserved memory and session messages
commit: 94778611d71b57ff917de507229e1c58ad9deba7
Best regards,
--
Srinivas Kandagatla <srini@kernel.org>
prev parent reply other threads:[~2026-09-14 8:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 7:03 Jianping Li
2026-09-14 8:12 ` Srinivas Kandagatla [this message]
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=178937356713.258680.1119640361942817879.b4-ty@kernel.org \
--to=srini@kernel.org \
--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=jianping.li@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_chennak@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
all inboxes | Powered by JetHome®