[PATCH] ehci: make debug port in-use detection functional again

2012-12-19 Thread Jan Beulich
ff-by: Jan Beulich Cc: Alan Stern Cc: Konrad Rzeszutek Wilk --- drivers/usb/host/ehci-pci.c | 39 --- 1 file changed, 20 insertions(+), 19 deletions(-) --- 3.7/drivers/usb/host/ehci-pci.c +++ 3.7-ehci-init-order/drivers/usb/host/ehci-pci.c @@ -192,6 +1

Re: [PATCH, v3] fix build with XEN and EARLY_PRINTK_DBGP enabled but USB_SUPPORT disabled

2012-11-02 Thread Jan Beulich
>>> On 02.11.12 at 18:01, Greg KH wrote: > On Fri, Nov 02, 2012 at 04:54:47PM +, Jan Beulich wrote: >> >>> On 02.11.12 at 17:23, Greg KH wrote: >> > On Fri, Nov 02, 2012 at 08:38:07AM +, Jan Beulich wrote: >> >> Since there

[PATCH] fix build of EHCI debug port code when USB_CHIPIDEA but !USB_EHCI_HCD

2012-11-02 Thread Jan Beulich
Relax condition of building the reset interface stubs in drivers/usb/early/ehci-dbgp.c from USB_EHCI_HCD to just USB, to also cover the chipidea driver re-using code from ehci-hcd. Reported-by: Randy Dunlap Signed-off-by: Jan Beulich Acked-by: Alan Stern Cc: Konrad Rzeszutek Wilk Cc: Stefano

Re: [PATCH, v3] fix build with XEN and EARLY_PRINTK_DBGP enabled but USB_SUPPORT disabled

2012-11-02 Thread Jan Beulich
>>> On 02.11.12 at 17:23, Greg KH wrote: > On Fri, Nov 02, 2012 at 08:38:07AM +, Jan Beulich wrote: >> Since there's no possible caller of dbgp_external_startup() and > > > > Please just send the incremental patch, in a format that I can apply it > (hi

Re: linux-next: Tree for Oct 31 (ehci, dbgp)

2012-11-02 Thread Jan Beulich
>>> On 02.11.12 at 15:01, Alan Stern wrote: > On Thu, 1 Nov 2012, Jan Beulich wrote: > >> >>> Alan Stern 11/01/12 9:39 PM >>> >> >On Thu, 1 Nov 2012, Jan Beulich wrote: >> >> >>> Alan Stern 11/01/12 4:28 PM >>> >

[PATCH, v3] fix build with XEN and EARLY_PRINTK_DBGP enabled but USB_SUPPORT disabled

2012-11-02 Thread Jan Beulich
the merge f1c6872e4980bc4078cfaead05f892b3d78dea64. Reported-by: Randy Dunlap Signed-off-by: Jan Beulich Cc: Alan Stern Cc: Stefano Stabellini --- (incremental patch attached, in case that one is preferred) v3: Relax condition from USB_EHCI_HCD to just USB, to also cover the chipidea driver re-using code from ehci-hcd.

Re: linux-next: Tree for Oct 31 (ehci, dbgp)

2012-11-01 Thread Jan Beulich
>>> Alan Stern 11/01/12 9:39 PM >>> >On Thu, 1 Nov 2012, Jan Beulich wrote: >> >>> Alan Stern 11/01/12 4:28 PM >>> >> >Evidently we need to change your new test in >> >drivers/usb/early/ehci-dbgp.c to: >> > >

Re: linux-next: Tree for Oct 31 (ehci, dbgp)

2012-11-01 Thread Jan Beulich
>>> Alan Stern 11/01/12 4:28 PM >>> >On Wed, 31 Oct 2012, Randy Dunlap wrote: >> on x86_64: >> >> drivers/built-in.o: In function `ehci_reset': >> host.c:(.text+0x542a7e): undefined reference to `dbgp_reset_prep' >> host.c:(.text+0x542b75): undefined reference to `dbgp_external_startup' >> driver

Re: [PATCH, v2] fix build with XEN and EARLY_PRINTK_DBGP enabled but USB_SUPPORT disabled

2012-10-30 Thread Jan Beulich
>>> On 29.10.12 at 17:50, Greg KH wrote: > On Mon, Oct 29, 2012 at 04:45:54PM +, Jan Beulich wrote: >> Since there's no possible caller of dbgp_external_startup() and >> dbgp_reset_prep() when !USB_EHCI_HCD, there's no point in building and >> expo

Re: [PATCH, v2] fix build with XEN and EARLY_PRINTK_DBGP enabled but USB_SUPPORT disabled

2012-10-30 Thread Jan Beulich
>>> On 29.10.12 at 23:17, Alan Stern wrote: > On Mon, 29 Oct 2012, Jan Beulich wrote: > >> Since there's no possible caller of dbgp_external_startup() and >> dbgp_reset_prep() when !USB_EHCI_HCD, there's no point in building and >> exporting these func

[PATCH, v2] fix build with XEN and EARLY_PRINTK_DBGP enabled but USB_SUPPORT disabled

2012-10-29 Thread Jan Beulich
the merge f1c6872e4980bc4078cfaead05f892b3d78dea64. Reported-by: Randy Dunlap Signed-off-by: Jan Beulich Cc: Stefano Stabellini Cc: Alan Stern --- v2: Switch the dependency from USB_SUPPORT to USB_EHCI_HCD as requested by Alan (albeit I don't really agree to that change). --- arch/x86/kernel/cpu/perf_ev

[PATCH] EHCI/Xen: propagate controller reset information to hypervisor

2012-09-18 Thread Jan Beulich
actually cares about doing this only for the device where the debug is port actually in use, i.e. it needs to be told the coordinates of the device being reset (quite obviously, leveraging the addition done for that would likely benefit the in-tree driver too). Signed-off-by: Jan Beulich --- drivers