Hi,
search for FSG_STATE_CONFIG_CHANGE and FSG_STATE_INTERFACE_CHANGE in
file_storage.c and f_mass_storage.c
something seems missing in f_mass_storage.c
cheers,
-roger
On 04/06/2011 08:02 PM, ext Sonasath, Moiz wrote:
All,
I am working on android kernel based on K35, and I see these bunch of device
configure failures. Any pointers would really help.
Configuring device, set configuration = 0x1
NOTE: It is expected the device has reset the data toggles on all Bulk endpoints
after the above SetConfiguration call
Setting device interface, interface number = 0x0 and alternate setting = 0x0
NOTE: It is expected the device has reset the data toggles on all Bulk endpoints
after the above SetInterface call
Issuing Get Max LUN request
Max LUN value = 0
Getting Device Type
Issuing INQUIRY
Issuing CBW (attempt #1):
|----- CBW LUN = 0x0
|----- CBW Flags = 0x80
|----- CBW Data Transfer Length = 0x24
|----- CBW CDB Length = 0x6
|----- CBW CDB-00 = 0x12
|----- CBW CDB-01 = 0x0
|----- CBW CDB-02 = 0x0
|----- CBW CDB-03 = 0x0
|----- CBW CDB-04 = 0x24
|----- CBW CDB-05 = 0x0
Issuing DATA IN
DATA Bulk Request timed out!
Failed DATA phase : should have been success or stall!
(5.2.3) Devices must consider the CBW meaningful if no reserved bits
are set, the LUN number indicates a LUN supported by the device,
bCBWCBLength is in the range of 1 through 16, and the length and
content of the CBWCB field are appropriate to the SubClass.
BOTCommonMSCRequest failed: error=80004000
Re-enumerating device
Detected hard error, issuing BOT MSC Reset
Failed INQUIRY request
(5.7.1) All devices must support the commands marked as required in 4.2 based
on PDT. Devices that support all the commands marked as required for Bootable
devices will
be reported as Bootable.
Unconfiguring the device
Get configuration failed
--
Regards
Moiz Sonasath
Android Kernel Team
--
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
