Received: by 2002:ac0:e350:0:0:0:0:0 with SMTP id g16csp242178imn; Thu, 4 Aug 2022 04:17:25 -0700 (PDT) X-Google-Smtp-Source: AA6agR7Y/vye4p6A5eLewB6ywHZc+yV1S8qaP3FwGNTrsNJabrxW5ernovLsMs99haMPEux0JcDy X-Received: by 2002:a17:90b:3ec3:b0:1f1:ff45:1d3b with SMTP id rm3-20020a17090b3ec300b001f1ff451d3bmr9889549pjb.101.1659611845395; Thu, 04 Aug 2022 04:17:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1659611845; cv=none; d=google.com; s=arc-20160816; b=A0TWdkaf90O4XGQNUjCAeDT0wVhkrLRVr1cn4DTp2g8iZhpNJ3wPZn8/GUTZNYuWam BFK5KSC2vuegL+LV3KhymKBmkO91cnw4NDRmfWWZNEANEoVXyNrbrdbYwC0VWQT+9/MF 9P28FPBPiJbz7uTFr/uZHCgf4voXYhxX6jomVcV74oKwyNStdDMrpyEE1NotuA6wmlX+ JJpZRQeLA+RYECkChGkH0gTZ6hArkG8HACvnblKh405ADBl4IKPCFU/zh6Y+MyCw86fP lY6aA5Chnkyy8JBJBoCvSgKZ2M7UdfQ2WP59RrldPs4mcVW/C6WMqlABbMiEISpsE44B N/Fg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:to:references:message-id :content-transfer-encoding:cc:date:in-reply-to:from:subject :mime-version:dkim-signature; bh=N7EQU9MlWTC84hNYcDq54sTO0o6CB2OpePDIIDMkHEg=; b=U3V0p4T7XZkP4R1UmfxJOeYhSpo3AGWoBhRESkiz12fydmN2pSJXGznBY8QuVzSry1 r7TnWNR/DDNwqCzZm4G1mlHfHV2uy3fBp4xn4QcvkjLDY9UA/p4nD2bELjG9Q9sJGp58 Rpkht3zAScBQoQCzBZgJHvo/TOkGfyyAjm9OHafGyuLNEoA4fK1uQwEtyO1tYjgDJbGo bsTGfqHwAvuXWucbtOnB1hV8kBroZFkJyUsp+CMsnROcCeaL8TAK47T5JvqlmWFKWLHu E+E73dqLPmnr34gagXdzP7wIhMwHe8dIxSKmDTivEzMcUQLZgGFHkdN1Ar9KCHwf9t5R o1LA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kohlschutter-com.20210112.gappssmtp.com header.s=20210112 header.b=e0iyDEWH; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id m15-20020a170902db0f00b0016ef089881bsi805913plx.252.2022.08.04.04.17.10; Thu, 04 Aug 2022 04:17:25 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kohlschutter-com.20210112.gappssmtp.com header.s=20210112 header.b=e0iyDEWH; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236503AbiHDKoh (ORCPT + 99 others); Thu, 4 Aug 2022 06:44:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38898 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229575AbiHDKoe (ORCPT ); Thu, 4 Aug 2022 06:44:34 -0400 Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B157D31935 for ; Thu, 4 Aug 2022 03:44:32 -0700 (PDT) Received: by mail-ed1-x536.google.com with SMTP id r4so17066970edi.8 for ; Thu, 04 Aug 2022 03:44:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kohlschutter-com.20210112.gappssmtp.com; s=20210112; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=N7EQU9MlWTC84hNYcDq54sTO0o6CB2OpePDIIDMkHEg=; b=e0iyDEWH8R0ix9gFWmNDk9YNInINTAfTGWPNXlGZ8OMK+TPX9jji6h0kvB6L+BpDdY RipD+0jXzrAyZ+OkRzyYzvJYfdDPS8GfQ4Xz36S+hcy0arEIC6qFnPyRvyAxjJbwbw9Y BkJhymEuvYgaXbydzpH67xbEm7Winn6br50iX4+zdoRvCpzc+HkMGOvgG1kLnvOxPMHi dJxj+q8sX5Pe7PyQtSycORO1LwgYX+4RhNhyU/2MQzjdkRt+ZvnC5SIQaHEf6ugxMOdp h9dM7HEcF5nu3pivSWyRw++MMLqeCxd+igKMaZ110OpZAoHmFrNoKwsIyT4QPYrhzSa7 UMIA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=N7EQU9MlWTC84hNYcDq54sTO0o6CB2OpePDIIDMkHEg=; b=C7YFIx37EhY7paqU1gCQ18hWaPVBgNanuKEoL/ga7NCU62KG1qtItR5MbdUjawCRYE GjiEHU3na0PQqIB0eUYNoOoF+bv5c1r1z1oMfNemYDdJ9wcWcFPsJpaNfy6rKM/plZR/ Z+21oJqZIhZ/VmYxnMl8MaFTgnzyBP42oSMoR15EVSIa74udCjcsTGb9Q7LEeoewIo1a Ggh1ijYu+ztadB7y10FGNjAU7haEamsooupEYalabTyQOgmxVg5bkXtgt3GWyKZhmI7H q8OBDZ4RGuiD0vma/NOsc0fptfKzXwkE3yoxKAWPm3JhbN/WBJiiDEJB89ykZfp97Zn1 uuMQ== X-Gm-Message-State: ACgBeo3lUV5C1L3NmUpigh5HYHgq1Wybtd2Hkwf1oKjkAYXRX2uTaF2N Ss3EZhvl+MDFWBFUmeSJbV0pZg== X-Received: by 2002:a05:6402:32a8:b0:43e:5490:295f with SMTP id f40-20020a05640232a800b0043e5490295fmr1365826eda.193.1659609871260; Thu, 04 Aug 2022 03:44:31 -0700 (PDT) Received: from smtpclient.apple (ip5b434222.dynamic.kabel-deutschland.de. [91.67.66.34]) by smtp.gmail.com with ESMTPSA id 17-20020a170906211100b0072b2378027csm220357ejt.26.2022.08.04.03.44.30 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Aug 2022 03:44:30 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\)) Subject: [PATCH v3] regulator: core: Resolve supply name earlier to prevent double-init From: =?utf-8?Q?Christian_Kohlsch=C3=BCtter?= In-Reply-To: Date: Thu, 4 Aug 2022 12:44:29 +0200 Cc: =?utf-8?Q?Heiko_St=C3=BCbner?= , Liam Girdwood , linux-arm-kernel , linux-kernel , Linux MMC List , "open list:ARM/Rockchip SoC..." , Markus Reichl , Robin Murphy , wens@kernel.org Content-Transfer-Encoding: 7bit Message-Id: References: To: Vincent Legoll , Mark Brown X-Mailer: Apple Mail (2.3696.120.41.1.1) X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Previously, an unresolved regulator supply reference upon calling regulator_register on an always-on or boot-on regulator caused set_machine_constraints to be called twice. This in turn may initialize the regulator twice, leading to voltage glitches that are timing-dependent. A simple, unrelated configuration change may be enough to hide this problem, only to be surfaced by chance. One such example is the SD-Card voltage regulator in a NanoPI R4S that would not initialize reliably unless the registration flow was just complex enough to allow the regulator to properly reset between calls. Fix this by re-arranging regulator_register, trying resolve the regulator's supply early enough that set_machine_constraints does not need to be called twice. Signed-off-by: Christian Kohlsch=C3=BCtter --- drivers/regulator/core.c | 51 +++++++++++++++++++++++++--------------- 1 file changed, 32 insertions(+), 19 deletions(-) diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c index 398c8d6afd4..5c2b97ea633 100644 --- a/drivers/regulator/core.c +++ b/drivers/regulator/core.c @@ -5492,7 +5492,38 @@ regulator_register(const struct regulator_desc = *regulator_desc, BLOCKING_INIT_NOTIFIER_HEAD(&rdev->notifier); INIT_DELAYED_WORK(&rdev->disable_work, regulator_disable_work); =20 - /* preform any regulator specific init */ + /* set regulator constraints */ + if (init_data) + rdev->constraints =3D kmemdup(&init_data->constraints, + sizeof(*rdev->constraints), + GFP_KERNEL); + else + rdev->constraints =3D = kzalloc(sizeof(*rdev->constraints), + GFP_KERNEL); + if (!rdev->constraints) { + ret =3D -ENOMEM; + goto clean; + } + + if (init_data && init_data->supply_regulator) + rdev->supply_name =3D init_data->supply_regulator; + else if (regulator_desc->supply_name) + rdev->supply_name =3D regulator_desc->supply_name; + + if ((rdev->supply_name && !rdev->supply) && rdev->constraints + && (rdev->constraints->always_on || = rdev->constraints->boot_on)) { + /* Try to resolve the name of the supplying regulator = here first + * so we prevent double-initializing the regulator, = which may + * cause timing-specific voltage brownouts/glitches that = are + * hard to debug. + */ + ret =3D regulator_resolve_supply(rdev); + if (ret) + rdev_dbg(rdev, "unable to resolve supply early: = %pe\n", + ERR_PTR(ret)); + } + + /* perform any regulator specific init */ if (init_data && init_data->regulator_init) { ret =3D init_data->regulator_init(rdev->reg_data); if (ret < 0) @@ -5518,24 +5549,6 @@ regulator_register(const struct regulator_desc = *regulator_desc, (unsigned long) atomic_inc_return(®ulator_no)); dev_set_drvdata(&rdev->dev, rdev); =20 - /* set regulator constraints */ - if (init_data) - rdev->constraints =3D kmemdup(&init_data->constraints, - sizeof(*rdev->constraints), - GFP_KERNEL); - else - rdev->constraints =3D = kzalloc(sizeof(*rdev->constraints), - GFP_KERNEL); - if (!rdev->constraints) { - ret =3D -ENOMEM; - goto wash; - } - - if (init_data && init_data->supply_regulator) - rdev->supply_name =3D init_data->supply_regulator; - else if (regulator_desc->supply_name) - rdev->supply_name =3D regulator_desc->supply_name; - ret =3D set_machine_constraints(rdev); if (ret =3D=3D -EPROBE_DEFER) { /* Regulator might be in bypass mode and so needs its = supply --=20 2.36.2