Gitweb:     
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=2e2eb83ffd1aeb92bf8793eea892b5bc05a993ea
Commit:     2e2eb83ffd1aeb92bf8793eea892b5bc05a993ea
Parent:     241ca64fc55bd2b676890472880e2d2d86cfae82
Author:     Alan Stern <[EMAIL PROTECTED]>
AuthorDate: Tue Dec 4 14:35:15 2007 -0500
Committer:  Greg Kroah-Hartman <[EMAIL PROTECTED]>
CommitDate: Fri Feb 1 14:34:54 2008 -0800

    USB: add usbfs stubs for suspend and resume
    
    This patch (as1022b) adds stub methods for suspend and resume to the
    usbfs driver.  There isn't much they can do since there's no way to
    inform a user task about the events.  But it's important to have the
    stubs, because an upcoming change to usbcore will automatically unbind
    drivers that don't have those methods when a suspend occurs.
    
    Signed-off-by: Alan Stern <[EMAIL PROTECTED]>
    Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
---
 drivers/usb/core/devio.c |   15 +++++++++++++++
 1 files changed, 15 insertions(+), 0 deletions(-)

diff --git a/drivers/usb/core/devio.c b/drivers/usb/core/devio.c
index 85ec65a..32e5591 100644
--- a/drivers/usb/core/devio.c
+++ b/drivers/usb/core/devio.c
@@ -402,10 +402,25 @@ static void driver_disconnect(struct usb_interface *intf)
        destroy_async_on_interface(ps, ifnum);
 }
 
+/* The following routines are merely placeholders.  There is no way
+ * to inform a user task about suspend or resumes.
+ */
+static int driver_suspend(struct usb_interface *intf, pm_message_t msg)
+{
+       return 0;
+}
+
+static int driver_resume(struct usb_interface *intf)
+{
+       return 0;
+}
+
 struct usb_driver usbfs_driver = {
        .name =         "usbfs",
        .probe =        driver_probe,
        .disconnect =   driver_disconnect,
+       .suspend =      driver_suspend,
+       .resume =       driver_resume,
 };
 
 static int claimintf(struct dev_state *ps, unsigned int ifnum)
-
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to