On 10-06-19, 15:49, Viresh Kumar wrote:
On 22-05-19, 12:36, Viresh Kumar wrote:
On 22-05-19, 10:03, Ilias Apalodimas wrote:
Hi Viresh, Gregory On Mon, May 20, 2019 at 04:50:42PM +0530, Viresh Kumar wrote:
On 25-04-19, 15:33, Ilias Apalodimas wrote:
Hi Viresh,
> > Also, during this week-end, Christian suggested that the issue might > > come from the AVS support. > > > > Could you disable it and check you still have the issue? > > > > For this, you just have to remove the avs node in > > arch/arm64/boot/dts/marvell/armada-37xx.dtsi and rebuild the dtb. > Sure. You'll have to wait for a week though. Currently on a trip. I'll run that > once i return
@Ilias: Can you please try this now and confirm to Gregory ?
I am more overloaded than usual and totally forgot about this. Apologies. I'll try finding some time and do this.
Ping Ilias.
Sorry for the huge delay. Applying this patch and removing tha 'avs' node from arch/arm64/boot/dts/marvell/armada-37xx.dtsi seems to work. Changing between governors does not freeze the board any more. I haven't checked the actual impact on the CPU speed but the values on /sys/devices/system/cpu/cpufreq/policy0/scaling_governor are correct
Thanks for testing it out. Lets see what Gregory has to say now.
@Gregory: Do you have any further advice for Ilias ?
Ping.