Doug,
I started writing the interface you put forth in your email. I
am currently debugging it in UML so I can generate the error
conditions in a control manner. I still have some stuff to look
at in the error handler with it running in this mode as it
previously expected no one else to be possibly doing operations
on the host. This could be the case if other LLDD's use this
interface and have another device that happens to timeout an IO
post a device being set offline.
A clarification question below.
Doug Ledford [[EMAIL PROTECTED]] wrote:
> So, what you should be doing in
> order to be both a nice scsi host that plays well with the generic
> mechanism we have in place is when you get this removal event, you should
> be free'ing all the state you needed about the usb bus and such and taking
> this usb device off line or whatever you do. Then let the scsi mid layer
> clean up at it's leisure. You don't need to worry about it because the
> only thing you will have left is to wait for the scsi subsys to call you
> when it's time to delete things. You don't even have to keep device
> references around because we pass those in to your deletion routines
> anyway.
>
> > I want to be able to inform the SCSI mid-layer, which will then inform
> > higher layers, that the device is gone.
>
> scsi_set_device_offline() as we've been discussing.
>
I assumed that the hotplug event would only come from this function if
no commands where outstanding. If there where commands outstanding the
event would not be generated until the error handler gained ownership of
all the commands.
-andmike
--
Michael Anderson
[EMAIL PROTECTED]
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
