This is a note to let you know that I've just added the patch titled
usb: musb: omap: fix crash when musb glue (omap) gets initialized
to the 3.3-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
usb-musb-omap-fix-crash-when-musb-glue-omap-gets-initialized.patch
and it can be found in the queue-3.3 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.
>From 3006dc8c627d738693e910c159630e4368c9e86c Mon Sep 17 00:00:00 2001
From: Kishon Vijay Abraham I <[email protected]>
Date: Wed, 21 Mar 2012 21:30:20 +0530
Subject: usb: musb: omap: fix crash when musb glue (omap) gets initialized
From: Kishon Vijay Abraham I <[email protected]>
commit 3006dc8c627d738693e910c159630e4368c9e86c upstream.
pm_runtime_enable is being called after omap2430_musb_init. Hence
pm_runtime_get_sync in omap2430_musb_init does not have any effect (does
not enable clocks) resulting in a crash during register access. It is
fixed here.
Signed-off-by: Kishon Vijay Abraham I <[email protected]>
Signed-off-by: Felipe Balbi <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
drivers/usb/musb/omap2430.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/drivers/usb/musb/omap2430.c
+++ b/drivers/usb/musb/omap2430.c
@@ -451,14 +451,14 @@ static int __init omap2430_probe(struct
goto err2;
}
+ pm_runtime_enable(&pdev->dev);
+
ret = platform_device_add(musb);
if (ret) {
dev_err(&pdev->dev, "failed to register musb device\n");
goto err2;
}
- pm_runtime_enable(&pdev->dev);
-
return 0;
err2:
Patches currently in stable-queue which might be from [email protected] are
queue-3.3/usb-gadget-udc-core-fix-asymmetric-calls-in-remove_driver.patch
queue-3.3/usb-musb-omap-fix-crash-when-musb-glue-omap-gets-initialized.patch
queue-3.3/usb-musb-omap-fix-the-error-check-for-pm_runtime_get_sync.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
