Hi, * deffo@xxxxxx <deffo@xxxxxx> [191127 13:53]: > hi there! > > i'm using the TI OMAP4460 (VAR-SOM-OM44) and i get several errors in dmesg on the latest for-next branch: > > root@localhost:~# dmesg -l err > [ 1.146026] twl: not initialized > [ 1.146087] twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660 > [ 1.146087] twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660 > [ 1.146179] twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660 > [ 1.146209] twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660 > [ 1.146270] twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660 > [ 1.146301] twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660 > [ 1.146331] twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1410000 Vs max 1316660 > [ 1.522979] omap_dm_timer_set_source: timer_sys_ck not found Sounds like something needs fixing for sure. Similar messages seem to appear for all omap4 with twl PMIC. > which probably leads to the problem, that the cpu cannot run with more than 920 mhz. is this a known problem? Yes, see the drivers/cpufreq changes recently done for omap3: $ git log v5.4..3fbeef397212046cc514fe9fcd07e67e6ca32163 drivers/cpufreq Similar changes are also needed for omap4 to detect the supported rates. And then we also need to add a regulator controller driver for cpufreq to use that manages the voltage controller. > i need to run the cpus with 1.5 ghz, as it was possible with the v3.4 kernel, how is this possible? My guess is that v3.4 was missing some critical checks to protect the SoC :) But please do check, maybe we're missing some code that was there earlier. Regards, Tony
