Messages in this thread | | | Date | Wed, 27 Mar 2024 08:09:44 +0000 | Subject | Re: [PATCH v2 1/3] clk: samsung: introduce nMUX for MUX clks that can reparented | From | Tudor Ambarus <> |
| |
On 3/26/24 17:43, André Draszik wrote: > Hi Tudor, >
Hi, Andre'!
> On Tue, 2024-03-26 at 17:28 +0000, Tudor Ambarus wrote: >> All samsung MUX clocks that are defined with MUX() set the >> CLK_SET_RATE_NO_REPARENT flag in __MUX(), which prevents MUXes to be >> reparented during clk_set_rate(). >> >> Introduce nMUX() for MUX clocks that can be reparented. > > What does n in nMUX stand for?
I thought about using the common terminology, "n-to-1 multiplexer", where n is the number of select lines. I'm open to other suggestions if there are any. I should have specified the naming scheme in the commit message, will do in the next version. > >> [...] >> >> +/* Used by MUX clocks where reparenting is allowed. */ >> +#define __nMUX(_id, cname, pnames, o, s, w, f, mf) \ >> + { \ >> + .id = _id, \ >> + .name = cname, \ >> + .parent_names = pnames, \ >> + .num_parents = ARRAY_SIZE(pnames), \ >> + .flags = f, \ >> + .offset = o, \ >> + .shift = s, \ >> + .width = w, \ >> + .mux_flags = mf, \ >> + } > > You've duplicated __MUX() and removed the CLK_SET_RATE_NO_REPARENT > from flags - I think it would make sense to instead drop the flag > from the existing __MUX(), and adjust the only two existing users > of the macro, i.e. to add it in MUX() and MUX_F(). >
Yes, I find the suggestion good. Will do in v3.
Thanks, ta
| |