Message ID | 1416925325.26128.6.camel@AMDC1943 (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Hello Krzysztof, On 11/25/2014 03:22 PM, Krzysztof Kozlowski wrote: >> Any ideas? > > Yes, I got. On Peach board the i2s0 is enabled in DTS. Probing it could > fail because it relies on enabling audss clocks (which cannot be > accessed). > > I reproduced another hang on Arndale Octa after enabling i2s0 in DTS. > Maybe that is the cause also on Peach. > You are correct, if I disable i2s0 then I see the logs from clk_disable_unused_subtree() and boot hangs when accessing the adma clock: clk: checking dout_fimd1 clk: checking mout_fimd1_final clk: checking mout_fimd1 clk: checking mout_sclk_rpll clk: checking fout_rpll clk: checking adma With i2s0 disabled, your series are indeed enough to make it boot again but as you said enabling i2s0 in the DTS makes it hang even with your patches. Thanks a lot for digging into this! Best regards, Javier -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On wto, 2014-11-25 at 15:52 +0100, Javier Martinez Canillas wrote: > Hello Krzysztof, > > On 11/25/2014 03:22 PM, Krzysztof Kozlowski wrote: > >> Any ideas? > > > > Yes, I got. On Peach board the i2s0 is enabled in DTS. Probing it could > > fail because it relies on enabling audss clocks (which cannot be > > accessed). > > > > I reproduced another hang on Arndale Octa after enabling i2s0 in DTS. > > Maybe that is the cause also on Peach. > > > > You are correct, if I disable i2s0 then I see the logs from > clk_disable_unused_subtree() and boot hangs when accessing the adma clock: > > clk: checking dout_fimd1 > clk: checking mout_fimd1_final > clk: checking mout_fimd1 > clk: checking mout_sclk_rpll > clk: checking fout_rpll > clk: checking adma > > With i2s0 disabled, your series are indeed enough to make it boot again but > as you said enabling i2s0 in the DTS makes it hang even with your patches. > > Thanks a lot for digging into this! My patch only fixed the gate clocks but it didn't touched div and mux. I'll prepare a v2 of it (I got some feedback) which I hope will fix both cases: i2s and disabling unused clocks. Best regards, Krzysztof -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hello Krzysztof, On 11/25/2014 03:54 PM, Krzysztof Kozlowski wrote: > > My patch only fixed the gate clocks but it didn't touched div and mux. > I'll prepare a v2 of it (I got some feedback) which I hope will fix both > cases: i2s and disabling unused clocks. > Perfect, I will gladly test on Peach boards once you post it. Thanks a lot for your help. Best regards, Javier -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
From def8df7c5d8098ec1656c075701e9ba17f0617c9 Mon Sep 17 00:00:00 2001 From: Krzysztof Kozlowski <k.kozlowski@samsung.com> Date: Thu, 6 Nov 2014 12:58:07 +0100 Subject: [PATCH] Very early printk, for next-20141106 (3.19?) Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com> --- kernel/printk/printk.c | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c index 1b7092dbb590..269318013504 100644 --- a/kernel/printk/printk.c +++ b/kernel/printk/printk.c @@ -1708,6 +1708,13 @@ asmlinkage int vprintk_emit(int facility, int level, } } + if (1) { + extern void printascii(const char *); + printascii(text); + printed_len = 0; + goto early_printk_out; + } + if (level == LOGLEVEL_DEFAULT) level = default_message_loglevel; @@ -1754,6 +1761,7 @@ asmlinkage int vprintk_emit(int facility, int level, dict, dictlen, text, text_len); } +early_printk_out: logbuf_cpu = UINT_MAX; raw_spin_unlock(&logbuf_lock); lockdep_on(); -- 1.9.1