Message ID | 1564384997-16775-1-git-send-email-abel.vesa@nxp.com (mailing list archive) |
---|---|
State | Mainlined |
Commit | 9b9c60bed562c3718ae324a86f3f30a4ff983cf8 |
Headers | show |
Series | [v2] clk: imx8mq: Mark AHB clock as critical | expand |
Hi Abel, On Mon, Jul 29, 2019 at 4:23 AM Abel Vesa <abel.vesa@nxp.com> wrote: > > Keep the AHB clock always on since there is no driver to control it and > all the other clocks that use it as parent rely on it being always enabled. > > Signed-off-by: Abel Vesa <abel.vesa@nxp.com> > Tested-by: Daniel Baluta <daniel.baluta@nxp.com> > --- > > Changes since v1: > * added comment in code why this clock is critical > * added T-b by Daniel > > This needs to go in ASAP to fix the boot hang. Which boot hang exactly? Are you referring to the TMU clock hang? On the TMU clock hang, the issue was that the qoriq_thermal needs to enable the TMU clock. Please always provide a detailed description in the commit log. Also, if this fixes a hang it should contain a Fixes tag.
Hi Fabio, On 19-07-29 09:19:01, Fabio Estevam wrote: > Hi Abel, > > On Mon, Jul 29, 2019 at 4:23 AM Abel Vesa <abel.vesa@nxp.com> wrote: > > > > Keep the AHB clock always on since there is no driver to control it and > > all the other clocks that use it as parent rely on it being always enabled. > > > > Signed-off-by: Abel Vesa <abel.vesa@nxp.com> > > Tested-by: Daniel Baluta <daniel.baluta@nxp.com> > > --- > > > > Changes since v1: > > * added comment in code why this clock is critical > > * added T-b by Daniel > > > > This needs to go in ASAP to fix the boot hang. > > Which boot hang exactly? Are you referring to the TMU clock hang? > > On the TMU clock hang, the issue was that the qoriq_thermal needs to > enable the TMU clock. > > Please always provide a detailed description in the commit log. > > Also, if this fixes a hang it should contain a Fixes tag. Please have a the explanation here: https://lkml.org/lkml/2019/7/28/306
Hi Abel, On Mon, Jul 29, 2019 at 12:07 PM Abel Vesa <abel.vesa@nxp.com> wrote: > Please have a the explanation here: > > https://lkml.org/lkml/2019/7/28/306 I read that and it is still not clear for me: which hang exactly are you referring to in your comment below the --- line? Reading the commit log it is not clear if the patch fixes a real bug or if it is just an improvement. Please make this clear in the commit log.
diff --git a/drivers/clk/imx/clk-imx8mq.c b/drivers/clk/imx/clk-imx8mq.c index 4328c22..04302f2 100644 --- a/drivers/clk/imx/clk-imx8mq.c +++ b/drivers/clk/imx/clk-imx8mq.c @@ -406,7 +406,8 @@ static int imx8mq_clocks_probe(struct platform_device *pdev) clks[IMX8MQ_CLK_NOC_APB] = imx8m_clk_composite_critical("noc_apb", imx8mq_noc_apb_sels, base + 0x8d80); /* AHB */ - clks[IMX8MQ_CLK_AHB] = imx8m_clk_composite("ahb", imx8mq_ahb_sels, base + 0x9000); + /* AHB clock is used by the AHB bus therefore marked as critical */ + clks[IMX8MQ_CLK_AHB] = imx8m_clk_composite_critical("ahb", imx8mq_ahb_sels, base + 0x9000); clks[IMX8MQ_CLK_AUDIO_AHB] = imx8m_clk_composite("audio_ahb", imx8mq_audio_ahb_sels, base + 0x9100); /* IPG */