Hi Derek and Denis, Let us be civil. If I could have bug reported you I would have bug reported you. However, for some weird coincidence, I do not have access to the ShadowBlip bug tracker or the relevant communities. Nevertheless, this is not relevant public discussion. Let us refrain from this discussion further, including e.g., name-calling. The MCU of the Ally is the embedded microcontroller that runs the RGB and the controller of the Ally. Therefore, the discussion of the MCU powersave and wake is relevant here. What is not proper is that I should also have replied to the original patch. I admitted that much in my original email. However, since you are now aware of it, I trust that you can block the patch for merging until you review it. If the patch does not function under normal operation, this is relevant here. It means this extended patchset is built on reliance of the broken patch, which raises questions. Nevertheless, calling the patchset "experimental" is hearsay. Therefore, I will refer to it as ambitious from now on :). > This is 100% an issue with your software. I just completed an exhaustive > battery of testing at 8w STAPM/FPPT/SPPT on Quiet power profile with only > 2 cores active. The tests included using Steam by itself and the kernel > implementation, as well as running InputPlumber (which also has an > 80ms delay). Please refrain from name-calling. I was very specific to say that the issue here is that under load when in a game, Steam will either let A leak through to the game or not respond, sporadically. While in Steam UI the combination always works, regardless of TDP. Since you did not test while in a game, this renders your test invalid. To save you some additional invalid testing for the other issues: using ryzenadj on the Ally causes misbehavior, especially after suspend, where the TDP will reset. In addition, modifying SMP and core parking can freeze the Ally during suspend. Therefore, for further testing, I expect you to disable your "PowerStation" application and instead use the low-power platform profile, which is provided by asus-wmi, and is the vendor specific way for setting TDP on the Ally. Or use asusctl, which does the same. As for using direct HID commands to program RGB, asusctl does the same, including many other userspace apps, and prior to this patchset there was no way to do different, so I do not see the problem here. Best, Antheas
