Hi Fabio, On 06/12/2016 04:36 PM, Fabio Estevam wrote: > On Sun, Jun 12, 2016 at 11:05 AM, Christopher Spinrath > <christopher.spinrath@xxxxxxxxxxxxxx> wrote: > >> Well, without this patch the SoC runs at 1.2GHz so it seems like the >> fuse indicates that it is possible. But with a fair amount of IPs >> enabled and high load the board becomes unstable (display >> flickering/blanks, ethernet package drops, ...). I guess CompuLab >> allowed 1.2GHz at first and then realized that it is a bad idea (at >> least for some boards). >> >> Is there any way to influence the fuse (e.g. from the >> firmware/bootloader) or do you have another proposal on how to fix this >> issue? > > Ok, understood. So the mx6q fuse indicates that 1.2GHz operation is > possible on , but the board itself does not behave nicely at this > frequency. > > Maybe you could send a v2 of this patch that matches the operating > points form mx6qdl.dtsi and remove only the 1.2GHz entry and put the > explanation you gave us here in the dts and commit log. > Will do. Thanks, Christopher > Regards, > > Fabio Estevam > -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html