[PATCH 0/2] mmc: Make sure clk_init_data is fully initialized

[Ulf Hansson]

On Fri, Aug 21, 2026 at 12:06 PM Geert Uytterhoeven
<geert+renesas at glider.be> wrote:
>
>         Hi all,
>
> The clk_init_data structure contains several mutually-exclusive members
> for different methods to specify the possible parents of a clock,
> prompting drivers to initialize only the members they need.  However,
> not initializing all members may cause subtle issues, which are only
> exposed when CONFIG_INIT_STACK_ALL_PATTERN or CONFIG_INIT_STACK_NONE is
> enabled.
>
> Hence this series aims to make sure all members are fully initialized,
> to avoid such bugs, and to prevent future breakage when converting
> drivers to a different method for specifying the parents.
>
> Part One[1] fixed all cases that I identified to be real bugs, in
> response to a crash I saw on BeagleBone Black.
>
> This series is the MMC subpart of Part Two, which fixes remaining cases
> that are currently harmless.  These are still fragile, and may cause
> future breakage when converting drivers to a different method for
> specifying the parents.
>
> Thanks for your comments!
>
> [1] "[PATCH treewide 0/5] clk: Make sure clk_init_data is fully
>      initialized (part 1)"
>     https://lore.kernel.org/cover.1787165329.git.geert+renesas@glider.be
>
> Geert Uytterhoeven (2):
>   mmc: meson-gx: FIXME: Make sure clk_init_data is fully initialized
>   mmc: sdhci-of-arasan: Make sure clk_init_data is fully initialized
>
>  drivers/mmc/host/meson-gx-mmc.c    | 2 +-
>  drivers/mmc/host/sdhci-of-arasan.c | 4 ++--
>  2 files changed, 3 insertions(+), 3 deletions(-)
>
> --

The series applied for next, thanks!

Kind regards
Uffe