Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761714AbXKUPLA (ORCPT ); Wed, 21 Nov 2007 10:11:00 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755855AbXKUPKx (ORCPT ); Wed, 21 Nov 2007 10:10:53 -0500 Received: from smtp-out001.kontent.com ([81.88.40.215]:46013 "EHLO smtp-out001.kontent.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755586AbXKUPKw (ORCPT ); Wed, 21 Nov 2007 10:10:52 -0500 From: Oliver Neukum To: Felipe Balbi Subject: Re: USB deadlock after resume Date: Wed, 21 Nov 2007 16:10:58 +0100 User-Agent: KMail/1.9.6 (enterprise 20070904.708012) Cc: Markus Rechberger , Mark Lord , linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net, Laurent Pinchart References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200711211610.58684.oliver@neukum.org> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1130 Lines: 24 Am Mittwoch 21 November 2007 schrieb Felipe Balbi: > > Do you know any good way for performing a softreset within the driver? > > The video application should get a continuous datastream after > > resuming the notebook, so the driver shouldn't be unloaded. > > The driver also keeps a list of previous camera settings which should > > be set up again after resuming. Stopping the video application and > > reattaching the device using ACPI (this board supports reconnecting > > the device using ACPI) should be avoided. > > When you suspend, you cut off vbus (afaik, correct me if I'm wrong), which > means your device will get disconnected. One way to avoid this is enabling > CONFIG_USB_PERSIST and trying with that on. Suspend may or may not cut off power. If it does cut off power, resume() will never be called, instead either disconnect() or reset_resume(). Regards Oliver - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/