On Wed, Nov 02, 2011 at 04:09:46PM -0400, Richard Retanubun wrote: > Hello, > > I am working on a project where an usb host controller (isp1763-hcd) > is placed on a hot-swappable module. Like pcmcia? PCI Express? > I know on the USB side it supports hot-swap by design. However when > the module is disconnected, it is the cpu-local bus side that is > disconnected (i.e. all access to the isp1763 register/memory space > from the cpu is now undefined). That's just like pci. > The CPU in this case is an MPC8360e and the hcd is on the local bus in GPCM mode. > > My question is: > > If an hcd wants to do damage-control in this mode and fake a message > that says to the upper layer on the usb stack "whatever usb device > that was connected to me is disconnected" what should it do? > Essentially the method will mimic the electrical sequence that > prints "usb 1-1.2: USB disconnect, address 3" on the logs. Do the same thing that the existing pci drivers do, tear themselves down when they get the disconnect message to their drivers that they are going away. You do get this type of callback, right? If not, then your bus code is broken and needs to be fixed, and that's independant of USB. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
