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

2012-12-10 Thread Lan Tianyu
On 2012年12月11日 01:59, Sarah Sharp wrote: > On Mon, Dec 10, 2012 at 11:29:38AM -0500, Alan Stern wrote: >> On Mon, 10 Dec 2012, Lan Tianyu wrote: >> >>> Hi Alan&Greg: >>> We meet a problem that bind usb3.0 port(supper-speed port) with ACPI. >>> The main problem is that the port index num of ss p

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

2012-12-10 Thread Lan Tianyu
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 meth

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

2012-12-10 Thread Sarah Sharp
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

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

2012-12-10 Thread Alan Stern
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

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

2012-12-10 Thread Sarah Sharp
On Mon, Dec 10, 2012 at 02:10:34PM -0500, Alan Stern wrote: > You seem to be saying that core/acpi.c can figure out everything it > needs, given the list of port speeds as described in the xHCI extended > capabilities. But the problem was caused originally by the way we > split the xHCI root hu

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

2012-12-10 Thread Alan Stern
On Mon, 10 Dec 2012, Sarah Sharp wrote: > > Is there any reason the ACPI port number should have any connection > > with the port numbers used by usbcore, even for USB-2 controllers? > > If there is no connection at all, how is Windows supposed to know which > ACPI method turns off which port? Y

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

2012-12-10 Thread Sarah Sharp
On Mon, Dec 10, 2012 at 10:08:24AM -0800, Greg Kroah-Hartman wrote: > On Mon, Dec 10, 2012 at 09:59:32AM -0800, Sarah Sharp wrote: > > On Mon, Dec 10, 2012 at 11:29:38AM -0500, Alan Stern wrote: > > > On Mon, 10 Dec 2012, Lan Tianyu wrote: > > > > > > > Hi Alan&Greg: > > > > We meet a prob

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

2012-12-10 Thread Greg Kroah-Hartman
On Mon, Dec 10, 2012 at 09:44:53AM -0800, Sarah Sharp wrote: > So the problem Tianyu and I were trying to solve is how do we export the > USB port speed list from the xHCI extended capabilities to the USB core > ACPI code that matches USB ports to their ACPI power off method? Ok, but why do you wa

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

2012-12-10 Thread Greg Kroah-Hartman
On Mon, Dec 10, 2012 at 09:59:32AM -0800, Sarah Sharp wrote: > On Mon, Dec 10, 2012 at 11:29:38AM -0500, Alan Stern wrote: > > On Mon, 10 Dec 2012, Lan Tianyu wrote: > > > > > Hi Alan&Greg: > > > We meet a problem that bind usb3.0 port(supper-speed port) with ACPI. > > > The main problem is that

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

2012-12-10 Thread Sarah Sharp
On Mon, Dec 10, 2012 at 11:29:38AM -0500, Alan Stern wrote: > On Mon, 10 Dec 2012, Lan Tianyu wrote: > > > Hi Alan&Greg: > > We meet a problem that bind usb3.0 port(supper-speed port) with ACPI. > > The main problem is that the port index num of ss port in the usb ocre > > is mismatched with i

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

2012-12-10 Thread Sarah Sharp
On Mon, Dec 10, 2012 at 06:53:04AM -0800, Greg Kroah-Hartman wrote: > On Mon, Dec 10, 2012 at 04:42:23PM +0800, Lan Tianyu wrote: > > Hi Alan&Greg: > > We meet a problem that bind usb3.0 port(supper-speed port) with ACPI. > > The main problem is that the port index num of ss port in the usb ocr

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

2012-12-10 Thread Alan Stern
On Mon, 10 Dec 2012, Lan Tianyu wrote: > Hi Alan&Greg: > We meet a problem that bind usb3.0 port(supper-speed port) with ACPI. > The main problem is that the port index num of ss port in the usb ocre > is mismatched with its counterpart in the ACPI table. > The xhci usb3.0 root hub por

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

2012-12-10 Thread Greg Kroah-Hartman
On Mon, Dec 10, 2012 at 04:42:23PM +0800, Lan Tianyu wrote: > Hi Alan&Greg: > We meet a problem that bind usb3.0 port(supper-speed port) with ACPI. > The main problem is that the port index num of ss port in the usb ocre > is mismatched with its counterpart in the ACPI table. Why do you care

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

2012-12-10 Thread Lan Tianyu
Hi Alan&Greg: We meet a problem that bind usb3.0 port(supper-speed port) with ACPI. The main problem is that the port index num of ss port in the usb ocre is mismatched with its counterpart in the ACPI table. The xhci usb3.0 root hub port's index num is based on 0 in the usb core(xh