Return-path: Received: from mail-ob0-f174.google.com ([209.85.214.174]:56691 "EHLO mail-ob0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751741Ab2IJKX2 (ORCPT ); Mon, 10 Sep 2012 06:23:28 -0400 MIME-Version: 1.0 In-Reply-To: References: <1345536267-9449-1-git-send-email-ming.lei@canonical.com> Date: Mon, 10 Sep 2012 15:53:27 +0530 Message-ID: (sfid-20120910_122337_922114_F1A1504D) Subject: Re: [PATCH -next v1] wireless: ath9k-htc: only load firmware in need From: Mohammed Shafi To: Ming Lei Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org, ath9k-devel@lists.ath9k.org, "Luis R. Rodriguez" , Jouni Malinen , Vasanthakumar Thiagarajan , Senthil Balasubramanian , "John W. Linville" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: Hi, On Sat, Sep 1, 2012 at 10:41 AM, Ming Lei wrote: > On Tue, Aug 21, 2012 at 4:04 PM, Ming Lei wrote: >> It is not necessary to hold the firmware memory during the whole >> driver lifetime, and obviously it does waste memory. Suppose there >> are 4 ath9k-htc usb dongles working, kernel has to consume about >> 4*50KBytes RAM to cache firmware for all dongles. After applying the >> patch, kernel only caches one single firmware image in RAM for >> all ath9k-htc devices just during system suspend/resume cycle. >> >> When system is ready for loading firmware, ath9k-htc can request >> the loading from usersapce. During system resume, ath9k-htc still >> can load the firmware which was cached in kernel memory before >> system suspend. >> >> Cc: ath9k-devel@lists.ath9k.org >> Cc: "Luis R. Rodriguez" >> Cc: Jouni Malinen >> Cc: Vasanthakumar Thiagarajan >> Cc: Senthil Balasubramanian >> Cc: "John W. Linville" >> Signed-off-by: Ming Lei >> --- >> v1: >> fix double free of firmware in failue path of >> ath9k_hif_usb_firmware_cb > > Gentle ping, :-) this patch is now in wireless-testing :-) > > > Thanks, > -- > Ming Lei > -- > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- thanks, shafi