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

On Fri, 21 Aug 2026 12:04:05 +0200
Geert Uytterhoeven <[email protected]> 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 IIO 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/[email protected]

Applied to the testing branch of iio.git.

I made a trivial tweak from {} to { } to follow the style we are trying
to stick to for these in IIO.

Thanks,

Jonathan

> 
> Geert Uytterhoeven (2):
>   iio: adc: meson-saradc: Make sure clk_init_data is fully initialized
>   iio: frequency: adf4350: Make sure clk_init_data is fully initialized
> 
>  drivers/iio/adc/meson_saradc.c  | 2 +-
>  drivers/iio/frequency/adf4350.c | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
>