From: Saravana Kannan <saravanak@google.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Len Brown <lenb@kernel.org>
Cc: Saravana Kannan <saravanak@google.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
kernel-team@android.com, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: [PATCH v1 2/2] of: platform: Mark bus devices nodes with FWNODE_FLAG_NEVER_PROBES
Date: Wed, 1 Sep 2021 19:55:27 -0700 [thread overview]
Message-ID: <20210902025528.1017391-3-saravanak@google.com> (raw)
In-Reply-To: <20210902025528.1017391-1-saravanak@google.com>
We don't want fw_devlink creating device links for bus devices as
they'll never probe. So mark those device node with this flag.
Signed-off-by: Saravana Kannan <saravanak@google.com>
---
drivers/of/platform.c | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/drivers/of/platform.c b/drivers/of/platform.c
index 74afbb7a4f5e..42b3936d204a 100644
--- a/drivers/of/platform.c
+++ b/drivers/of/platform.c
@@ -392,6 +392,22 @@ static int of_platform_bus_create(struct device_node *bus,
if (!dev || !of_match_node(matches, bus))
return 0;
+ /*
+ * If the bus node has only one compatible string value and it has
+ * matched as a bus node, it's never going to get probed by a device
+ * driver. So flag it as such so that fw_devlink knows not to create
+ * device links with this device.
+ *
+ * This doesn't catch all devices that'll never probe, but this is good
+ * enough for now.
+ *
+ * This doesn't really work for PPC because of how it uses
+ * of_platform_bus_probe() to add normal devices. So ignore PPC cases.
+ */
+ if (!IS_ENABLED(CONFIG_PPC) &&
+ of_property_count_strings(bus, "compatible") == 1)
+ bus->fwnode.flags |= FWNODE_FLAG_NOT_DEVICE;
+
for_each_child_of_node(bus, child) {
pr_debug(" create child: %pOF\n", child);
rc = of_platform_bus_create(child, matches, lookup, &dev->dev, strict);
--
2.33.0.259.gc128427fd7-goog
next prev parent reply other threads:[~2021-09-02 2:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 2:55 [PATCH v1 0/2] Ulf reported an issue[1] with fw_devlink. This series tries to fix that issue Saravana Kannan
2021-09-02 2:55 ` [PATCH v1 1/2] driver core: Add support for FWNODE_FLAG_NEVER_PROBES Saravana Kannan
2021-09-02 2:55 ` Saravana Kannan [this message]
2021-09-02 14:24 ` [PATCH v1 2/2] of: platform: Mark bus devices nodes with FWNODE_FLAG_NEVER_PROBES Rob Herring
2021-09-02 16:57 ` Saravana Kannan
2021-09-02 19:02 ` Rob Herring
2021-09-02 19:28 ` Saravana Kannan
2021-09-03 0:53 ` Rob Herring
2021-09-03 1:15 ` Saravana Kannan
2021-09-03 14:58 ` Rob Herring
2021-09-03 17:06 ` Saravana Kannan
2021-09-03 17:37 ` Rafael J. Wysocki
2021-09-02 17:20 ` Saravana Kannan
2021-09-02 2:56 ` [PATCH v1 0/2] Ulf reported an issue[1] with fw_devlink. This series tries to fix that issue Saravana Kannan
2021-09-02 15:56 ` Rafael J. Wysocki
2021-09-02 16:27 ` Saravana Kannan
2021-09-02 16:31 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210902025528.1017391-3-saravanak@google.com \
--to=saravanak@google.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=ulf.hansson@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).