[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <169200755848.527063.16780652057592961020.b4-ty@linaro.org>
Date: Mon, 14 Aug 2023 13:09:57 +0300
From: Abel Vesa <abel.vesa@...aro.org>
To: Abel Vesa <abelvesa@...nel.org>, Peng Fan <peng.fan@....com>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
Fabio Estevam <festevam@...il.com>,
NXP Linux Team <linux-imx@....com>,
Ahmad Fatoum <a.fatoum@...gutronix.de>
Cc: Peng Fan <peng.fan@....nxp.com>, linux-clk@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] clk: imx: composite-8m: fix clock pauses when set_rate would be a no-op
On Mon, 07 Aug 2023 10:22:00 +0200, Ahmad Fatoum wrote:
> Reconfiguring the clock divider to the exact same value is observed
> on an i.MX8MN to often cause a longer than usual clock pause, probably
> because the divider restarts counting whenever the register is rewritten.
>
> This issue doesn't show up normally, because the clock framework will
> take care to not call set_rate when the clock rate is the same.
> However, when we reconfigure an upstream clock, the common code will
> call set_rate with the newly calculated rate on all children, e.g.:
>
> [...]
Applied, thanks!
[1/1] clk: imx: composite-8m: fix clock pauses when set_rate would be a no-op
commit: 4dd432d985ef258e3bc436e568fba4b987b59171
Best regards,
--
Abel Vesa <abel.vesa@...aro.org>
Powered by blists - more mailing lists