On 2012年12月11日 03:45, Sarah Sharp wrote: > On Mon, Dec 10, 2012 at 02:43:25PM -0500, Alan Stern wrote: >> On Mon, 10 Dec 2012, Sarah Sharp wrote: >> >>>> Do you think we will ever need to do the mapping in the other >>>> direction? >>> >>> Meaning the xHCI driver would need to know which ACPI method was >>> attached to a raw port? I don't think so. The code in usb-acpi.c >>> should abstract that away from the xHCI driver. >> >> No, I meant will we ever need to translate a "raw" port number into a >> usbcore-style port number and root hub. For example, if an ACPI event >> occurs and it's associated with an ACPI port, we'd want to know which >> port that really was. > > Hmm, I'm not sure. I don't think there are any ACPI events associated > with a port, but Tianyu should be able to answer that question. This is dependent on bios. Currently, I think there is no such demand for usb. For pcie, sata/zpodd, the device can issume remote wakeup after entering into D3clod and so there are wakeup ACPI events for them. But for usb device, device is totally power off and there is no ACPI event for usb port. > > Sarah Sharp > -- Best regards Tianyu Lan -- 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
