Message ID | 20241023102148.1698910-1-quic_sibis@quicinc.com |
---|---|
Headers | show |
Series | firmware: arm_scmi: Misc Fixes | expand |
On Wed, Oct 23, 2024 at 03:51:44PM +0530, Sibi Sankar wrote: > The series addresses the kernel warnings reported by Johan at [1] and are > are required to X1E cpufreq device tree changes [2] to land. > > [1] - https://lore.kernel.org/lkml/ZoQjAWse2YxwyRJv@hovoldconsulting.com/ > [2] - https://lore.kernel.org/lkml/20240612124056.39230-1-quic_sibis@quicinc.com/ > > The following warnings remain unadressed: > 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 > > They indicate that duplicate opps are reported by the SCP firmware and > they are seen during probe. They will get addressed by firmware updates. > > 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. Thanks for sorting this out, Sibi! I guess the above description is clear enough too as to why the opps_by_lvl warnings should stay (in some form). Johan