Hi Lee, On Fri, 27 Feb 2015, Lee Jones wrote: > Lots of platforms contain clocks which if turned off would prove fatal. > The only way to recover is to restart the board(s). This driver takes > references to clocks which are required to be always-on in order to > prevent the common clk framework from trying to turn them off during > the clk_disabled_unused() procedure. > In this patch we are identifying clocks, which if gated would render > the STiH410 development board unserviceable. Can you also add <clk_s_c0_flexgen CLK_PROC_STFE> to the list of always on clocks for stih407 and stih410? This clock is slightly unusual in that the clock doesn't need to be on at boot, but once enabled by the kernel, can't be disabled without causing the system to hang. So slightly different from the others, but I would prefer to keep balanced enable/disable calls in the tsin driver, in case this (bug?) goes away on future SoC's. regards, Peter. -- 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
