diff for duplicates of <1498664332.2337.6.camel@baylibre.com> diff --git a/a/1.txt b/N1/1.txt index 120a1d0..6f1d899 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -15,26 +15,26 @@ On Wed, 2017-06-28 at 16:04 +0100, Sudeep Holla wrote: bL cpu freq driver requesting the cpu clock, which failed to register. Here the Oops call trace: -[ 2.202284] [<ffff00000849a058>] __clk_create_clk.part.18+0x68/0xb0 -[ 2.208494] [<ffff00000849ac2c>] __of_clk_get_from_provider+0xfc/0x140 -[ 2.214962] [<ffff000008496c28>] __of_clk_get_by_name+0x100/0x118 -[ 2.220999] [<ffff000008496c94>] clk_get+0x2c/0x78 -[ 2.225744] [<ffff000008570110>] dev_pm_opp_get_opp_table+0xb0/0x118 -[ 2.232039] [<ffff000008570940>] dev_pm_opp_add+0x20/0x68 -[ 2.237388] [<ffff0000087a0f30>] scpi_init_opp_table+0xa8/0x188 -[ 2.243252] [<ffff0000087a0558>] _get_cluster_clk_and_freq_table+0x80/0x180 -[ 2.250151] [<ffff0000087a0a48>] bL_cpufreq_init+0x3f0/0x480 -[ 2.255758] [<ffff00000879eed8>] cpufreq_online+0xc0/0x658 -[ 2.261191] [<ffff00000879f500>] cpufreq_add_dev+0x78/0x88 -[ 2.266625] [<ffff00000855c2c4>] subsys_interface_register+0x84/0xc8 -[ 2.272922] [<ffff00000879e330>] cpufreq_register_driver+0x138/0x1b8 -[ 2.279218] [<ffff0000087a0b4c>] bL_cpufreq_register+0x74/0x120 -[ 2.285083] [<ffff0000087a1038>] scpi_cpufreq_probe+0x28/0x38 -[ 2.290776] [<ffff00000855fbf0>] platform_drv_probe+0x50/0xb8 -[ 2.296468] [<ffff00000855dd84>] driver_probe_device+0x21c/0x2d8 +[????2.202284] [<ffff00000849a058>] __clk_create_clk.part.18+0x68/0xb0 +[????2.208494] [<ffff00000849ac2c>] __of_clk_get_from_provider+0xfc/0x140 +[????2.214962] [<ffff000008496c28>] __of_clk_get_by_name+0x100/0x118 +[????2.220999] [<ffff000008496c94>] clk_get+0x2c/0x78 +[????2.225744] [<ffff000008570110>] dev_pm_opp_get_opp_table+0xb0/0x118 +[????2.232039] [<ffff000008570940>] dev_pm_opp_add+0x20/0x68 +[????2.237388] [<ffff0000087a0f30>] scpi_init_opp_table+0xa8/0x188 +[????2.243252] [<ffff0000087a0558>] _get_cluster_clk_and_freq_table+0x80/0x180 +[????2.250151] [<ffff0000087a0a48>] bL_cpufreq_init+0x3f0/0x480 +[????2.255758] [<ffff00000879eed8>] cpufreq_online+0xc0/0x658 +[????2.261191] [<ffff00000879f500>] cpufreq_add_dev+0x78/0x88 +[????2.266625] [<ffff00000855c2c4>] subsys_interface_register+0x84/0xc8 +[????2.272922] [<ffff00000879e330>] cpufreq_register_driver+0x138/0x1b8 +[????2.279218] [<ffff0000087a0b4c>] bL_cpufreq_register+0x74/0x120 +[????2.285083] [<ffff0000087a1038>] scpi_cpufreq_probe+0x28/0x38 +[????2.290776] [<ffff00000855fbf0>] platform_drv_probe+0x50/0xb8 +[????2.296468] [<ffff00000855dd84>] driver_probe_device+0x21c/0x2d8 But that's not the point. The point is there is path in clk-scpi driver which -registers uninitialized data in the clock provider. That's not good. +registers uninitialized data in the clock provider. That's not good.? > Also one of the reason for keeping it continuing is, if firmware fails > on some non-critical clock, that's fine rather than punishing the entire diff --git a/a/content_digest b/N1/content_digest index 8333455..086cd79 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,16 +1,9 @@ "ref\020170628135345.9337-1-jbrunet@baylibre.com\0" "ref\0c7123c06-b75b-5209-5817-230c63c1bf49@arm.com\0" - "From\0Jerome Brunet <jbrunet@baylibre.com>\0" - "Subject\0Re: [PATCH] clk: scpi: error when clock fails to register\0" + "From\0jbrunet@baylibre.com (Jerome Brunet)\0" + "Subject\0[PATCH] clk: scpi: error when clock fails to register\0" "Date\0Wed, 28 Jun 2017 17:38:52 +0200\0" - "To\0Sudeep Holla <sudeep.holla@arm.com>" - Michael Turquette <mturquette@baylibre.com> - " Stephen Boyd <sboyd@codeaurora.org>\0" - "Cc\0linux-arm-kernel@lists.infradead.org" - linux-clk@vger.kernel.org - linux-kernel@vger.kernel.org - Neil Armstrong <narmstrong@baylibre.com> - " Kevin Hilman <khilman@baylibre.com>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "On Wed, 2017-06-28 at 16:04 +0100, Sudeep Holla wrote:\n" @@ -30,26 +23,26 @@ "bL cpu freq driver requesting the cpu clock, which failed to register. Here the\n" "Oops call trace:\n" "\n" - "[\302\240\302\240\302\240\302\2402.202284] [<ffff00000849a058>] __clk_create_clk.part.18+0x68/0xb0\n" - "[\302\240\302\240\302\240\302\2402.208494] [<ffff00000849ac2c>] __of_clk_get_from_provider+0xfc/0x140\n" - "[\302\240\302\240\302\240\302\2402.214962] [<ffff000008496c28>] __of_clk_get_by_name+0x100/0x118\n" - "[\302\240\302\240\302\240\302\2402.220999] [<ffff000008496c94>] clk_get+0x2c/0x78\n" - "[\302\240\302\240\302\240\302\2402.225744] [<ffff000008570110>] dev_pm_opp_get_opp_table+0xb0/0x118\n" - "[\302\240\302\240\302\240\302\2402.232039] [<ffff000008570940>] dev_pm_opp_add+0x20/0x68\n" - "[\302\240\302\240\302\240\302\2402.237388] [<ffff0000087a0f30>] scpi_init_opp_table+0xa8/0x188\n" - "[\302\240\302\240\302\240\302\2402.243252] [<ffff0000087a0558>] _get_cluster_clk_and_freq_table+0x80/0x180\n" - "[\302\240\302\240\302\240\302\2402.250151] [<ffff0000087a0a48>] bL_cpufreq_init+0x3f0/0x480\n" - "[\302\240\302\240\302\240\302\2402.255758] [<ffff00000879eed8>] cpufreq_online+0xc0/0x658\n" - "[\302\240\302\240\302\240\302\2402.261191] [<ffff00000879f500>] cpufreq_add_dev+0x78/0x88\n" - "[\302\240\302\240\302\240\302\2402.266625] [<ffff00000855c2c4>] subsys_interface_register+0x84/0xc8\n" - "[\302\240\302\240\302\240\302\2402.272922] [<ffff00000879e330>] cpufreq_register_driver+0x138/0x1b8\n" - "[\302\240\302\240\302\240\302\2402.279218] [<ffff0000087a0b4c>] bL_cpufreq_register+0x74/0x120\n" - "[\302\240\302\240\302\240\302\2402.285083] [<ffff0000087a1038>] scpi_cpufreq_probe+0x28/0x38\n" - "[\302\240\302\240\302\240\302\2402.290776] [<ffff00000855fbf0>] platform_drv_probe+0x50/0xb8\n" - "[\302\240\302\240\302\240\302\2402.296468] [<ffff00000855dd84>] driver_probe_device+0x21c/0x2d8\n" + "[????2.202284] [<ffff00000849a058>] __clk_create_clk.part.18+0x68/0xb0\n" + "[????2.208494] [<ffff00000849ac2c>] __of_clk_get_from_provider+0xfc/0x140\n" + "[????2.214962] [<ffff000008496c28>] __of_clk_get_by_name+0x100/0x118\n" + "[????2.220999] [<ffff000008496c94>] clk_get+0x2c/0x78\n" + "[????2.225744] [<ffff000008570110>] dev_pm_opp_get_opp_table+0xb0/0x118\n" + "[????2.232039] [<ffff000008570940>] dev_pm_opp_add+0x20/0x68\n" + "[????2.237388] [<ffff0000087a0f30>] scpi_init_opp_table+0xa8/0x188\n" + "[????2.243252] [<ffff0000087a0558>] _get_cluster_clk_and_freq_table+0x80/0x180\n" + "[????2.250151] [<ffff0000087a0a48>] bL_cpufreq_init+0x3f0/0x480\n" + "[????2.255758] [<ffff00000879eed8>] cpufreq_online+0xc0/0x658\n" + "[????2.261191] [<ffff00000879f500>] cpufreq_add_dev+0x78/0x88\n" + "[????2.266625] [<ffff00000855c2c4>] subsys_interface_register+0x84/0xc8\n" + "[????2.272922] [<ffff00000879e330>] cpufreq_register_driver+0x138/0x1b8\n" + "[????2.279218] [<ffff0000087a0b4c>] bL_cpufreq_register+0x74/0x120\n" + "[????2.285083] [<ffff0000087a1038>] scpi_cpufreq_probe+0x28/0x38\n" + "[????2.290776] [<ffff00000855fbf0>] platform_drv_probe+0x50/0xb8\n" + "[????2.296468] [<ffff00000855dd84>] driver_probe_device+0x21c/0x2d8\n" "\n" "But that's not the point. The point is there is path in clk-scpi driver which\n" - "registers uninitialized data in the clock provider. That's not good.\302\240\n" + "registers uninitialized data in the clock provider. That's not good.?\n" "\n" "> Also one of the reason for keeping it continuing is, if firmware fails\n" "> on some non-critical clock, that's fine rather than punishing the entire\n" @@ -65,4 +58,4 @@ "If you have a better solution later on, I don't think there would be any problem\n" to revert this patch. -01339fa8de5a1c63964b421e0bc02b966c544903a69abb7fea605cd51121170b +2d49ef57ca3ab2fbe819a89150bf167c534eae75f36f2fc7ecafbbc446a6fcec
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.