[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87jzbqtfc3.fsf@bootlin.com>
Date: Mon, 23 Dec 2024 19:38:20 +0100
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: Stephen Boyd <sboyd@...nel.org>
Cc: Abel Vesa <abelvesa@...nel.org>, Fabio Estevam <festevam@...il.com>,
Marek Vasut <marex@...x.de>, Michael Turquette
<mturquette@...libre.com>, Peng Fan <peng.fan@....com>, Pengutronix
Kernel Team <kernel@...gutronix.de>, Sascha Hauer
<s.hauer@...gutronix.de>, Shawn Guo <shawnguo@...nel.org>, Ying Liu
<victor.liu@....com>, Laurent Pinchart
<laurent.pinchart@...asonboard.com>, linux-clk@...r.kernel.org,
imx@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org, Abel
Vesa <abel.vesa@...aro.org>, Herve Codina <herve.codina@...tlin.com>,
Luca Ceresoli <luca.ceresoli@...tlin.com>, Thomas Petazzoni
<thomas.petazzoni@...tlin.com>, Ian Ray <ian.ray@...com>
Subject: Re: [PATCH 4/5] clk: Add flag to prevent frequency changes when
walking subtrees
Hi Stephen,
>> +/* do not passively change this clock rate during subtree rate propagation */
>> +#define CLK_NO_RATE_CHANGE_DURING_PROPAGATION BIT(14)
>
> Why doesn't rate locking work?
Can you be more specific? What function from the API is supposed to do
what I need? AFAIU, none of them is properly locking the rate during a
subtree walk, but if I misread one of them, I'd be glad to drop all this.
Thanks,
Miquèl
Powered by blists - more mailing lists