-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: add option to disable GPU frequency scaling #1308
Comments
On a Pi with onboard Bluetooth, |
I tried it, it doesn't work to me
And I'm unsure if |
You are correct - the two are incompatible. disable-bt effectively turns a BT Pi into a non-BT Pi, at which point the clock-fixing is disabled. Although I'm not yet convinced about the choice of name, I think this would be a useful addition - particularly now that Pi 4 uses different clock speeds. |
English is not my native language, I completely rely on your choice of name. |
@popcornmix To be maximally useful we need two options - one to fix the core clock at the highest supported frequency, and one to fix it at the lowest. How about |
In relation to raspberrypi/linux#3381, there should also be a way of setting the value from Device Tree. |
just want to confirm - is there currently a way to disable GPU scaling on the RPi 4? I am also looking for optimal settings for SPI usage, also disabled bluetooth and using uarts referring to https://www.raspberrypi.org/documentation/configuration/config-txt/overclocking.md
So correct me if I'm wrong, we'll currently have to do Appreciate any input, thanks! |
For an unchanging core clock, the absolute max/min values chosen for the core frequency don't matter - only that they are the same. Choose the absolute values appropriately for the platform and the workload - 500 on the Pi 4 is likely to be fine:
|
I see. I tried this
and confirmed that I'm confused why the documentation states for
https://www.raspberrypi.org/documentation/configuration/config-txt/overclocking.md |
@edo1 think that
does the trick to keep arm clock at 1500MHz and everything else at lowest 250MHz on the RPi 4 |
That page is currently under review. |
@JamesH65 thanks for pointing that out. I've added this note to the PR |
What about
? |
Those settings are declared to be integers, with standard integer parsing code, so that scheme won't work without some hackery. |
ok, |
hi there, I tried |
guys this is so painful, @pelwell is there a simple way to disable SPI frequency change, rpi 3 SPI frequency is constant, rpi 4 keeps scaling down by 1/2, 1/4, 1/8 multipliers very randomly and causes all kinds of problems with the attached device, here's what I have in my
I even tried different values for |
Those settings have to be on separate lines. Setting force_turbo=1 should be sufficient on its own, provided you aren't thermal throttling or undervolting. Another way is to add But yes, there should be an easier way - I'm thinking |
Thanks @pelwell , the settings are on different lines (displayed problem in comment), I already had I'm trying some experiments (comment out enable_uart), also changing frequencies to zero like your suggestion, I will update with my findings, I do have the latest eeprom (beta) flashed
|
I must not have been clear enough in what I said - the There was a problem recently where the frequency lock wasn't being honoured - I suggest you use
The |
On second thoughts - leave the rpi-update until after you've edited your config.txt as advised and run the measure_clock test. If you see the same frequency in both cases then there is no reason to update. |
I do have a question, what clock source does the SPI block take, gpu or core? |
SPI, like I2C, is run from the core clock, hence |
@pelwell , I'm sorry I didn't clarify, I'm using a RPi 4 |
I know it's a Pi 4, otherwise you wouldn't have an EEPROM version. My comments still apply. The core clock is also known as the VPU clock, as it is the main processor clock for the VideoCore processor. |
I'd like to report back on the findings, after |
Is there an estimate for when this feature will be implemented? I'm maintaining the pigpio library and it would be really useful to have - Bump @popcornmix |
Does |
It stops "auto" boosts, caused by running gpu jobs that require higher clocks (high resolution/framerate hardware video decode, encode, deinterlace). |
I need stable core clock frequency because SPI bus is used.
I use my PRi in headless mode, so GPU performance doesn't matter to me. And I prefer to keep GPU power consumption as low as possible.
I want to use max (non-overcocked) CPU frequency. At least with performance governor RPi boots faster. And idle temperature difference between 600MHz and 1400MHz is only 0.5-1℃ on 3B+.
There is my current config, it works on RPi 3B+:
I dislike explicit frequency setting, I'm unsure if it is compatible with RPi 4 and future models.
What about new option? Something like
gpu_turbo=0
would be fine.The text was updated successfully, but these errors were encountered: