From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id AB772470EB5 for ; Mon, 31 Aug 2026 15:36:09 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.129.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788190571; cv=none; b=YJiHZnGaacvGEV9Xgvgq3Rzxmhu1HFenpIp6ujqJJVBujIUL+g92XLTyLrxISwoTluTDQ38QuePH9h+G6X7rTg6iJ1f0o0r4oCDmjx3jN/HQQ0nHOz5oIszVqrsisl9WeqWP8JukNmvsQCjo7w4DEggfkONvjzIMKnWknmyb2Cs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788190571; c=relaxed/simple; bh=DodOb5bu1oSMuLPsOxNFB8oK01GET+pyiMt7NsDyP0I=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=GLJHgHngeZ+yh4wzlqev0E8T+MmfG7YDuXCe5sdknLxI1YunLX8pKuR3RimeohwQigGhcPUQ2IZAmiaCP6MrGeh2QqYd6p2uphxxBzP3TweFw78SUlQitrlkRp+v9mx7KZH1d1w1OfU1UFyKCLJxGsaU2DaWxCEMlaC5ZHJhxFE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=dakA0lC1; dkim=pass (2048-bit key) header.d=redhat.com header.i=@redhat.com header.b=ewCGphf9; arc=none smtp.client-ip=170.10.129.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="dakA0lC1"; dkim=pass (2048-bit key) header.d=redhat.com header.i=@redhat.com header.b="ewCGphf9" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1788190568; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=uVxBilOuJ3eJRjLFViKxIC+i5050iOvt2YALC/2UHq4=; b=dakA0lC1O+Wx9Un543FmnQ6r29Xds96hGCtuQA0VAHdBGT4SYp21rIzYG6yTjUx4ehqvn9 c08hMuqN3YlfCLEhSC3xsVCpI50N3PWBXPbusYv/nz3G1+t0tRx0ybS8myVyb71FOJZZpU JUSv2Oq8Nn0tNxtxjBy9F1QDAWhlfUU= Received: from mail-yx1-f71.google.com (mail-yx1-f71.google.com [74.125.224.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-645-PWTwGBSHOTeBoaRY1rwlxg-1; Mon, 31 Aug 2026 11:36:06 -0400 X-MC-Unique: PWTwGBSHOTeBoaRY1rwlxg-1 X-Mimecast-MFC-AGG-ID: PWTwGBSHOTeBoaRY1rwlxg_1788190566 Received: by mail-yx1-f71.google.com with SMTP id 956f58d0204a3-66c767e23f6so4913307d50.0 for ; Mon, 31 Aug 2026 08:36:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=google; t=1788190566; x=1788795366; darn=vger.kernel.org; h=user-agent:in-reply-to:content-disposition:content-type :mime-version:references:message-id:subject:cc:to:from:date:from:to :cc:subject:date:message-id:reply-to:content-type; bh=uVxBilOuJ3eJRjLFViKxIC+i5050iOvt2YALC/2UHq4=; b=ewCGphf972PAR8+k1iRpbk/FrpS7EDIgvk+laCzpoq6oHTazz0nWGn7fL5eenQuHDk pK2aaSI3LtieJ0EDNlGLizJxmHY0iLVNgpR44zNteMSAcIYW5YhngTXGMwf2f/KOfYjE 3Wk5rTfDGf6+0AVVaXTb607fcY0Tkm0dVZy4ewwm8z/CSn07cILYFA9QJVgIF2mVs3Yq bL6kUYmFnIdGxIHuEHdJoWgrFVWmZnxufKzwK4wrmJK+1GvYVcam+ZpRI9dmjF0EGAom uErZdLe7+hzkEInBPE1SfmmDrAchECt9RKygdhev30/AXwHZJrT/GwT2EwbNichjtDM9 O1Lg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1788190566; x=1788795366; h=user-agent:in-reply-to:content-disposition:content-type :mime-version:references:message-id:subject:cc:to:from:date:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=uVxBilOuJ3eJRjLFViKxIC+i5050iOvt2YALC/2UHq4=; b=DdYLgDlYeP8BAJD1by5CLzDuuzY5ZiGTkStErUwCdxKikgggdG+qIDyTNMs2+N/8jB 0Vzah7xAA7mnBYaXAO+D1xXGJlMjsv2s9lDFfgMS8QRklD3cMfqLmPjX7elRQIHeuuus 7Bwinzaur6XimdkgnBKmPkORJNYxUndOxZMqx1DE8SoaYbHSn2lM4rS2ezGLp+/wYETI LMDv+p50vqkoWCdaNG/ZLJPfPAyXr5Y77G2PKHmLiDxgMHm39yGVp/M4kGASK9YuLTz6 3w0BKUc0VVUHff8k6OWPBLvogI2CnuNJo/KC1J0C8h+G1VKgxbfA0GOouFx1N9guuG2q V53w== X-Forwarded-Encrypted: i=1; AKwUvBwBOS7yx4ofTHdMg6KKDWXd+S0MgS/0OJDh3TmLAec3Wvm+moUhE+GPpoMVUNsbSrtfdEVOewdM+/h0Lj4=@vger.kernel.org X-Gm-Message-State: AFuF++k0wg0lMUR/0qCZRkxJ8bfROJwrzTbjwAusa7neMoZnFrvoTi4Q 8foqFO2rrtkFZDQ7HXbpdOCQ96wTAoP2EmeIlhX28NjnE2z8PkDBY6tR/E+dppfUEa1QcYP8Wcl 54H9sCl6ekrgt7SePJOpFk5M/k9ZTucT+BFnQRE9Hgtws1WeUqSYLRkfmg2+KzQ9xlA== X-Gm-Gg: AYBFou1k0ewYCDJSr52SZjcz/7X11VGUxfLES2cSwRcFwZkev+MEvqkNWaIxLLbH0kC AMn8JHyvIOoRLItLktZPaY/WPVpFjdoWo1Ym3q7BpL2ySymN3WS4oSmt1+d2J0DswDsEbkZYXIY 5ERwT5XozSrAZs7vFRLrednCH34qwf8i0jo8DILHCAn3VeKnrosZQwotuK1VQLc1S45heWxw+wC IbCOGG0xVhjj17bMXmixvG/masiPAp15OFs8VohWb997+p1/uzLGgd5PLglS3K+Q49aIkOMO/t4 AR2ZWyD2SYSsesaqdnr1DykHFMHoDRArBqlgwZHyndZm4JWrUyLzCnVpMl4OaeDwWHEY3M3JJhI = X-Received: by 2002:a05:690e:13c7:b0:66f:8255:9f3d with SMTP id 956f58d0204a3-66f873db9b1mr559439d50.7.1788190565256; Mon, 31 Aug 2026 08:36:05 -0700 (PDT) X-Received: by 2002:a05:690e:13c7:b0:66f:8255:9f3d with SMTP id 956f58d0204a3-66f873db9b1mr559344d50.7.1788190564555; Mon, 31 Aug 2026 08:36:04 -0700 (PDT) Received: from redhat.com ([2600:382:8519:3f74:ab6c:bb55:e9cb:f8d6]) by smtp.gmail.com with ESMTPSA id 956f58d0204a3-66f7efc9dbfsm2062227d50.9.2026.08.31.08.35.56 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 31 Aug 2026 08:36:03 -0700 (PDT) Date: Mon, 31 Aug 2026 11:35:55 -0400 From: Brian Masney To: Geert Uytterhoeven Cc: Ryan Chen , Joel Stanley , Stephen Boyd , Brian Masney , Jerome Brunet , Andrew Jeffery , Billy Tsai , Nicolas Ferre , Alexandre Belloni , Claudiu Beznea , Ray Jui , Scott Branden , Broadcom internal kernel review list , Taichi Sugaya , Takao Orito , Linus Walleij , Avi Fishman , Tomer Maimon , Tali Perry , Patrick Venture , Nancy Yuen , Benjamin Fair , Sudeep Holla , Cristian Marussi , David Lechner , Abel Vesa , Peng Fan , Frank Li , Sascha Hauer , Pengutronix Kernel Team , Fabio Estevam , Paul Cercueil , Santosh Shilimkar , Andrew Lunn , Gregory Clement , Sebastian Hesselbarth , Vladimir Zapolskiy , Heiko Stuebner , Krzysztof Kozlowski , Sylwester Nawrocki , Chanwoo Choi , Peter Griffin , Alim Akhtar , Dinh Nguyen , Viresh Kumar , Maxime Coquelin , Alexandre Torgue , Emilio =?iso-8859-1?Q?L=F3pez?= , Chen-Yu Tsai , Jernej Skrabec , Samuel Holland , Prashant Gaikwad , Thierry Reding , Jonathan Hunter , Kunihiko Hayashi , Masami Hiramatsu , Ulf Hansson , Liviu Dudau , Lorenzo Pieralisi , Michal Simek , Matthias Brugger , linux-clk@vger.kernel.org, linux-aspeed@lists.ozlabs.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, openbmc@lists.ozlabs.org, arm-scmi@vger.kernel.org, imx@lists.linux.dev, linux-mips@vger.kernel.org, linux-renesas-soc@vger.kernel.org, linux-rockchip@lists.infradead.org, linux-samsung-soc@vger.kernel.org, soc@lists.linux.dev, linux-stm32@st-md-mailman.stormreply.com, linux-sunxi@lists.linux.dev, linux-tegra@vger.kernel.org, linux-mediatek@lists.infradead.org Subject: Re: [PATCH 00/45] clk: Make sure clk_init_data is fully initialized (part two) Message-ID: References: Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/2.4.0 (2026-06-19) Hi Geert / all, On Fri, Aug 21, 2026 at 10:53:10AM +0200, Geert Uytterhoeven 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 clock 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 (45): > clk: aspeed: Make sure clk_init_data is fully initialized > clk: at91: Make sure clk_init_data is fully initialized > clk: bcm: iproc: Make sure clk_init_data is fully initialized > clk: berlin: Make sure clk_init_data is fully initialized > clk: cdce925: Make sure clk_init_data is fully initialized > clk: clk-axi-clkgen: Make sure clk_init_data is fully initialized > clk: cs2000-cp: Make sure clk_init_data is fully initialized > clk: davinci: Make sure clk_init_data is fully initialized > clk: fractional-divider: Make sure clk_init_data is fully initialized > clk: gemini: Make sure clk_init_data is fully initialized > clk: highbank: Make sure clk_init_data is fully initialized > clk: hisilicon: Make sure clk_init_data is fully initialized > clk: imx: Make sure clk_init_data is fully initialized > clk: ingenic: Make sure clk_init_data is fully initialized > clk: keystone: Make sure clk_init_data is fully initialized > clk: lmk04832: Make sure clk_init_data is fully initialized > clk: mediatek: Make sure clk_init_data is fully initialized > clk: milbeaut: Make sure clk_init_data is fully initialized > clk: mmp: Make sure clk_init_data is fully initialized > clk: mvebu: Make sure clk_init_data is fully initialized > clk: mxs: Make sure clk_init_data is fully initialized > clk: nomadik: Make sure clk_init_data is fully initialized > clk: npcm7xx: Make sure clk_init_data is fully initialized > clk: nxp: Make sure clk_init_data is fully initialized > clk: pistachio: Make sure clk_init_data is fully initialized > clk: pwm: Make sure clk_init_data is fully initialized > clk: renesas: Make sure clk_init_data is fully initialized > clk: rockchip: Make sure clk_init_data is fully initialized > clk: samsung: Make sure clk_init_data is fully initialized > clk: scpi: Make sure clk_init_data is fully initialized > clk: silabs: Make sure clk_init_data is fully initialized > clk: socfpga: Make sure clk_init_data is fully initialized > clk: spear: Make sure clk_init_data is fully initialized > clk: stm32: Make sure clk_init_data is fully initialized > clk: st: Make sure clk_init_data is fully initialized > clk: sunxi: Make sure clk_init_data is fully initialized > clk: tegra: Make sure clk_init_data is fully initialized > clk: uniphier: Make sure clk_init_data is fully initialized > clk: ux500: Make sure clk_init_data is fully initialized > clk: versatile: Make sure clk_init_data is fully initialized > clk: vt8500: Make sure clk_init_data is fully initialized > clk: x86: Make sure clk_init_data is fully initialized > clk: xgene: Make sure clk_init_data is fully initialized > clk: xilinx: Make sure clk_init_data is fully initialized > clk: zynqmp: Make sure clk_init_data is fully initialized 44 / 45 patches have been added to clk-next. I took it all for simplicity rather than everyone trying to cherry pick just their parts. Geert: The only patch that didn't apply was: [PATCH 27/45] clk: renesas: Make sure clk_init_data is fully initialized I didn't look into it too much. Brian