[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZxufoL3NjYs8Lyq0@hovoldconsulting.com>
Date: Fri, 25 Oct 2024 15:39:44 +0200
From: Johan Hovold <johan@...nel.org>
To: Sibi Sankar <quic_sibis@...cinc.com>
Cc: sudeep.holla@....com, cristian.marussi@....com, ulf.hansson@...aro.org,
jassisinghbrar@...il.com, dmitry.baryshkov@...aro.org,
linux-kernel@...r.kernel.org, arm-scmi@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-arm-msm@...r.kernel.org,
konradybcio@...nel.org, linux-pm@...r.kernel.org,
tstrudel@...gle.com, rafael@...nel.org,
Johan Hovold <johan+linaro@...nel.org>
Subject: Re: [PATCH V4 1/4] firmware: arm_scmi: Ensure that the message-id
supports fastchannel
On Wed, Oct 23, 2024 at 03:51:45PM +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.
Again, perhaps you could include the error message I reported here so
that anyone searching for that error will find this fix more easily?
> Reported-by: Johan Hovold <johan+linaro@...nel.org>
> Closes: https://lore.kernel.org/lkml/ZoQjAWse2YxwyRJv@hovoldconsulting.com/
> Fixes: 6f9ea4dabd2d ("firmware: arm_scmi: Generalize the fast channel support")
And, also again, should you add a CC-stable tag here to get this
backported?
> Signed-off-by: Sibi Sankar <quic_sibis@...cinc.com>
> Reviewed-by: Sudeep Holla <sudeep.holla@....com>
> Tested-by: Johan Hovold <johan+linaro@...nel.org>
> ---
>
> v3:
> * Pick up R-b, T-b from the list.
> * Move scmi_protocol_msg_check to the top [Sudeep]
Johan
Powered by blists - more mailing lists