RSS Bot Posted July 10, 2023 Posted July 10, 2023 Description When booting on H3 boards with regulator-gpio, we get the following error. [ 8.518147] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 8.518188] cpu cpu0: _opp_add: OPP not supported by regulators (1104000000) [ 8.518373] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 8.518391] cpu cpu0: _opp_add: OPP not supported by regulators (1200000000) [ 8.518565] core: _opp_supported_by_regulators: OPP minuV: 1340000 maxuV: 1340000, not supported by regulator [ 8.518585] cpu cpu0: _opp_add: OPP not supported by regulators (1296000000) [ 8.518752] core: _opp_supported_by_regulators: OPP minuV: 1400000 maxuV: 1400000, not supported by regulator [ 8.518770] cpu cpu0: _opp_add: OPP not supported by regulators (1368000000) [ 9.016159] thermal_sys: Failed to bind 'cpu_thermal' with 'cpufreq-cpu0': -22 [ 9.016200] thermal_sys: Failed to bind 'cpu_thermal' with 'cpufreq-cpu0': -22 These boards have the voltage capped at 1.3Volts and can't support voltages higher than that. Because of that we get reduced from having 8 cpufreq states to just 4 states that further causes us to observe the error thrown by thermal_sys module. This PR fixes the same. Also I have disabled 1.368 Ghz operation state as in my test, my board hit the first trip in just 1 sec throttling the board down to 1.296 Ghz instantaneously. If anyone needs the same, we do have the overclock overlay for that anyway. Also enabled legacy kernel for NanoPi Duo2. How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [X] Tested that patch applies on legacy, current as well as edge kernel [X] Booted on NanoPi Duo2. Made sure error related to thermal_sys is not shown in dmesg. Also ran minerd --benchmark and monitored the system with armbianmonitor -M to make sure trips are working as expected. Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article
Recommended Posts