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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D1CD8C64EC7 for ; Sat, 25 Feb 2023 06:25:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229562AbjBYGZm (ORCPT ); Sat, 25 Feb 2023 01:25:42 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55878 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229532AbjBYGZk (ORCPT ); Sat, 25 Feb 2023 01:25:40 -0500 Received: from mail-pl1-x634.google.com (mail-pl1-x634.google.com [IPv6:2607:f8b0:4864:20::634]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 850B724487 for ; Fri, 24 Feb 2023 22:25:37 -0800 (PST) Received: by mail-pl1-x634.google.com with SMTP id z2so1636500plf.12 for ; Fri, 24 Feb 2023 22:25:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=4QPCIfZpunPpGQRjZ0CLzZgvh1bMrAOlRsJYurE9VOI=; b=i2OnX+qtVkxWkVFcUUUtHoMVo58k8kPteFOU3yRJoch4UrZVjVtoKgQCILPsSIH2IM 9SuCn3vu72nb3n2gCsoCb9MQcwZbuXYf5jgyHDO34s/gR8M5CxRU5gV0+YnHw+9V/jL3 UereLqEbLRdif9+wLl1Wv9EJQ5zwKS3GE8nA8qUJSHw1j151949EZ1cDEtx0EJ19hLV9 2i4mG+2eo1p0BSS1qZavXyXOVwVlLf24HyC12nbm1kz7x2IzYuc7LLP1/1i2knyLhN87 asicV45YD46sfQWagebPdNnXBrCMp8DyEYimgDowgWuBomRC1Gc2M0hNTbO7Evf7ew4Y cwsQ== 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=4QPCIfZpunPpGQRjZ0CLzZgvh1bMrAOlRsJYurE9VOI=; b=AkbEm3PJWl31mt90tAEQB8eIRgKb/AIg20S0DReWi4l3GcIYKrmBQdNyhxgtS/Q7UK P5swK/JWDA/wU/s+CsQCGZpqL8ZTtj4GNx/wDB+o975jYcdG3G7F4j8KEQBEj8/G+av1 tL9EZSq5FrKMCAQ+7NHyC/zIG/okgQ5V+NUR33QzLqLahkEs2CR4iZnZzA/eLf6NLXsI dr86X9/GqBO05v5iuLM/wWer3pxGdEKJa+ARA5ah7LKBwHQ1AksS7GrnrNM3Uaq9n9Xu pW1//DBMGua4OITAEuBebY2ASgfQvoBw2wjeYt7FQxLrdUFDH9N7ayo8FIzXYAB7JhPh A4Dw== X-Gm-Message-State: AO0yUKVHyvYyibaEmh/QMzHncBMZs3hp/9KV2tZuh1oN+qHlDaLzSxa/ s/V/mNTq9ehexBkYovnyhjvQIXQEI6gU2MovKCHknA== X-Google-Smtp-Source: AK7set/k/0eO1pGMhcQMet0YU6e3h9+c98wFu1JipuFF0QZYfLgw6WY/Kw7NUyUCthebeNVAXRQmnWBsB84kG+im0+I= X-Received: by 2002:a17:903:2402:b0:19c:a7a7:7072 with SMTP id e2-20020a170903240200b0019ca7a77072mr3005999plo.10.1677306336589; Fri, 24 Feb 2023 22:25:36 -0800 (PST) MIME-Version: 1.0 References: <20230207014207.1678715-1-saravanak@google.com> In-Reply-To: From: Saravana Kannan Date: Fri, 24 Feb 2023 22:24:59 -0800 Message-ID: Subject: Re: [PATCH v3 00/12] fw_devlink improvements To: Dmitry Baryshkov Cc: Greg Kroah-Hartman , "Rafael J. Wysocki" , Sudeep Holla , Cristian Marussi , Linus Walleij , Bartosz Golaszewski , Thomas Gleixner , Marc Zyngier , Shawn Guo , Sascha Hauer , Pengutronix Kernel Team , Fabio Estevam , NXP Linux Team , Miquel Raynal , Richard Weinberger , Vignesh Raghavendra , Rob Herring , Frank Rowand , Geert Uytterhoeven , Magnus Damm , Andy Shevchenko , Daniel Scally , Heikki Krogerus , Sakari Ailus , Len Brown , =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= , Abel Vesa , Alexander Stein , Tony Lindgren , Geert Uytterhoeven , John Stultz , Doug Anderson , Guenter Roeck , Maxim Kiselev , Maxim Kochetkov , Luca Weiss , Colin Foster , Martin Kepplinger , Jean-Philippe Brucker , Vladimir Oltean , kernel-team@android.com, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org, linux-mtd@lists.infradead.org, devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org, linux-acpi@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 15, 2023 at 7:12 PM Dmitry Baryshkov wrote: > > On 07/02/2023 03:41, Saravana Kannan wrote: > > Naresh, Tony, Abel, Geert, Dmitry, Maxim(s), Miquel, Luca, Doug, Martin, > > Jean-Philippe, > > > > Can I get your Tested-by's for this v3 series please? > > > > Vladimir, > > > > Ccing you because DSA's and fw_devlink have known/existing problems > > (still in my TODOs to fix). But I want to make sure this series doesn't > > cause additional problems for DSA. > > > > All, > > > > This patch series improves fw_devlink in the following ways: > > > > 1. It no longer cares about a fwnode having a "compatible" property. It > > figures this out more dynamically. The only expectation is that > > fwnodes that are converted to devices actually get probed by a driver > > for the dependencies to be enforced correctly. > > > > 2. Finer grained dependency tracking. fw_devlink will now create device > > links from the consumer to the actual resource's device (if it has one, > > Eg: gpio_device) instead of the parent supplier device. This improves > > things like async suspend/resume ordering, potentially remove the need > > for frameworks to create device links, more parallelized async probing, > > and better sync_state() tracking. > > > > 3. Handle hardware/software quirks where a child firmware node gets > > populated as a device before its parent firmware node AND actually > > supplies a non-optional resource to the parent firmware node's > > device. > > > > 4. Way more robust at cycle handling (see patch for the insane cases). > > > > 5. Stops depending on OF_POPULATED to figure out some corner cases. > > > > 6. Simplifies the work that needs to be done by the firmware specific > > code. > > > > The v3 series has gone through my usual testing on my end and looks good > > to me. > > Saravana, > > Please excuse me, I was completely overwhelmed with my regular work and > had no time to properly test the series, while doing just the light > test would defeat the purpose of testing. > > Tested-by: Dmitry Baryshkov # Qualcomm RB3 > > Thanks a lot for going through all the troubles and hunting all the issues! You are welcome! Thanks for testing it. > Just a note: on an RB3 device (arm64 qcom/sdm845-db845c.dtsi) extended > with the patch at [3] I got the following messages in dmesg: > > [ 1.051325] platform ae00000.mdss: Failed to create device link > with ae00000.mdss > [ 1.059368] platform ae00000.mdss: Failed to create device link > with ae00000.mdss > [ 1.067174] platform ae00000.mdss: Failed to create device link > with ae00000.mdss > [ 1.088322] platform c440000.spmi: Failed to create device link > with c440000.spmi > [ 1.096019] platform c440000.spmi: Failed to create device link > with c440000.spmi > [ 1.103707] platform c440000.spmi: Failed to create device link > with c440000.spmi > [ 1.111400] platform c440000.spmi: Failed to create device link > with c440000.spmi > [ 1.119141] platform c440000.spmi: Failed to create device link > with c440000.spmi > [ 1.126825] platform c440000.spmi: Failed to create device link > with c440000.spmi > [ 2.024763] qcom-lab-ibb-regulator c440000.spmi:pmic@3:labibb: > Failed to create device link with c440000.spmi > [ 2.035026] qcom-lab-ibb-regulator c440000.spmi:pmic@3:labibb: > Failed to create device link with c440000.spmi > > They look to be harmless, but it might be good to filter some of them > out? Especially the ones which tell about creating a device link > pointing back to the same device. I'm sure it's harmless when the supplier == consumer. Agreed on filtering these out. I looked at [3], but it's not obvious to me how this is happening for your specific case. There are a couple of ways I can think of: 1. A SYNC_STATE_ONLY link being created as a proxy link (I don't do as many checks here because it can't break anything) 2. __fw_devlink_pickup_dangling_consumers() causing the consumer and supplier to be the same. But I want to understand which one is happening in your case. Can you add a WARN_ON(1) after the error message and give me the list of stack dumps that are unique? Thanks, Saravana > > [3] https://lore.kernel.org/linux-arm-msm/20230118082048.2198715-1-dmitry.baryshkov@linaro.org/ > > > > > Thanks, > > Saravana > > > > [1] - https://lore.kernel.org/lkml/20220810060040.321697-1-saravanak@google.com/ > > [2] - https://lore.kernel.org/lkml/CAGETcx-JUV1nj8wBJrTPfyvM7=Mre5j_vkVmZojeiumUGG6QZQ@mail.gmail.com/ > > > > v1 -> v2: > > - Fixed Patch 1 to handle a corner case discussed in [2]. > > - New patch 10 to handle "fsl,imx8mq-gpc" being initialized by 2 drivers. > > - New patch 11 to add fw_devlink support for SCMI devices. > > > > v2 -> v3: > > - Addressed most of Andy's comments in v2 > > - Added Colin and Sudeep's Tested-by for the series (except the imx and > > renesas patches) > > - Added Sudeep's Acked-by for the scmi patch. > > - Added Geert's Reviewed-by for the renesas patch. > > - Fixed gpiolib crash reported by Naresh. > > - Patch 6: Fix __fwnode_links_move_consumers() to preserve fwnode link flags. > > - New Patch 12 to fix nvmem-cells issue reported by Maxim(s)/Miquel. > > - Deleted some stale function doc in Patch 8 > > > > Cc: Abel Vesa > > Cc: Alexander Stein > > Cc: Tony Lindgren > > Cc: Sudeep Holla > > Cc: Geert Uytterhoeven > > Cc: John Stultz > > Cc: Doug Anderson > > Cc: Guenter Roeck > > Cc: Dmitry Baryshkov > > Cc: Maxim Kiselev > > Cc: Maxim Kochetkov > > Cc: Miquel Raynal > > Cc: Luca Weiss > > Cc: Colin Foster > > Cc: Martin Kepplinger > > Cc: Jean-Philippe Brucker > > Cc: Vladimir Oltean > > > > Saravana Kannan (12): > > driver core: fw_devlink: Don't purge child fwnode's consumer links > > driver core: fw_devlink: Improve check for fwnode with no > > device/driver > > soc: renesas: Move away from using OF_POPULATED for fw_devlink > > gpiolib: Clear the gpio_device's fwnode initialized flag before adding > > driver core: fw_devlink: Add DL_FLAG_CYCLE support to device links > > driver core: fw_devlink: Allow marking a fwnode link as being part of > > a cycle > > driver core: fw_devlink: Consolidate device link flag computation > > driver core: fw_devlink: Make cycle detection more robust > > of: property: Simplify of_link_to_phandle() > > irqchip/irq-imx-gpcv2: Mark fwnode device as not initialized > > firmware: arm_scmi: Set fwnode for the scmi_device > > mtd: mtdpart: Don't create platform device that'll never probe > > > > drivers/base/core.c | 449 +++++++++++++++++++++----------- > > drivers/firmware/arm_scmi/bus.c | 3 +- > > drivers/gpio/gpiolib.c | 7 + > > drivers/irqchip/irq-imx-gpcv2.c | 1 + > > drivers/mtd/mtdpart.c | 10 + > > drivers/of/property.c | 84 +----- > > drivers/soc/imx/gpcv2.c | 2 +- > > drivers/soc/renesas/rcar-sysc.c | 2 +- > > include/linux/device.h | 1 + > > include/linux/fwnode.h | 12 +- > > 10 files changed, 344 insertions(+), 227 deletions(-) > > > > -- > With best wishes > > Dmitry