search

retronx-team / sys-clk

Nintendo Switch homebrew overclocking/underclocking system module and frontend
Other
892 stars 68 forks source link

[Feature Request] Smart Boost Mode Handling #18

Closed IBNobody closed 4 years ago

IBNobody commented 4 years ago

Can sys-clk be tuned to better handle boost mode? When the Switch enters boost mode for loading (1785 CPU / 76 GPU), sys-clk resets the clocks to overridden values on the next polling interval.

Current behavior:

If I am overclocking at 1224 / 768 and enter a loading screen, the switch will jump to 1785 / 76 and then switch back to 1224 / 768.

Ideal Behavior:

If I am overclocking at 1224 / 768 and enter a loading screen, the switch will jump to 1785 / 76. Sys-clk detects this and stops overriding the clock. When the CPU and GPU clocks change after exiting boost mode (CPU != 1785, GPU != 76), sys-clk should resume overriding tle clocks at 1224 / 768.

(My current work-around is to not overclock the CPU and to only overclock the GPU. This causes the CPU to boost up to 1785 but keeps the GPU at 768. Not ideal, but the title I am using it with is not GPU intensive during loading screens.)

p-sam commented 4 years ago

Hey,

This is a duplicate of a discussion that went on in gbatemp multiple times:

References: https://gbatemp.net/threads/sys-clk-under-overclocking-sysmodule.531372/page-28#post-8852404 https://gbatemp.net/threads/sys-clk-under-overclocking-sysmodule.531372/page-29#post-8866580

IBNobody commented 4 years ago

So it's a conceptual denial, but not a technical one? (Meaning, if I fork and change how the line if (hz != this->context->freqs[module] && this->context->enabled) handles boost mode, I could get it to work? I'm asking because I wanted to know if it was worth my time pursuing this.)

p-sam commented 4 years ago

Basically, discussion already happened in the links -> not worth the time

IBNobody commented 4 years ago

I did check out the links, but what I saw was that this kind of change was not in the spirit of the tool, and I didn't come across anything that said that this wouldn't work.

On Sun, Mar 15, 2020, 12:20 PM Samuel P. notifications@github.com wrote:

Basically, discussion already happened in the links -> not worth the time

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/retronx-team/sys-clk/issues/18#issuecomment-599239060, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABMXTUBNAW74226JTRJW533RHUE53ANCNFSM4LLD6FIQ .