Re: Expose port sequence in the xhci extended capabilities table to usb core.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.

Sarah Sharp
--
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


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux