From: Abhijeet@vger.kernel.org, Kumar@vger.kernel.org
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jaejoong Kim <climbbb.kim@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
Abhijeet Kumar <abhijeet.kumar@intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] USB :core :Prevent USB devices to autosuspend while setting interface
Date: Fri, 10 Nov 2017 21:32:07 +0530 [thread overview]
Message-ID: <1510329728-26491-1-git-send-email-abhijeet.kumar@intel.com> (raw)
From: Abhijeet Kumar <abhijeet.kumar@intel.com>
Runtime resume USB device in order to ensure that PM framework knows
that the we might be using the device in a short time and doesn't
autosuspend the device while we update it's interface. Without this
change, if device autosuspends and the kernel polling for block
devices is disabled through sysfs at runtime or through bootargs, then
storage devices might never unmount since the disconnect IRQ wont be
kicked at all.
Signed-off-by: Abhijeet Kumar <abhijeet.kumar@intel.com>
---
drivers/usb/core/message.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/drivers/usb/core/message.c b/drivers/usb/core/message.c
index 371a07d874a3..54a9accf88cb 100644
--- a/drivers/usb/core/message.c
+++ b/drivers/usb/core/message.c
@@ -1305,6 +1305,11 @@ int usb_set_interface(struct usb_device *dev, int interface, int alternate)
if (iface->unregistering)
return -ENODEV;
+ /*Letting runtime PM know that we wish to use the device in a
+ * short time.
+ */
+ pm_runtime_get(&iface->dev);
+
alt = usb_altnum_to_altsetting(iface, alternate);
if (!alt) {
dev_warn(&dev->dev, "selecting invalid altsetting %d\n",
--
1.9.1
next reply other threads:[~2017-11-10 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 16:02 Abhijeet, Kumar [this message]
2017-11-10 16:07 ` Greg Kroah-Hartman
2017-11-10 16:30 ` Alan Stern
-- strict thread matches above, loose matches on Subject: below --
2017-11-10 12:49 Abhijeet, Kumar
2017-11-10 12:54 ` Felipe Balbi
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=1510329728-26491-1-git-send-email-abhijeet.kumar@intel.com \
--to=abhijeet@vger.kernel.org \
--cc=Kumar@vger.kernel.org \
--cc=abhijeet.kumar@intel.com \
--cc=climbbb.kim@gmail.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@kernel.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
all inboxes | Powered by JetHome®