Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 50068C433F5 for ; Tue, 16 Nov 2021 00:06:17 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 3582B63244 for ; Tue, 16 Nov 2021 00:06:17 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1348798AbhKPAJJ (ORCPT ); Mon, 15 Nov 2021 19:09:09 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49730 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1350460AbhKOUXy (ORCPT ); Mon, 15 Nov 2021 15:23:54 -0500 Received: from mail-yb1-xb2c.google.com (mail-yb1-xb2c.google.com [IPv6:2607:f8b0:4864:20::b2c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 295EBC061746 for ; Mon, 15 Nov 2021 12:18:24 -0800 (PST) Received: by mail-yb1-xb2c.google.com with SMTP id s186so50481521yba.12 for ; Mon, 15 Nov 2021 12:18:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ti2qS38N54C0keJ4viYpkfZvuilsGcLNEF7JfCXeTTQ=; b=dh/Oa9Ne/UX3lXjDB4COE5fcmk8sukuVS9CcQeo4HvaaL9inYkLrRgESiTiiJjH8Ha VD+voEPVlu4lT/PFKwINwdG4d11smF+KO/ppWh9QkjAYWf9nI2V51AWJZTZVp4mOvqr/ OqeBQGqGBLjLgEja7DyQ3k/np69fx0UsIFBY0muAvUQRNUVa5/KFzlzavNtVE2HhmDsK bmh6KbqsAKlU3IKOQjpgPqjw0dOCkZxcS8P+7EtoLtYNqQhqa9IbpkxB9gRHMNpqSxBi l/xRTx3ssiex9d5VCAExW9LSc6GJtcglSAdxi43WZcr1AEmZAEonPwY3qqbOY1Qs3OD3 dPHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ti2qS38N54C0keJ4viYpkfZvuilsGcLNEF7JfCXeTTQ=; b=6vlcEDKshIgGpQgFXG5SkQiXT4ZEe86E95+FGWI3+N70lFUjXgQHezTKGwAjTE85ra B0qaPsU4/ieutWwwfVqU/6pBCpBXwEyHMJvrWwk9ar85w7xWfGCvtqcqieJViZZiAVin DeTDUzjSX5ULdBHlJB278P5jjUblV8P6PpVU6vpEWcfBoX7FRMLilNApS+B2RSF9qXpW 3RM0y83Ijgr1wbOXOhGT1D59cqCDw50QdIfSFCZV9w2qW0cU4EayVU5/C2pciU34wuyM 8GkepU2MCtOedwGWDYvLhhq2PKnMh+zRDKw+bLpcnBseHC0aFq78l4LuzM1WdEiD3dG9 uPiA== X-Gm-Message-State: AOAM5330UrEHzhwnFj3JaS2D96CJAhrMW7jWrJmGIRB0hsevT9Mu4sft zvFsl8RWoJG7nni/SNujVvI9MXIhLgG7L59ITqkINg== X-Google-Smtp-Source: ABdhPJxKkmPEnUXj0aVbJDTQXnWiiYrBJDqwAo+CYLHhYd6MMCN9FGeHm5tb4KkW7mZ9cUyGQQ0uXz7x+4W8OBjmlCo= X-Received: by 2002:a5b:783:: with SMTP id b3mr1822562ybq.328.1637007502971; Mon, 15 Nov 2021 12:18:22 -0800 (PST) MIME-Version: 1.0 References: <20210929000735.585237-1-saravanak@google.com> <20210929000735.585237-2-saravanak@google.com> In-Reply-To: From: Saravana Kannan Date: Mon, 15 Nov 2021 12:17:46 -0800 Message-ID: Subject: Re: [PATCH v4 1/2] drivers: bus: simple-pm-bus: Add support for probing simple bus only devices To: Abel Vesa Cc: Russell King , Neil Armstrong , Geert Uytterhoeven , Magnus Damm , Tony Lindgren , Catalin Marinas , Will Deacon , Damien Le Moal , Greg Kroah-Hartman , Ulf Hansson , Rob Herring , kernel-team@android.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-oxnas@groups.io, linux-renesas-soc@vger.kernel.org, linux-omap@vger.kernel.org, linux-riscv@lists.infradead.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 10, 2021 at 12:24 PM Saravana Kannan wrote: > > On Wed, Nov 10, 2021 at 4:16 AM Abel Vesa wrote: > > > > On 21-09-28 17:07:33, Saravana Kannan wrote: > > > fw_devlink could end up creating device links for bus only devices. > > > However, bus only devices don't get probed and can block probe() or > > > sync_state() [1] call backs of other devices. To avoid this, probe these > > > devices using the simple-pm-bus driver. > > > > > > However, there are instances of devices that are not simple buses (they get > > > probed by their specific drivers) that also list the "simple-bus" (or other > > > bus only compatible strings) in their compatible property to automatically > > > populate their child devices. We still want these devices to get probed by > > > their specific drivers. So, we make sure this driver only probes devices > > > that are only buses. > > > > > > [1] - https://lore.kernel.org/lkml/CAPDyKFo9Bxremkb1dDrr4OcXSpE0keVze94Cm=zrkOVxHHxBmQ@mail.gmail.com/ > > > Fixes: c442a0d18744 ("driver core: Set fw_devlink to "permissive" behavior by default") > > > Signed-off-by: Saravana Kannan > > > Tested-by: Saravana Kannan > > > Tested-by: Ulf Hansson > > > --- > > > drivers/bus/simple-pm-bus.c | 42 ++++++++++++++++++++++++++++++++++--- > > > 1 file changed, 39 insertions(+), 3 deletions(-) > > > > > > diff --git a/drivers/bus/simple-pm-bus.c b/drivers/bus/simple-pm-bus.c > > > index 01a3d0cd08ed..6b8d6257ed8a 100644 > > > --- a/drivers/bus/simple-pm-bus.c > > > +++ b/drivers/bus/simple-pm-bus.c > > > @@ -13,11 +13,36 @@ > > > #include > > > #include > > > > > > - > > > static int simple_pm_bus_probe(struct platform_device *pdev) > > > { > > > - const struct of_dev_auxdata *lookup = dev_get_platdata(&pdev->dev); > > > - struct device_node *np = pdev->dev.of_node; > > > + const struct device *dev = &pdev->dev; > > > + const struct of_dev_auxdata *lookup = dev_get_platdata(dev); > > > + struct device_node *np = dev->of_node; > > > + const struct of_device_id *match; > > > + > > > + /* > > > + * Allow user to use driver_override to bind this driver to a > > > + * transparent bus device which has a different compatible string > > > + * that's not listed in simple_pm_bus_of_match. We don't want to do any > > > + * of the simple-pm-bus tasks for these devices, so return early. > > > + */ > > > + if (pdev->driver_override) > > > + return 0; > > > + > > > + match = of_match_device(dev->driver->of_match_table, dev); > > > + /* > > > + * These are transparent bus devices (not simple-pm-bus matches) that > > > + * have their child nodes populated automatically. So, don't need to > > > + * do anything more. We only match with the device if this driver is > > > + * the most specific match because we don't want to incorrectly bind to > > > + * a device that has a more specific driver. > > > + */ > > > + if (match && match->data) { > > > + if (of_property_match_string(np, "compatible", match->compatible) == 0) > > > + return 0; > > > + else > > > + return -ENODEV; > > > + } > > > > This change is breaking the expected behavior for the already existent > > simple-bus nodes. All the simple-bus compatibles should be replaced now > > to simple-pm-bus. In my case, on some i.MX8 platforms, without the > > devlink, the devices suspend sequence changes (and even breaks). > > > > To avoid breaking the already existent simple-bus nodes, maybe the logic > > should've been reversed: keep the simple-bus as is and add another > > compatible, IDK, something like simple-trasnparent-bus, or something. > > The intent of this change IS to affect existing simple-bus nodes (but > not in the way it's affecting you). But if it's breaking stuff, we > obviously need to fix it. > > I have a hunch on what's going on in your case, but can you point me > to the specific simple-bus node that's getting affected? I'm expecting > it to be a simple-bus node that gets added AFTER this driver is > registered at device_initcall (module_init gets converted to > device_initcall). > > Also, can you try this hack patch to see if it helps your case? > https://lore.kernel.org/lkml/CAGETcx9U130Oq-umrvXME4JhEpO0Wadoki3kNxx=0-YvTR6PtQ@mail.gmail.com/ > > I have some thoughts on how I could fix this, but I need to think > about a few cases. Hi Abel, Friendly reminder. -Saravana