From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751151AbdKTKnQ (ORCPT ); Mon, 20 Nov 2017 05:43:16 -0500 Received: from mx2.suse.de ([195.135.220.15]:41205 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750764AbdKTKnP (ORCPT ); Mon, 20 Nov 2017 05:43:15 -0500 Message-ID: <1511174342.6213.9.camel@suse.com> Subject: Re: question about usb_rebind_intf From: Oliver Neukum To: Alan Stern , Mathias Nyman Cc: Greg Kroah-Hartman , linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org Date: Mon, 20 Nov 2017 11:39:02 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.20.5 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am Freitag, den 17.11.2017, 13:21 -0500 schrieb Alan Stern: > > The real fix would be to change the interface drivers by adding proper > support for reset-resume.  Otherwise there will always be a time window > following resume during which the interface is non-functional. Very hard to do with btusb. The connection is messed up if we lose power. Regards Oliver