On 3/16/26 4:59 AM, Julien Stephan wrote: > Le lun. 9 mars 2026 à 22:29, David Lechner <[email protected]> a écrit : >> >> The MediaTek clock driver currently have two ways to indicate the parent >> tree that contains the parent clock. This adds to code complexity and >> makes it more difficult to know the "right thing" to do in new drivers. >> >> The plan here is to convert all mux clocks to use the more robust option >> of using struct mtk_parent to specify parent clocks. Then we can remove >> dead and duplicate code and macros. >> >> The conversion to the static const struct mtk_parent arrays was done >> by script to minimize the chance of error (and save time). >> >> Signed-off-by: David Lechner <[email protected]> >> --- >> Changes in v2: >> - Rebased on updated dependencies. >> - Link to v1: >> https://lore.kernel.org/r/20260302-clk-mtk-unify-mux-parents-v1-0-32f45085f...@baylibre.com >> >> --- >> David Lechner (13): >> clk: mediatek: mt7622: convert to struct mtk_parent > > Hello David, > > Is there a reason to have 2 different series to convert to struct mtk_parent? > You are already doing this kind of cleanup in [1]. Can we merge into > one single series? Specifically we end up doing this cleanup into two > commits for mt7622.. > > [1]: > https://patchwork.ozlabs.org/project/uboot/cover/20260306-clk-mtk-remove-clk-bypass-xtal-flag-v2-0-b253b49f1...@baylibre.com/ > The reason is that I didn't plan ahead so well. :-/
I didn't know that I was going to make these changes when I sent the other series. I suppose we could move the other patches to this series and swap the order of the series.
