On Tue, Nov 12, 2024 at 04:56:26PM +0100, Ulf Hansson wrote: > On Wed, 6 Nov 2024 at 08:12, Sudeep Holla <sudeep.holla@xxxxxxx> wrote: > > On Wed, Oct 30, 2024 at 04:28:41PM +0000, Cristian Marussi wrote: > > > On Wed, Oct 30, 2024 at 05:19:39PM +0100, Ulf Hansson wrote: > > > > On Wed, 30 Oct 2024 at 13:55, Sibi Sankar <quic_sibis@xxxxxxxxxxx> wrote: > > > > > > > > > > The series addresses the kernel warnings reported by Johan at [1] and are > > > > > are required to X1E cpufreq device tree changes to land. > > > > > > > > > > [1] - https://lore.kernel.org/lkml/ZoQjAWse2YxwyRJv@xxxxxxxxxxxxxxxxxxxx/ > > > > > > > > > > Duplicate levels: > > > > > arm-scmi arm-scmi.0.auto: Level 2976000 Power 218062 Latency 30us Ifreq 2976000 Index 10 > > > > > arm-scmi arm-scmi.0.auto: Level 3206400 Power 264356 Latency 30us Ifreq 3206400 Index 11 > > > > > arm-scmi arm-scmi.0.auto: Level 3417600 Power 314966 Latency 30us Ifreq 3417600 Index 12 > > > > > arm-scmi arm-scmi.0.auto: Failed to add opps_by_lvl at 3417600 for NCC - ret:-16 > > > > > arm-scmi arm-scmi.0.auto: Failed to add opps_by_lvl at 3417600 for NCC - ret:-16 > > > > > arm-scmi arm-scmi.0.auto: Level 4012800 Power 528848 Latency 30us Ifreq 4012800 Index 15 > > > > > > > > > > ^^ exist because SCP reports duplicate values for the highest sustainable > > > > > freq for perf domains 1 and 2. These are the only freqs that appear as > > > > > duplicates and will be fixed with a firmware update. FWIW the warnings > > > > > that we are addressing in this series will also get fixed by a firmware > > > > > update but they still have to land for devices already out in the wild. > > > > > > > > > > V4: > > > > > * Rework debugfs node creation patch [Ulf/Dmitry] > > > > > * Reduce report level to dev_info and tag it with FW_BUG [Johan/Dmitry] > > > > > * Add cc stable and err logs to patch 1 commit message [Johan] > Sorry for the delay. I have picked up the remaining patches from this > series. All applied for fixes and by adding stable tags to them, > thanks! As I reported here: https://lore.kernel.org/lkml/ZyTQ9QD1tEkhQ9eu@xxxxxxxxxxxxxxxxxxxx/ I'm seeing a hard reset on the x1e80100 CRD and Lenovo ThinkPad T14s when accessing the cpufreq sysfs attributes. Sibi tracked it down to the first patch in this series ("firmware: arm_scmi: Ensure that the message-id supports fastchannel") and reverting that one indeed fixes the reset. Unfortunately this was only discussed on IRC and was never reported in this thread. Ulf, could you please drop the first patch again until we've figured out how best to handle this? Johan
