Hi Doug, On Monday 08 of April 2013 12:21:32 Doug Anderson wrote: > Kukjin, > > On Mon, Apr 8, 2013 at 11:29 AM, Kukjin Kim <kgene....@gmail.com> wrote: > > BTW, if any problems on current for-next, please kindly let me know. > > I usually try to check linux-next at least once a week, but sometimes > it's more or less often. At the moment I'm trying to track something > weird down but it seems like it has some userspace component to it. > I'll post a separate thread if I find a kernel problem there. > > Aside from the RTC, my biggest problem right now is that reboot > stopped working at the same time as the common clock. The > exynos5_restart() function is essentially behaving as a no-op since > the clock to the IP block that handles reset has been gated. :( The > bit "CLK_PMU_APBIF" is gated in "CLK_GATE_IP_PERIS". This used to be > ungated in exynos5_clk_ip_peris_ctrl(). > > I'm happy to test a patch that fixes this but I haven't yet had time > to try to fix it cleanly myself.
Common Clock Framework by default automatically gates unused clocks, just like regulator core does with unused regulators. Maybe this is the cause? There is a CLK_IGNORE_UNUSED flag which disables this behavior for all clocks which have it set. Maybe it should be set for the problematic clock? Best regards, Tomasz -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
