Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp2552681rwb; Fri, 9 Dec 2022 03:42:11 -0800 (PST) X-Google-Smtp-Source: AA0mqf4jKGrfiafXuR/IyQtVJSR6QK88dcCS07pu8nXJAT9EyEczVwx7kz6PGIDfTrgXlP9Cn1av X-Received: by 2002:a05:6a20:c887:b0:ac:f68:33c9 with SMTP id hb7-20020a056a20c88700b000ac0f6833c9mr6826183pzb.33.1670586131151; Fri, 09 Dec 2022 03:42:11 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1670586131; cv=none; d=google.com; s=arc-20160816; b=WAwYV4V9KpuIoaj+lO8SzeXz9KqSyCoRTF4qcF0cHtYLlfPW1QW3TfeBL5QYSt/CkI +ZIH73UjaE+Wbsoummsxk2iNGYNTDezzbMbnDcxEP0XO9vlZSO8UFHVHzgOureEd0otT XWr1HNu3kwCmm88yz4n8AN5oqrpOVNKXi1bg7VIeq2F3Ma0qdDcpR6bah44CYHKyQS4R uBXkADkOgzItenF5M70kBZNtNnJIJu7q5tjfbuiMar6eKkXZCpcyYO3U4x0THcVuCeqJ HwsGmUWLZqEei3epR9C2Idst/eGGG0gRteUqLCM7JNKgClMCRy4TethwsPM2hNTrQ4Tr ZgiQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=CeH76cIn44BHozvkORl6+VsQ+27Ui3VZGR1dvHq/zpw=; b=nhgoUCGl9cedKxHfVh3Ta3nIOWc2J9MC5sfnhxrd7WyGDCudvb1TJHzjXIMCHAtWDo Uldhs0VptUIEbNxfWlQFiUZnzELEJX/Sa8Bam9gxzWZCE12WWf7mfT7siX9eBrwUdStS HeyoeJuqlpQtRGICpA5DGADaHwv2SkRpSaXO8loXVOlWOzGoWY+yq5R7ANzGMZyfKk+s 9TvtqTijOWquPS2IZCA8CVaadxcHuW1ssNxQVND+sacFjSJybZoNQySuCWjujM934bFe bEjg9fwHyVhoGr6CvprQwumn2CfPzjj70K+hIZIN3QZA4aSqsazl6y0uw39aqNE7QN/m 7s3A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=IY+agMYT; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id k4-20020a654644000000b00476f87434ebsi1288915pgr.467.2022.12.09.03.42.00; Fri, 09 Dec 2022 03:42:11 -0800 (PST) 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=@linaro.org header.s=google header.b=IY+agMYT; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229905AbiLIL0L (ORCPT + 74 others); Fri, 9 Dec 2022 06:26:11 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50102 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229563AbiLIL0J (ORCPT ); Fri, 9 Dec 2022 06:26:09 -0500 Received: from mail-yb1-xb2f.google.com (mail-yb1-xb2f.google.com [IPv6:2607:f8b0:4864:20::b2f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 19EDE6932D for ; Fri, 9 Dec 2022 03:26:08 -0800 (PST) Received: by mail-yb1-xb2f.google.com with SMTP id e141so5146243ybh.3 for ; Fri, 09 Dec 2022 03:26:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=CeH76cIn44BHozvkORl6+VsQ+27Ui3VZGR1dvHq/zpw=; b=IY+agMYTzfHBx+3Qkj4f7wSGEXcVTNzwuJ17QNdQUvenElRs5D4sYRUzbCDlz4dqoY 7ZGU1BWq4Kyz8FchqdvJ6Pj2Ee8jsVKRw5sYsH4aYLAY9IOtXBMfDgPrdzKNK1IcJ1bC M0mropxzc4utuKa0eeuQykt9I8qP2aJ6wuVv1lB+ElriT9oRsxWIO9kwX7uB4uSDUSgC tAzY0XbBn1ewdGat06eQNwY6+iiLzplRzZ6R3UWhQ2k549n4HI0349rIumKcZuEGjquy 4TIq4DLSk8qAGThvkLIGC/RosPo0y+FmvkK61h0sPKRESAby048mN+VuvCfCEHoRMFke ymWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=CeH76cIn44BHozvkORl6+VsQ+27Ui3VZGR1dvHq/zpw=; b=sH5ohTyi2O5ezLWC/XPyj8KaHoqEsw/3Du1ExfZ4vURQjNNAc920d/VMTdd2tka2ao BP1V8I5/jxU4WHBYlg3S3gdHsq7YBmzfg0agwxE+epPcUpR0wWw6DTMSaljYXK27KvEW 9rorvGQvNzPK5G+F547QduoHcRWL6qyyXF6xKCovc/yiDRqsLeWSAKUcJbvWwdP6GOMC q5AnO1A/sEe5m/Et5tfRpGIPtuDPLqBNCNOY7ZAaPvwLV8ucbu46cOE4GnRilOiUwbnd w1E48KKAJQYl5WJ2RhAe5pJIn0VscCUD0q3iCajD00RA27zZF6c8b2oRY5G17ChWWlS5 Yd4Q== X-Gm-Message-State: ANoB5plYNlq1vL2H/0JzrEdp6S9oJCLp/+EMXhx4UmT14QlWONypsDw5 Ar4I3J4cmV2WB5Ssuq3TxWxiMWYf0aYSO9/M7V6M1g== X-Received: by 2002:a25:7648:0:b0:6fe:54d5:2524 with SMTP id r69-20020a257648000000b006fe54d52524mr22109411ybc.522.1670585167318; Fri, 09 Dec 2022 03:26:07 -0800 (PST) MIME-Version: 1.0 References: <20221128054820.1771-1-clin@suse.com> <20221128054820.1771-3-clin@suse.com> In-Reply-To: From: Linus Walleij Date: Fri, 9 Dec 2022 12:27:28 +0100 Message-ID: Subject: Re: [PATCH v2 2/2] pinctrl: add NXP S32 SoC family support To: Chester Lin , Saravana Kannan Cc: Fabio Estevam , Dong Aisheng , Shawn Guo , Jacky Bai , Pengutronix Kernel Team , s32@nxp.com, linux-gpio@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Larisa Grigore , Ghennadi Procopciuc , Andrei Stefanescu , Radu Pirea , =?UTF-8?Q?Andreas_F=C3=A4rber?= , Matthias Brugger , Matthew Nunez , Phu Luu An , Stefan-Gabriel Mirea Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS autolearn=unavailable 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 On Fri, Dec 9, 2022 at 5:39 AM Chester Lin wrote: > > Hi Linus and Fabio, > > Thanks for your time to review this patch! > > On Thu, Dec 08, 2022 at 10:37:36PM +0100, Linus Walleij wrote: > > On Thu, Dec 8, 2022 at 12:04 AM Fabio Estevam wrote: > > > > > In other imx8m pinctrl drivers we pass: > > (...) > > > > +module_platform_driver(s32g_pinctrl_driver); > > > > > > And we also register it in arch_initcall() level. > > > > Do you really need that though? This driver certainly does not. > > > > I was under the impression that recent changes to the probe-order > > logic has made most explicit arch_ etc initcall orderings surplus. > > > > Could bool/tristate options in the Kconfig be the key point? > > Based on current design I prefer to build the s32g2 pinctrl driver as built-in > rather than a loadable module. IIUC, when the driver is not built as module > then the initcall ordering should still matter. It is true that if you compile something into a module then all initicalls are the same: they are called when the module is loaded. But the remaining initcalls used to be assigned to core, arch, subsystem etc in order for resources (such as clocks, regulators or pins) to be available before the drivers that need them get probed. However there was first deferred probe to partially solve the problem and recently a large and refined series that use the dependencies in the device tree to resolve probe order. Saravana Kannan has been working tirelessly at this, issueing git log --oneline --author="Saravana Kannan" you will see the scope of this work. Yours, Linus Walleij