From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [PATCH] EHCI/Xen: propagate controller reset information to hypervisor Date: Tue, 18 Sep 2012 11:15:19 -0400 Message-ID: <20120918151519.GB30940@phenom.dumpdata.com> References: <505875B6020000780009C01D@nat28.tlf.novell.com> <20120918144230.GC19332@phenom.dumpdata.com> <20120918150649.GA24798@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20120918150649.GA24798@kroah.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Greg KH Cc: linux-usb@vger.kernel.org, stern@rowland.harvard.edu, Jan Beulich , xen-devel List-Id: xen-devel@lists.xenproject.org On Tue, Sep 18, 2012 at 04:06:49PM +0100, Greg KH wrote: > On Tue, Sep 18, 2012 at 10:42:30AM -0400, Konrad Rzeszutek Wilk wrote: > > On Tue, Sep 18, 2012 at 12:23:02PM +0100, Jan Beulich wrote: > > > Just like for the in-tree early console debug port driver, the > > > hypervisor - when using a debug port based console - also needs to be > > > told about controller resets, so it can suppress using and then > > > re-initialize the debug port accordingly. > > > > > > Other than the in-tree driver, the hypervisor driver 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 > > > > Acked-by: Konrad Rzeszutek Wilk > > > > on the *xen* parts. > > So, I'm guessing this should go in through the USB tree? If there are > no objections, I'll do that. No objections. Thank you.