-
Notifications
You must be signed in to change notification settings - Fork 29
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
Further increase minimum CPU voltage to 1.2V #330
Conversation
This change, when applied, changes the OPP voltages for both 144MHz and 312MHz from 1V to 1.2V when creating Openvario images. This fixes freezes previously encountered. It is a "follow up" change to PR #324. It turned out that even at 1.1V OV occasionally crashed. For more information on the why and how of this change please see comment in PR #324
I think commit messages should refer to commit ids, not to PR numbers, because those are proprietary GitHub things out of git's scope |
I think further increasing voltage for the low frequencies is good but avoiding them by additionally setting a minimum frequency of >400MHz like in the old 3.4 kernel images would be even better. |
You don't need to recompile or change the kernel to change minimum/maximum frequencies; just set |
@mihu - my idea (and I am currently working on it) is to add a separate "fix cpu freq" service to systemd (simple service - one time run) running a shell script with a set frequency (just like @MaxKellermann just commented). Currently trying to understand how I include that into the bitbake logic of OV.... |
This change, when applied, changes the OPP voltages for both 144MHz and 312MHz from 1V to 1.2V when creating Openvario images. This fixes freezes previously encountered. It is a "follow up" change to PR #324. It turned out that even at 1.1V OV occasionally crashed. For more information on the why and how of this change please see comment in commit #0426cb7023a415d2c4645d19ec54f9462579bd5c
…nd 312MHz from 1V to 1.2V when creating Openvario images. This fixes freezes previously encountered. It is a "follow up" change to commit 0426cb7. It turned out that even at 1.1V OV occasionally crashed. For more information on the why and how of this change please see comment in PR
…nd 312MHz from 1V to 1.2V when creating Openvario images. This fixes freezes previously encountered. It is a "follow up" change to commit 0426cb7. It turned out that even at 1.1V OV occasionally crashed. For more information on the why and how of this change please see comment in PR Also corrected a missing \ in the linux bb file I had accidentally deleted.
This change, when applied, changes the OPP voltages for both 144MHz and 312MHz from 1V to 1.2V when creating Openvario images. This fixes freezes previously encountered. It is a "follow up" change to PR #324. It turned out that even at 1.1V OV occasionally crashed. For more information on the why and how of this change please see comment in #0426cb7023a415d2c4645d19ec54f9462579bd5c
Can someone merge this and this PR, please? |
@tb59427 : There are conficts in the PR. Can you please fix this ? |
Same situation as with the other commit: github says "Only those with write access to this repository can merge pull requests." And "resolve conflicts" is greyed out for me. |
This change, when applied, changes the OPP voltages for both 144MHz and 312MHz from 1V to 1.2V when creating Openvario images. This fixes freezes previously encountered. It is a "follow up" change to PR #324. It turned out that even at 1.1V OV occasionally crashed.
For more information on the why and how of this change please see comment in PR #324