Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Personally I'm against this hand-holding (you already require root permissions to overclock at all) and think that the whole block of code gotta go but if you wanna keep this at least use some more realistic numbers. I can personally do 140/2790 (150 clock crashes, 2800 vram has artifacts) but I've seen people comfortably at 250 clock so 300 should be a good upper bound.
I would also suggest that instead of failing at all to just do a
max(config_get_nv_core_clock_mhz_offset(), 300)
but that would require a few more changes.