On 8/10/2023 6:23 PM, Nishanth Menon wrote:
On 17:23-20230810, Kumar, Udit wrote: [..]+ opp1-750000000 { + opp-hz = /bits/ 64 <750000000>; }; }; -- 2.34.1[..] This wont work: a) in u-boot's falcon boot mode and puts unrelated responsibility to bootloader (u-boot is not the only bootloader in the party here). b) Further, the reason for doing the opp detection in the kernel is due to the severity of consequence of attempting to run a lower rated chip at higher frequency - PoH (Power on Hours) or physical damage can result. c) Finally, in a virtualized environment: TISCI will get DM (Device Manager) to arbitrate between the each of the VM's request, but if the VM's are'nt self sufficient, we will have DM making wrong choices resulting in (b) condition again. This is the reason why drivers/cpufreq/ti-cpufreq.c exists and all SoCs that have OPPs from TI is handled in the kernel itself.
Thanks to pointing to this driver.
