Re: [PATCH] fastrpc: Reduce log level for DSP info and reserved memory messages

在 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 <[email protected]>
>> ---
>>   drivers/misc/fastrpc.c | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>