Messages in this thread | | | Date | Tue, 19 Sep 2023 09:07:03 +0200 | From | Maxime Ripard <> | Subject | Re: [PATCH 06/13] clk: keep track if a clock is explicitly configured |
| |
Hi,
On Mon, Sep 18, 2023 at 12:40:02AM +0200, Benjamin Bara wrote: > From: Benjamin Bara <benjamin.bara@skidata.com> > > When we keep track if a clock has a given rate explicitly set by a > consumer, we can identify unintentional clock rate changes in an easy > way. This also helps during debugging, as one can see if a rate is set > by accident or due to a consumer-related change. > > Signed-off-by: Benjamin Bara <benjamin.bara@skidata.com> > --- > drivers/clk/clk.c | 25 +++++++++++++++++++++++++ > include/linux/clk-provider.h | 1 + > 2 files changed, 26 insertions(+) > > diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c > index 8f4f92547768..82c65ed432c5 100644 > --- a/drivers/clk/clk.c > +++ b/drivers/clk/clk.c > @@ -70,6 +70,7 @@ struct clk_core { > unsigned long rate; > unsigned long req_rate; > unsigned long new_rate; > + unsigned long set_rate;
This is pretty much what req_rate is supposed to be about. Why didn't it work in your case?
Maxime [unhandled content-type:application/pgp-signature] | |