Return-path: Received: from mail-wg0-f54.google.com ([74.125.82.54]:45746 "EHLO mail-wg0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753212Ab3CKK0J (ORCPT ); Mon, 11 Mar 2013 06:26:09 -0400 Received: by mail-wg0-f54.google.com with SMTP id fm10so4623882wgb.21 for ; Mon, 11 Mar 2013 03:26:07 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20130309100150.432.50619.stgit@localhost6.localdomain6> References: <20130309100031.432.94974.stgit@localhost6.localdomain6> <20130309100150.432.50619.stgit@localhost6.localdomain6> Date: Mon, 11 Mar 2013 11:26:07 +0100 Message-ID: (sfid-20130311_112613_761177_6F020D0A) Subject: Re: [PATCH v2 3/3] ath6kl: cold reset target after host warm boot From: Julien Massot To: Kalle Valo Cc: ath6kl-devel@qca.qualcomm.com, linux-wireless@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: Hi Kalle, > Julien reported that ar6004 usb device fails to initialise > after host has been rebooted and power is still on for the ar6004 device. He > found out that doing a cold reset fixes the issue. > > I wasn't sure what would be the best way to detect if target needs a reset so I > settled on checking a timeout from htc_wait_recv_ctrl_message(). > > Reported-by: Julien Massot > Signed-off-by: Kalle Valo > --- This patch fix the issue, now my adapter works after a soft reboot. The log are also better: (here is what happen on soft reboot) [ 17.328029] ath6kl: htc pipe control receive timeout! [ 17.328033] ath6kl: htc wait target timed out, resetting device [ 17.332178] ath6kl: Failed to start hardware: -110 [ 17.332208] ath6kl: Failed to init ath6kl core: -110 [ 17.332270] ath6kl_usb: probe of 2-1:1.0 failed with error -110 [ 17.332306] usbcore: registered new interface driver ath6kl_usb [ 19.040315] ath6kl: ar6004 hw 1.3 usb fw 3.5.0.2356\x01 api 3 Thanks! Tested-by: Julien Massot Julien