Re: [PATCH v3 00/65] clk: Make determine_rate mandatory for muxes

2023-04-25 Thread Maxime Ripard
On Thu, Apr 13, 2023 at 02:44:51PM -0700, Stephen Boyd wrote: > Quoting Maxime Ripard (2023-04-04 03:10:50) > > Hi, > > > > This is a follow-up to a previous series that was printing a warning > > when a mux has a set_parent implementation but is missing > > determine_rate(). > > > > The rational

Re: [PATCH v3 00/65] clk: Make determine_rate mandatory for muxes

2023-04-13 Thread Stephen Boyd
Quoting Maxime Ripard (2023-04-04 03:10:50) > Hi, > > This is a follow-up to a previous series that was printing a warning > when a mux has a set_parent implementation but is missing > determine_rate(). > > The rationale is that set_parent() is very likely to be useful when > changing the rate, b

[PATCH v3 00/65] clk: Make determine_rate mandatory for muxes

2023-04-04 Thread Maxime Ripard
Hi, This is a follow-up to a previous series that was printing a warning when a mux has a set_parent implementation but is missing determine_rate(). The rationale is that set_parent() is very likely to be useful when changing the rate, but it's determine_rate() that takes the parenting decision.