From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-11.4 required=3.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT,USER_IN_DEF_DKIM_WL autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 15FB2C433FF for ; Mon, 29 Jul 2019 22:11:09 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D31F1206DD for ; Mon, 29 Jul 2019 22:11:08 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="KWJm69Cu" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387632AbfG2WLI (ORCPT ); Mon, 29 Jul 2019 18:11:08 -0400 Received: from mail-vk1-f202.google.com ([209.85.221.202]:56185 "EHLO mail-vk1-f202.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729694AbfG2WLH (ORCPT ); Mon, 29 Jul 2019 18:11:07 -0400 Received: by mail-vk1-f202.google.com with SMTP id b85so27034216vke.22 for ; Mon, 29 Jul 2019 15:11:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=date:message-id:mime-version:subject:from:to:cc; bh=J/HMClv+Qs0qZrH9UG+BYxmogIYQGmmSIGEo1BZEiYc=; b=KWJm69CueVQLRyf5hIJOJ/XbzHZbr9DgW2lgzu/UitcF10Bt8wV2n9G7RGNm0YBk2j R2PcEYmPf6FybYk8NkKraE/JYMPPWJXUK1hizVgep8AvTqB89d2sfeTzRhsWQiq+CNIB K1i+cGKmGlYzBYWuwNfUQspS3ZqjeNPX5+b85LTb8pvKEWvkc3ScwKMgiI7O/HoKn4WH Ye3EH5Cu66G9d36ZftAv+w21d5zUS+CEon6Ttk1z/RQO1QNPl95/lFYx5HhrWwAO0GNS 1ldXPKJ35jztl6THPMExgFu7zqUIgm0dCzhw+o1GxNe4OHvFdx6voT6Bmk+AoHM+HCRo Gz3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:message-id:mime-version:subject:from:to:cc; bh=J/HMClv+Qs0qZrH9UG+BYxmogIYQGmmSIGEo1BZEiYc=; b=J8HqJ+P9EHE0ZmeU8FHKoObW72DIhJS0jkWDkeWQUrDxN1MsUxGkwaxWRLg8psfTLc ehpDHJ0DAz8VieEklTfMt0WQTi0l52SezCSx9LoG/sjUKDntLk0idH2elg8qE4GtzrIo QtY3aqv9uza2zCMPYXoxhb+F4wAEEJ5lNUeD6y9pgP+QZa8TR6dieVluR9BwT3U6XqUk P4WruJc/YxgLkOZxrkiCJlL8DeFRMBlrUqO3CNt35ISmsQsjAAbkiyHzQiufn/S6KfYJ 4MPXFIFWrmAQwaczzvHuNVHvEqRdXRTaQtUdnbTxGnppao6jAwZJHAE+QeBfhrcJpUfU EJFg== X-Gm-Message-State: APjAAAXu2+v6d3v3YCtHNyhVma520mYuLZLKFSqtmbJRRNbbGhHfToRM /SuzR7zTZPcFy95E8byhQRjehvnQdaTpi/w= X-Google-Smtp-Source: APXvYqz1+OixMzZgXRLKjvjE7/CpPTIa6dEjtH4f1jMfEF7N/JxANYKuVQzddzc8XiVJgQ3n99c6Sf3KFoK+R7Q= X-Received: by 2002:ab0:4307:: with SMTP id k7mr3628736uak.45.1564438265657; Mon, 29 Jul 2019 15:11:05 -0700 (PDT) Date: Mon, 29 Jul 2019 15:10:54 -0700 Message-Id: <20190729221101.228240-1-saravanak@google.com> Mime-Version: 1.0 X-Mailer: git-send-email 2.22.0.709.g102302147b-goog Subject: [PATCH v8 0/7] Solve postboot supplier cleanup and optimize probe ordering From: Saravana Kannan To: Rob Herring , Mark Rutland , Greg Kroah-Hartman , "Rafael J. Wysocki" , Frank Rowand Cc: Saravana Kannan , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, David Collins , kernel-team@android.com Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Add device-links to track functional dependencies between devices after they are created (but before they are probed) by looking at their common DT bindings like clocks, interconnects, etc. Having functional dependencies automatically added before the devices are probed, provides the following benefits: - Optimizes device probe order and avoids the useless work of attempting probes of devices that will not probe successfully (because their suppliers aren't present or haven't probed yet). For example, in a commonly available mobile SoC, registering just one consumer device's driver at an initcall level earlier than the supplier device's driver causes 11 failed probe attempts before the consumer device probes successfully. This was with a kernel with all the drivers statically compiled in. This problem gets a lot worse if all the drivers are loaded as modules without direct symbol dependencies. - Supplier devices like clock providers, interconnect providers, etc need to keep the resources they provide active and at a particular state(s) during boot up even if their current set of consumers don't request the resource to be active. This is because the rest of the consumers might not have probed yet and turning off the resource before all the consumers have probed could lead to a hang or undesired user experience. Some frameworks (Eg: regulator) handle this today by turning off "unused" resources at late_initcall_sync and hoping all the devices have probed by then. This is not a valid assumption for systems with loadable modules. Other frameworks (Eg: clock) just don't handle this due to the lack of a clear signal for when they can turn off resources. This leads to downstream hacks to handle cases like this that can easily be solved in the upstream kernel. By linking devices before they are probed, we give suppliers a clear count of the number of dependent consumers. Once all of the consumers are active, the suppliers can turn off the unused resources without making assumptions about the number of consumers. By default we just add device-links to track "driver presence" (probe succeeded) of the supplier device. If any other functionality provided by device-links are needed, it is left to the consumer/supplier devices to change the link when they probe. v1 -> v2: - Drop patch to speed up of_find_device_by_node() - Drop depends-on property and use existing bindings v2 -> v3: - Refactor the code to have driver core initiate the linking of devs - Have driver core link consumers to supplier before it's probed - Add support for drivers to edit the device links before probing v3 -> v4: - Tested edit_links() on system with cyclic dependency. Works. - Added some checks to make sure device link isn't attempted from parent device node to child device node. - Added way to pause/resume sync_state callbacks across of_platform_populate(). - Recursively parse DT node to create device links from parent to suppliers of parent and all child nodes. v4 -> v5: - Fixed copy-pasta bugs with linked list handling - Walk up the phandle reference till I find an actual device (needed for regulators to work) - Added support for linking devices from regulator DT bindings - Tested the whole series again to make sure cyclic dependencies are broken with edit_links() and regulator links are created properly. v5 -> v6: - Split, squashed and reordered some of the patches. - Refactored the device linking code to follow the same code pattern for any property. v6 -> v7: - No functional changes. - Renamed i to index - Added comment to clarify not having to check property name for every index - Added "matched" variable to clarify code. No functional change. - Added comments to include/linux/device.h for add_links() v7 -> v8: - Rebased on top of linux-next to handle device link changes in [1] [1] - https://lore.kernel.org/lkml/2305283.AStDPdUUnE@kreacher/ -Saravana Saravana Kannan (7): driver core: Add support for linking devices during device addition driver core: Add edit_links() callback for drivers of/platform: Add functional dependency link from DT bindings driver core: Add sync_state driver/bus callback of/platform: Pause/resume sync state during init and of_platform_populate() of/platform: Create device links for all child-supplier depencencies of/platform: Don't create device links for default busses .../admin-guide/kernel-parameters.txt | 5 + drivers/base/core.c | 168 ++++++++++++++++ drivers/base/dd.c | 29 +++ drivers/of/platform.c | 189 ++++++++++++++++++ include/linux/device.h | 55 +++++ 5 files changed, 446 insertions(+) -- 2.22.0.709.g102302147b-goog