Fedora KDE power management unsuitable for asahi

[cloehle]

I know this isn't a kernel issue, but this is still the best place I could find to report this. Sorry if it isn't and please point me to a different place.
I noticed when upgrading from the arch-based to fedora that EAS (energy-aware scheduling) is no longer working out of the box.
The reason is that cpufreq policy0 is set to a governor that isn't schedutil but EAS only supports schedutil at this time.

Even if asahi no longer wanted to use EAS it still transles the user request badly.
The Plasma power management settings show 3 options: Power Save, Balanced and Performance. The default is balanced.
The M1 Pro has policy0 little (CPUs 0 and 1), policy2 big (CPUs 2-4) and policy5 big (CPUs 5-7).

When changing the power settings only policy0 actually changes:

# cat /sys/devices/system/cpu/cpufreq/policy*/scaling_governor 
performance
schedutil
schedutil

with performance being "powersave", "ondemand", "performance" respectively.
Clearly policy0 contributes the smallest amount to power usage on this system generally, therefore only changing policy0 isn't translating the user request at all.

Furthermore just having all set to schedutil, at least for "Power Save" and "Balance", should yield much better power results because of EAS being used.

[cloehle]

There's tuned and power-profiles-daemon in use. The profiles seem to be coming from RHEL according to here:
https://github.com/redhat-performance/tuned/blob/master/doc/manual/modules/performance/ref_tuned-profiles-distributed-with-rhel.adoc
I'll try to file a bug there as well.
I'm not sure where "only change first policy" bug originates from, though.