Return-path: <linux-wireless-owner@vger.kernel.org>
Received: from wolverine02.qualcomm.com ([199.106.114.251]:50151 "EHLO
	wolverine02.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1755874Ab2ICDzS (ORCPT
	<rfc822;linux-wireless@vger.kernel.org>);
	Sun, 2 Sep 2012 23:55:18 -0400
Message-ID: <50442A13.8030204@qca.qualcomm.com> (sfid-20120903_055522_958113_B99CA52B)
Date: Mon, 3 Sep 2012 09:24:59 +0530
From: Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>
MIME-Version: 1.0
To: "Jin, Navy" <nhjin@qca.qualcomm.com>
CC: "Valo, Kalle" <kvalo@qca.qualcomm.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	ath6kl-devel <ath6kl-devel@qualcomm.com>
Subject: Re: [PATCH 2/4] ath6kl: Recover from fw crash
References: <1346249428-24741-1-git-send-email-vthiagar@qca.qualcomm.com>,<1346249428-24741-2-git-send-email-vthiagar@qca.qualcomm.com> <ow6cb3l1q88896mivhugkyea.1346427514782@email.android.com>
In-Reply-To: <ow6cb3l1q88896mivhugkyea.1346427514782@email.android.com>
Content-Type: text/plain; charset="GB2312"
Sender: linux-wireless-owner@vger.kernel.org
List-ID: <linux-wireless.vger.kernel.org>



On Friday 31 August 2012 09:15 PM, Jin, Navy wrote:
> Can this feature be disabled by some control bit or module parameters?Once enabled,it is better for user,but more hard to find the root cause,or log chip info before recovery?
> Regards??

Good point, i'll send a follow up patch. thanks!.

Vasanth