| commit | deafeb24e8a846da8555e68f4bcf651daa8a4ed1 | |
| author | Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com> | |
| Fri, 8 Jul 2011 05:51:21 +0000 (8 14:51 +0900) | ||
| committer | Felipe Balbi <balbi@ti.com> | |
| Fri, 8 Jul 2011 09:47:37 +0000 (8 12:47 +0300) | ||
| tree | ba19bb658a0af42b2eab10d96f0a76b47df144b2 | treesnapshot (tar.gz zip) |
| parent | 5db05c09ac107ef957b7a052d7bba8190c93b460 | commitdiff |
usb: gadget: r8a66597-udc: fix cannot connect after rmmod gadget driver
When we run rmmod a gadget driver, the driver will call
disable_controller(). Then, because the bit of USBE in SYSCFG0 was
cleared in on_chip=1 mode, we could not connect the usb when we run
insmod a gadget driver next time.
This patch also cleans up probe() and ->stop() about unnecessary
init_controller().
Signed-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Signed-off-by: Felipe Balbi <balbi@ti.com>
When we run rmmod a gadget driver, the driver will call
disable_controller(). Then, because the bit of USBE in SYSCFG0 was
cleared in on_chip=1 mode, we could not connect the usb when we run
insmod a gadget driver next time.
This patch also cleans up probe() and ->stop() about unnecessary
init_controller().
Signed-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Signed-off-by: Felipe Balbi <balbi@ti.com>
| drivers/usb/gadget/r8a66597-udc.c | diffblobblamehistory |