From: Ivo van Doorn <ivdoorn@gmail.com>
To: chris2553@googlemail.com
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
linux-wireless@vger.kernel.org
Subject: Re: [Bug #13846] Possible regression in rt61pci driver
Date: Mon, 3 Aug 2009 22:17:19 +0200 [thread overview]
Message-ID: <200908032217.19947.IvDoorn@gmail.com> (raw)
In-Reply-To: <200908031931.27427.chris2553@googlemail.com>
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
---
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.
next prev parent reply other threads:[~2009-08-03 20:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 18:49 2.6.31-rc5: Reported regressions from 2.6.30 Rafael J. Wysocki
2009-08-02 22:22 ` Linus Torvalds
2009-08-03 14:31 ` Johannes Weiner
2009-08-03 16:09 ` Rafael J. Wysocki
2009-08-03 15:36 ` Rafael J. Wysocki
[not found] ` <iZB3Pj-uj3M.A.pRC.1cgdKB@chimera>
2009-08-03 18:31 ` [Bug #13846] Possible regression in rt61pci driver Chris Clayton
2009-08-03 19:17 ` Rafael J. Wysocki
2009-08-03 20:17 ` Ivo van Doorn [this message]
2009-08-04 16:04 ` Chris Clayton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200908032217.19947.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=chris2553@googlemail.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rjw@sisk.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).