[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20220928182037.41880C433D6@smtp.kernel.org>
Date: Wed, 28 Sep 2022 11:20:35 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Abel Vesa <abelvesa@...nel.org>,
Fabio Estevam <festevam@...il.com>, Han Xu <han.xu@....com>,
Michael Turquette <mturquette@...libre.com>,
NXP Linux Team <linux-imx@....com>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
Sascha Hauer <s.hauer@...gutronix.de>,
Shawn Guo <shawnguo@...nel.org>,
linux-arm-kernel@...ts.infradead.org, linux-clk@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: miquel.raynal@...tlin.com, linux-mtd@...ts.infradead.org,
han.xu@....com
Subject: Re: [PATCH v2] clk: imx: imx6sx: remove the SET_RATE_PARENT flag for QSPI clocks
Quoting Han Xu (2022-09-15 08:09:59)
> There is no dedicate parent clock for QSPI so SET_RATE_PARENT flag
> should not be used. For instance, the default parent clock for QSPI is
> pll2_bus, which is also the parent clock for quite a few modules, such
> as MMDC, once GPMI NAND set clock rate for EDO5 mode can cause system
> hang due to pll2_bus rate changed.
>
> Fixes: f1541e15e38e ("clk: imx6sx: Switch to clk_hw based API")
> Signed-off-by: Han Xu <han.xu@....com>
>
> ---
Applied to clk-fixes
Powered by blists - more mailing lists