public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Dybcio <konradybcio@kernel.org>
To: Johan Hovold <johan@kernel.org>, Sibi Sankar <quic_sibis@quicinc.com>
Cc: sudeep.holla@arm.com, cristian.marussi@arm.com,
	linux-kernel@vger.kernel.org, arm-scmi@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-arm-msm@vger.kernel.org, konradybcio@kernel.org
Subject: Re: [PATCH V2 1/2] firmware: arm_scmi: Ensure that the message-id supports fastchannel
Date: Wed, 4 Sep 2024 13:29:29 +0200	[thread overview]
Message-ID: <d482dca4-e61b-4a94-887b-d14422243929@kernel.org> (raw)
In-Reply-To: <ZtgFj1y5ggipgEOS@hovoldconsulting.com>

On 4.09.2024 9:00 AM, Johan Hovold wrote:
> On Wed, Sep 04, 2024 at 08:43:23AM +0530, Sibi Sankar wrote:
>> Currently the perf and powercap protocol relies on the protocol domain
>> attributes, which just ensures that one fastchannel per domain, before
>> instantiating fastchannels for all possible message-ids. Fix this by
>> ensuring that each message-id supports fastchannel before initialization.
> 
> Please include the warnings that I reported seeing on x1e80100 and that
> this patch suppresses to the commit message:
> 
> arm-scmi firmware:scmi: Failed to get FC for protocol 13 [MSG_ID:6 / RES_ID:0] - ret:-95. Using regular messaging.
> arm-scmi firmware:scmi: Failed to get FC for protocol 13 [MSG_ID:6 / RES_ID:1] - ret:-95. Using regular messaging.
> arm-scmi firmware:scmi: Failed to get FC for protocol 13 [MSG_ID:6 / RES_ID:2] - ret:-95. Using regular messaging.
>  
>> Fixes: 6f9ea4dabd2d ("firmware: arm_scmi: Generalize the fast channel support")
> 
> And add:
> 
> Reported-by: Johan Hovold <johan+linaro@kernel.org>
> Link: https://lore.kernel.org/lkml/ZoQjAWse2YxwyRJv@hovoldconsulting.com/
> 
> (or use Closes: if you prefer).
> 
>> Signed-off-by: Sibi Sankar <quic_sibis@quicinc.com>
>> ---
>>
>> v1:
>> * add missing MSG_SUPPORTS_FASTCHANNEL definition.
> 
> Unfortunately, this patch breaks resume from suspend on the x1e80100 crd:
> 
>         [   26.919676] CPU4: Booted secondary processor 0x0000010000 [0x511f0011]
>         [   26.960607] arm-scmi firmware:scmi: timed out in resp(caller: do_xfer+0x164/0x568)
>         [   26.987142] cpufreq: cpufreq_online: ->get() failed
> 
> and then the machine hangs (mostly, I saw an nvme timeout message after a
> while).
> 
> Make sure you test suspend as well as some of the warnings I reported
> only show up during suspend.

Eh it looks like PERF_LEVEL_GET (msgid 8) requires the use of FC, but
the firmware fails to inform us about it through BIT(0) in attrs..

Konrad

  reply	other threads:[~2024-09-04 11:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-04  3:13 [PATCH V2 0/2] firmware: arm_scmi: Misc Fixes Sibi Sankar
2024-09-04  3:13 ` [PATCH V2 1/2] firmware: arm_scmi: Ensure that the message-id supports fastchannel Sibi Sankar
2024-09-04  7:00   ` Johan Hovold
2024-09-04 11:29     ` Konrad Dybcio [this message]
2024-09-04 12:38       ` Sudeep Holla
2024-09-04 14:20         ` Cristian Marussi
2024-09-05 12:54           ` Konrad Dybcio
2024-10-07  6:46             ` Sibi Sankar
2024-09-04  3:13 ` [PATCH V2 2/2] firmware: arm_scmi: Skip adding bad duplicates Sibi Sankar
2024-09-04  7:09   ` Johan Hovold
2024-09-04  8:05     ` Johan Hovold
2024-09-04 13:56   ` Konrad Dybcio
2024-09-04 14:00     ` Konrad Dybcio
2024-09-04 15:21   ` Cristian Marussi
2024-09-04 15:30     ` Cristian Marussi
2024-09-04 15:46       ` Cristian Marussi
2024-09-05 12:43         ` Cristian Marussi
2024-10-07  7:00       ` Sibi Sankar
2024-10-09 14:20         ` Cristian Marussi
2024-09-04 16:12   ` Sudeep Holla
2024-09-04 16:20     ` Cristian Marussi
2024-10-07  6:51       ` Sibi Sankar

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=d482dca4-e61b-4a94-887b-d14422243929@kernel.org \
    --to=konradybcio@kernel.org \
    --cc=arm-scmi@vger.kernel.org \
    --cc=cristian.marussi@arm.com \
    --cc=johan@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_sibis@quicinc.com \
    --cc=sudeep.holla@arm.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