I hope that the below information might be helpful for you to debug the
problem.
The Linux EHCI driver enables asynchronous schedule while linking QH &
disables while unlinking the last QH of async list.
See start_unlink_async & qh_link_async functions. grep for CMD_ASE bit.
Which linux version you are using ?
Can you check whether you are getting USBINT, USBERRINT, IAA interrupts.
These interrupts will be generated while data transfers are going on.
See USB Status register description.
Do you have any bus doctor which can capture the usb traffic ? Check whether
HC is sending usb packets to the device or not.
-- Naveen
----- Original Message -----
From: "vichy" <vichy.kuo@xxxxxxxxx>
To: "Naveen Mamindlapalli" <mamindlapalli.naveen@xxxxxxxxxxx>
Cc: <linux-usb@xxxxxxxxxxxxxxx>
Sent: Tuesday, March 17, 2009 12:50 PM
Subject: Re: Drivers need for usb file system
Hi
2009/3/16 Naveen@moschip <mamindlapalli.naveen@xxxxxxxxxxx>:
Hi,
Did you mapped the correct HW interrupt to your driver ? Just check
whether
you are getting any interrupt for the port connection/disconnection by
putting traces in the interrupt handler.
-- Naveen
thanks for your kind suggestion.
When I unplug or plug my usb device, I can see port change interrupt
received my handler.
But I say the host command is 0x00010009, that means Asy is not enabled.
If Asy is not enabled, host cannot send control qtd to device.
Did linux driver enable it when send control pipe then disable it
after finishing it? If so, where it is?
appreciate your help,
vichy
----- Original Message -----
From: "vichy" <vichy.kuo@xxxxxxxxx>
To: <linux-usb@xxxxxxxxxxxxxxx>
Sent: Monday, March 16, 2009 7:56 PM
Subject: Re: Drivers need for usb file system
2009/3/12 Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>:
On Thu, 12 Mar 2009, Greg KH wrote:
On Thu, Mar 12, 2009 at 10:26:47PM +0800, vichy wrote:
> Dear all:
> I am porting ehci-host driver on my arm platform.
> So far the host seems correctly enabled, but I have no idea how to
> read the contents of USB storages as Ubuntu does.
> And I decide to build the drivers I need one by one.
> If someone knows the whole list of drivers I need, please let me know.
> ( The module utility is fail on my platform, so I use build-in to
> develop driver.)
usb-storage.
You also will need scsi_mod (which is required by usb-storage) and
sd_mod.
Alan Stern
Hi:
I use uclinux to port ehci host and I have 2 questions below:
1.
When porting the host driver, I have error message as below.
EHCI_TEST-ehci EHCI_TEST-ehci.0: port 1 high speed
EHCI_TEST-ehci EHCI_TEST-ehci.0: GetStatus port 1 status 00000d
sig=se0 PEC PE CONNECT
usb 1-1: device descriptor read/64, error -110
EHCI_TEST-ehci EHCI_TEST-ehci.0: port 1 high speed
EHCI_TEST-ehci EHCI_TEST-ehci.0: GetStatus port 1 status 00000d
sig=se0 PEC PE CONNECT
usb 1-1: device descriptor read/64, error -110
EHCI_TEST-ehci EHCI_TEST-ehci.0: port 1 high speed
EHCI_TEST-ehci EHCI_TEST-ehci.0: GetStatus port 1 status 00000d
sig=se0 PEC PE CONNECT
usb 1-1: new high speed USB device using EHCI_TEST-ehci and address 3
EHCI_TEST-ehci EHCI_TEST-ehci.0: port 1 high speed
EHCI_TEST-ehci EHCI_TEST-ehci.0: GetStatus port 1 status 00000d
sig=se0 PEC PE CONNECT
usb 1-1: device descriptor read/64, error -110
EHCI_TEST-ehci EHCI_TEST-ehci.0: port 1 high speed
EHCI_TEST-ehci EHCI_TEST-ehci.0: GetStatus port 1 status 00000d
sig=se0 PEC PE CONNECT
usb 1-1: device descriptor read/64, error -110
EHCI_TEST-ehci EHCI_TEST-ehci.0: port 1 high speed
EHCI_TEST-ehci EHCI_TEST-ehci.0: GetStatus port 1 status 00000d
sig=se0 PEC PE CONNECT
usb 1-1: new high speed USB device using EHCI_TEST-ehci and address 4
usb 1-1: device not accepting address 4, error -110
EHCI_TEST-ehci EHCI_TEST-ehci.0: port 1 high speed
EHCI_TEST-ehci EHCI_TEST-ehci.0: GetStatus port 1 status 00000d
sig=se0 PEC PE CONNECT
usb 1-1: new high speed USB device using EHCI_TEST-ehci and address 5
usb 1-1: device not accepting address 5, error -110
The error comes from hub_port_connect_change, while doing the
config_tries.
Is there debug option which can let me see the content of urb such
that I can make sure the qhd is properly set.
2. from the message at the end of letter, it seems I duplicate my
driver in sysfs.
I have searched the source but I cannot find out where it is.
what I do is modifying ehci-au1xxx.c.
Does the problem 1 come from problem2?
( I don't think so, since port communication should not have any
relationship with sysfs)
appreciate your help,
vichy
sysfs: duplicate filename 'EHCI_TEST-ehci' can not be created
------------[ cut here ]------------
WARNING: at fs/sysfs/dir.c:424 sysfs_add_one+0xb8/0xdc()
[<80063578>] (dump_stack+0x0/0x14) from [<8006cf50>]
(warn_on_slowpath+0x48/0x5c)
[<8006cf08>] (warn_on_slowpath+0x0/0x5c) from [<800d0450>]
(sysfs_add_one+0xb8/0xdc)
r6:83d9a850 r5:83c15e6c r4:83d9a850
[<800d0398>] (sysfs_add_one+0x0/0xdc) from [<800d0550>]
(create_dir+0x5c/0xb4)
r6:83d8b550 r5:83c15e6c r4:83d9a850
[<800d04f4>] (create_dir+0x0/0xb4) from [<800d0600>]
(sysfs_create_dir+0x38/0x60)
r7:83c04a14 r6:00000000 r5:00000000 r4:83d8b550
[<800d05c8>] (sysfs_create_dir+0x0/0x60) from [<800d5cec>]
(kobject_add_internal+0x74/0x1b0)
r4:83d8b550
[<800d5c78>] (kobject_add_internal+0x0/0x1b0) from [<800d5e6c>]
(kobject_add_varg+0x44/0x4c)
r7:8001503c r6:00000000 r5:00000000 r4:83d8b550
[<800d5e28>] (kobject_add_varg+0x0/0x4c) from [<800d5ea4>]
(kobject_init_and_add+0x30/0x34)
r6:00000000 r5:00000000 r4:83d8b550
[<800d5e78>] (kobject_init_and_add+0x4/0x34) from [<800f0cdc>]
(bus_add_driver+0x90/0x24c)
r5:80154d50 r4:00000000
[<800f0c4c>] (bus_add_driver+0x0/0x24c) from [<800f1d3c>]
(driver_register+0x40/0xec)
[<800f1cfc>] (driver_register+0x0/0xec) from [<800f3838>]
(platform_driver_register+0x6c/0x88)
r7:8001503c r6:ffffffed r5:00000000 r4:8015ec08
[<800f37cc>] (platform_driver_register+0x0/0x88) from [<80013c48>]
(ehci_hcd_init+0x58/0x88)
[<80013bf0>] (ehci_hcd_init+0x0/0x88) from [<80008bf0>]
(kernel_init+0xa4/0x2e0)
r4:00000000
[<80008b4c>] (kernel_init+0x0/0x2e0) from [<8006f764>] (do_exit+0x0/0x63c)
---[ end trace 18179480a435c8ba ]---
..
--
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
The information contained in this email and any attachments is
confidential
and may be subject to copyright or other intellectual property protection.
If you are not the intended recipient, you are not authorized to use or
disclose this information, and we request that you notify us by reply mail
or telephone and delete the original message from your mail system.
The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system.
--
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
