From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759380AbcISHDt (ORCPT ); Mon, 19 Sep 2016 03:03:49 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:60978 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751414AbcISHDn (ORCPT ); Mon, 19 Sep 2016 03:03:43 -0400 Date: Mon, 19 Sep 2016 09:03:46 +0200 From: Greg KH To: Joel Stanley , Mathias Nyman Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH] xhci: do not halt the secondary HCD Message-ID: <20160919070346.GA29827@kroah.com> References: <20160919063545.2055-1-joel@jms.id.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160919063545.2055-1-joel@jms.id.au> User-Agent: Mutt/1.7.0 (2016-08-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Sep 19, 2016 at 04:05:45PM +0930, Joel Stanley wrote: > We can't halt the secondary HCD, because it's also the primary HCD, > which will cause problems if we have devices attached to the primary > HCD, like a keyboard. > > We've been carrying this in our Linux-as-a-bootloader environment for a little > while now. The machines all have the same TI TUSB73x0 part, and when we kexec > the devices don't come back until a system power cycle. > > I'd like some advice on an acceptable way to upstream the fix, so that the xhci > device survives kexec. Any reason you didn't cc: Mathias? And have you tried 4.8-rc kernels? I thought we just fixed an issue around secondary HCDs... thanks, greg k-h