From: Saravana Kannan <saravanak@google.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Saravana Kannan <saravanak@google.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
kernel-team@android.com, linux-kernel@vger.kernel.org
Subject: [PATCH v1] driver core: fw_devlink: Don't create device links for devices not on a bus
Date: Tue, 31 Aug 2021 15:45:10 -0700 [thread overview]
Message-ID: <20210831224510.703253-1-saravanak@google.com> (raw)
Devices that are not on a bus will never have a driver bound to it. So,
fw_devlink should not create device links for it as it can cause probe
issues[1] or sync_state() call back issues[2].
[1] - https://lore.kernel.org/lkml/CAGETcx_xJCqOWtwZ9Ee2+0sPGNLM5=F=djtbdYENkAYZa0ynqQ@mail.gmail.com/
[2] - https://lore.kernel.org/lkml/CAPDyKFo9Bxremkb1dDrr4OcXSpE0keVze94Cm=zrkOVxHHxBmQ@mail.gmail.com/
Fixes: f9aa460672c9 ("driver core: Refactor fw_devlink feature")
Reported-by: Ulf Hansson <ulf.hansson@linaro.org>
Reported-by: Marek Szyprowski <m.szyprowski@samsung.com>
Signed-off-by: Saravana Kannan <saravanak@google.com>
---
drivers/base/core.c | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/drivers/base/core.c b/drivers/base/core.c
index f6360490a4a3..304a06314656 100644
--- a/drivers/base/core.c
+++ b/drivers/base/core.c
@@ -1719,8 +1719,24 @@ static int fw_devlink_create_devlink(struct device *con,
struct device *sup_dev;
int ret = 0;
+ /*
+ * If a consumer device is not on a bus (i.e. a driver will never bind
+ * to it), it doesn't make sense for fw_devlink to create device links
+ * for it.
+ */
+ if (con->bus == NULL)
+ return -EINVAL;
+
sup_dev = get_dev_from_fwnode(sup_handle);
if (sup_dev) {
+ /*
+ * If a supplier device is not on a bus (i.e. a driver will
+ * never bind to it), it doesn't make sense for fw_devlink to
+ * create device links for it.
+ */
+ if (sup_dev->bus == NULL)
+ return -EINVAL;
+
/*
* If it's one of those drivers that don't actually bind to
* their device using driver core, then don't wait on this
--
2.33.0.259.gc128427fd7-goog
next reply other threads:[~2021-08-31 22:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 22:45 Saravana Kannan [this message]
2021-09-01 6:24 ` [PATCH v1] driver core: fw_devlink: Don't create device links for devices not on a bus Greg Kroah-Hartman
2021-09-01 6:57 ` Saravana Kannan
2021-09-01 7:14 ` Greg Kroah-Hartman
2021-09-01 21:55 ` Saravana Kannan
2021-09-01 22:11 ` Ulf Hansson
2021-09-01 15:44 ` Ulf Hansson
2021-09-01 21:53 ` Saravana Kannan
2021-09-01 22:17 ` Ulf Hansson
2021-09-02 0:16 ` Saravana Kannan
2021-09-02 1:43 ` Saravana Kannan
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=20210831224510.703253-1-saravanak@google.com \
--to=saravanak@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=rafael@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