From: Amit Sunil Dhamne <amitsd@google.com>
To: heikki.krogerus@linux.intel.com, gregkh@linuxfoundation.org
Cc: badhri@google.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, kyletso@google.com,
rdbabiera@google.com, Amit Sunil Dhamne <amitsd@google.com>
Subject: [PATCH v1] usb: roles: add lockdep class key to struct usb_role_switch
Date: Tue, 13 Aug 2024 15:42:11 -0700 [thread overview]
Message-ID: <20240813224216.132619-1-amitsd@google.com> (raw)
There can be multiple role switch devices running on a platform. Given
that lockdep is not capable of differentiating between locks of
different instances, false positive warnings for circular locking are
reported. To prevent this, register unique lockdep key for each of the
individual instances.
Signed-off-by: Amit Sunil Dhamne <amitsd@google.com>
---
drivers/usb/roles/class.c | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/drivers/usb/roles/class.c b/drivers/usb/roles/class.c
index d7aa913ceb8a..807a8f18ec20 100644
--- a/drivers/usb/roles/class.c
+++ b/drivers/usb/roles/class.c
@@ -11,6 +11,7 @@
#include <linux/usb/role.h>
#include <linux/property.h>
#include <linux/device.h>
+#include <linux/lockdep.h>
#include <linux/module.h>
#include <linux/mutex.h>
#include <linux/slab.h>
@@ -33,6 +34,10 @@ struct usb_role_switch {
usb_role_switch_set_t set;
usb_role_switch_get_t get;
bool allow_userspace_control;
+
+#ifdef CONFIG_LOCKDEP
+ struct lock_class_key key;
+#endif
};
#define to_role_switch(d) container_of(d, struct usb_role_switch, dev)
@@ -396,6 +401,11 @@ usb_role_switch_register(struct device *parent,
sw->registered = true;
+#ifdef CONFIG_LOCKDEP
+ lockdep_register_key(&sw->key);
+ lockdep_set_class(&sw->lock, &sw->key);
+#endif
+
/* TODO: Symlinks for the host port and the device controller. */
return sw;
@@ -412,6 +422,11 @@ void usb_role_switch_unregister(struct usb_role_switch *sw)
{
if (IS_ERR_OR_NULL(sw))
return;
+
+#ifdef CONFIG_LOCKDEP
+ lockdep_unregister_key(&sw->key);
+#endif
+
sw->registered = false;
if (dev_fwnode(&sw->dev))
component_del(&sw->dev, &connector_ops);
base-commit: 38343be0bf9a7d7ef0d160da5f2db887a0e29b62
--
2.46.0.76.ge559c4bf1a-goog
next reply other threads:[~2024-08-13 22:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 22:42 Amit Sunil Dhamne [this message]
2024-08-14 4:49 ` Greg KH
2024-08-15 4:27 ` Amit Sunil Dhamne
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=20240813224216.132619-1-amitsd@google.com \
--to=amitsd@google.com \
--cc=badhri@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=kyletso@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rdbabiera@google.com \
/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
all inboxes | Powered by JetHome®