Tuned-cachy profile switching behaves inconsistently with ThinkPad power mode key (T14 Gen 6)

This ThinkPad has a dedicated key for switching power profiles. Normally, it cycles through three modes, I think: power_save , balanced , and performance (AMD Ryzen 3400 Pro).

I was initially relying on power-profiles-daemon (ppd ) shipped with CachyOS. However, compared to tuned , switching profiles with the dedicated key was not instant - there was a noticeable delay - which made me choose tuned instead.

That said, I heard that ppd-cachy also includes some extra optimizations, like changing the scheduler or something similar (not entirely sure). Because I wanted those integrations too, I ended up using tuned-cachy together with tuned-ppd-cachy .

However, these are the profiles I get every time I press the key:

[nicknamely@ZenThink ~]$ tuned-adm active
Current active profile: cachyos-powersave

[nicknamely@ZenThink ~]$ tuned-adm active
Current active profile: cachyos-desktop

[nicknamely@ZenThink ~]$ tuned-adm active
Current active profile: cachyos-powersave

[nicknamely@ZenThink ~]$ tuned-adm active
Current active profile: cachyos-desktop

[nicknamely@ZenThink ~]$ tuned-adm active
Current active profile: cachyos-desktop

[nicknamely@ZenThink ~]$ tuned-adm active
Current active profile: cachyos-gaming

I think there is a conflict, isn’t there?

The system/firmware seems to assume only 3 profiles for the dedicated ThinkPad power-mode key, while tuned-cachy adds additional profiles. Because of that, the switching behavior becomes inconsistent.

Just to clarify - using tuned originally worked as expected?

And what about tuned-ppd?

can you report

cpupower frequency-info

tuned with tuned-ppd behave as expected, and switching profiles is instant compared to ppd

analyzing CPU 3:
  driver: amd-pstate-epp
  CPUs which run at the same hardware frequency: 3
  CPUs which need to have their frequency coordinated by software: 3
  energy performance preference: power
  hardware limits: 625 MHz - 2.00 GHz
  available cpufreq governors: performance powersave
  current policy: frequency should be within 625 MHz and 2.00 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency: Unable to call hardware
  current CPU frequency: 1.42 GHz (asserted by call to kernel)
  boost state support:
    Supported: yes
    Active: no
  amd-pstate limits:
    Highest Performance: 137. Maximum Frequency: 3.43 GHz.
    Nominal Performance: 80. Nominal Frequency: 2.00 GHz.
    Lowest Non-linear Performance: 25. Lowest Non-linear Frequency: 625 MHz.
    Lowest Performance: 25. Lowest Frequency: 599 MHz.
    Preferred Core Support: 1. Preferred Core Ranking: 137.

I am currently using ppd with current mode being power_save