From patchwork Mon Aug 3 20:17:19 2009 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Ivo van Doorn X-Patchwork-Id: 38993 Received: from vger.kernel.org (vger.kernel.org [209.132.176.167]) by demeter.kernel.org (8.14.2/8.14.2) with ESMTP id n73KIEC4029009 for ; Mon, 3 Aug 2009 20:18:14 GMT Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751896AbZHCURZ (ORCPT ); Mon, 3 Aug 2009 16:17:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751664AbZHCURZ (ORCPT ); Mon, 3 Aug 2009 16:17:25 -0400 Received: from ey-out-2122.google.com ([74.125.78.24]:13811 "EHLO ey-out-2122.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751355AbZHCURX (ORCPT ); Mon, 3 Aug 2009 16:17:23 -0400 Received: by ey-out-2122.google.com with SMTP id 9so1011505eyd.37 for ; Mon, 03 Aug 2009 13:17:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:cc:references:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:message-id; bh=h1u2E4HK8WxAR1ulLKfaQrxeWROog8KoEFOilQYllaQ=; b=nyYAMYzBsyK4x8AJyJx/Ihg/EtFvsplNszdIXWkpzhuUbr7wKh39xFBOqZqCjKtdmu BtzUGCju4AlHfH0HHCOjO5TRZItuiAIELBV8HPl1iQoHzIO9UUniGjnBNH/ILQj3Nozs 14Wd9vuvDHFjUeN/XwJxY24Hy2BS1F/+fXSuE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:message-id; b=LIVU9ux+gTlsa6nH8YhHMWCqTsAVIy0BYE8nrIN00qaR4DBXy/wKtzx2qCBLB3f0mr XSW27DhcVAVf3UmivrqrogRqs/AAd1NFhfM+qL9fSZ8Wo89V8lUVomexRu9vv6mscKvh wi6/ytBscinWiZWUqgSLfRmiNMU34quBn4nd8= Received: by 10.210.92.8 with SMTP id p8mr7927689ebb.15.1249330642307; Mon, 03 Aug 2009 13:17:22 -0700 (PDT) Received: from ?192.168.8.40? (k19232.upc-k.chello.nl [62.108.19.232]) by mx.google.com with ESMTPS id 7sm1858890eyb.27.2009.08.03.13.17.21 (version=SSLv3 cipher=RC4-MD5); Mon, 03 Aug 2009 13:17:21 -0700 (PDT) From: Ivo van Doorn To: chris2553@googlemail.com Subject: Re: [Bug #13846] Possible regression in rt61pci driver Date: Mon, 3 Aug 2009 22:17:19 +0200 User-Agent: KMail/1.9.10 Cc: "Rafael J. Wysocki" , Linux Kernel Mailing List , Kernel Testers List , linux-wireless@vger.kernel.org References: <200908031931.27427.chris2553@googlemail.com> In-Reply-To: <200908031931.27427.chris2553@googlemail.com> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200908032217.19947.IvDoorn@gmail.com> Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org Hi, > On Sunday 02 August 2009, Rafael J. Wysocki wrote: > > This message has been generated automatically as a part of a report > > of recent regressions. > > > > The following bug entry is on the current list of known regressions > > from 2.6.30. Please verify if it still should be listed and let me know > > (either way). > > > > The folks on the wireless project have concluded that the problem I reported is down to a hardware > problem when power saving is switched on on for my Belkin cardbus wireless adapter, so now I simply > turn power-saving off when wlan0 comes up. I did, however, ask whether anyone was going to fix the > fact that once power-saving turns the LEDs off, they never come back on again, but I haven't had an > answer. Is that a regression? I guess the answer is no, because power saving in the rt61pci driver > is feature that is new to 2.6.31. Should it be fixed? I think the answer is yes, but being unable > to do it myself, I probably don't have a vote :-) Can't recall this issue was ever reported, but that might just be me having overlooked some emails or have completely forgotten all about it. But here is a test patch to see if this helps in the issue, it is not really correct for upstream, but if it works I can see if there is a better solution. Thanks, Ivo --- -- 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 diff --git a/drivers/net/wireless/rt2x00/rt2x00config.c b/drivers/net/wireless/rt2x00/rt2x00config.c index 3845316..6fe70b1 100644 --- a/drivers/net/wireless/rt2x00/rt2x00config.c +++ b/drivers/net/wireless/rt2x00/rt2x00config.c @@ -196,6 +196,12 @@ void rt2x00lib_config(struct rt2x00_dev *rt2x00dev, */ rt2x00dev->ops->lib->config(rt2x00dev, &libconf, ieee80211_flags); + if (ieee80211_flags & IEEE80211_CONF_CHANGE_PS) { + rt2x00led_led_activity(rt2x00dev, !(conf->flags & IEEE80211_CONF_PS)); + rt2x00leds_led_assoc(rt2x00dev, !(conf->flags & IEEE80211_CONF_PS)); + rt2x00leds_led_radio(rt2x00dev, !(conf->flags & IEEE80211_CONF_PS)); + } + /* * Some configuration changes affect the link quality * which means we need to reset the link tuner.