Hi: > 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 ? 2.6.16 uclinux version > Can you check whether you are getting USBINT, USBERRINT, IAA interrupts. If I change register manually, like reset port, I can get port change status interrupt. I will double confirm the 3 interrupt you mentioned. > 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. Ok, I will check it. BTW, I have some question about port reset sequence. We finish port reset sequence in get_port_status And below is final step of reset port: // what happens if HCS_N_CC(params) == 0 ? port_status |= PORT_OWNER; port_status &= ~PORT_RWC_BITS; ****2 ehci_writel(ehci, port_status, status_reg); in xxxx2, we should set port_status |= PORT_RWC_BITS, right? since PORT_RWC_BITS are writing clear. appreciate your help, miloody >> 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
