From: Ivo van Doorn <ivdoorn@gmail.com>
To: Josef Bacik <josef@redhat.com>
Cc: linux-wireless@vger.kernel.org, users@host1.serialmonkey.com,
John Linville <linville@tuxdriver.com>
Subject: Re: [PATCH] rt2800: do not enable tbtt unless we are in a beacon mode
Date: Mon, 16 Nov 2009 18:44:24 +0100 [thread overview]
Message-ID: <200911161844.25162.IvDoorn@gmail.com> (raw)
In-Reply-To: <20091116023317.GA6331@localhost.localdomain>
[ Added john to CC list ]
On Monday 16 November 2009, Josef Bacik wrote:
> Please be gentle, I'm a fs developer and this is my first foray into drivers, as
> I'm tired of building ralinks driver everytime I update my kernel. Whenever I
> load the rt2800pci driver my box bogs down, and a few printk's later I
> discovered its because I was getting 10's of thousands of TBTT interrupts a
> second. I discovered this was because we were setting the beacon timer to 0,
> which is apparently what TBTT keys off of. It seems to me that we should only
> be enabling TBTT when we are in a beacon transmitting mode, which from what I
> can tell is in AD-HOC and other such modes where the mac80211 layer would have
> given us a proper beacon_int to set the beacon timer to instead of 0. So this
> is my fix, only enable TBTT if our sync mode is for beacon. This makes it so my
> box doesn't die everytime I load the rt2800pci driver. Let me know if this is
> acceptable, I just learned all these terms about 15 minutes ago via wikipedia,
> so I really am not familiar with how this stuff is supposed to work. Thanks,
>
> Signed-off-by: Josef Bacik <josef@redhat.com>
Good catch.
Acked-by: Ivo van Doorn <IvDoorn@gmail.com>
> ---
> drivers/net/wireless/rt2x00/rt2800lib.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/net/wireless/rt2x00/rt2800lib.c b/drivers/net/wireless/rt2x00/rt2800lib.c
> index eb6d129..e90d6fd 100644
> --- a/drivers/net/wireless/rt2x00/rt2800lib.c
> +++ b/drivers/net/wireless/rt2x00/rt2800lib.c
> @@ -560,7 +560,8 @@ void rt2800_config_intf(struct rt2x00_dev *rt2x00dev, struct rt2x00_intf *intf,
> rt2800_register_read(rt2x00dev, BCN_TIME_CFG, ®);
> rt2x00_set_field32(®, BCN_TIME_CFG_TSF_TICKING, 1);
> rt2x00_set_field32(®, BCN_TIME_CFG_TSF_SYNC, conf->sync);
> - rt2x00_set_field32(®, BCN_TIME_CFG_TBTT_ENABLE, 1);
> + rt2x00_set_field32(®, BCN_TIME_CFG_TBTT_ENABLE,
> + (conf->sync == TSF_SYNC_BEACON));
> rt2800_register_write(rt2x00dev, BCN_TIME_CFG, reg);
> }
>
next prev parent reply other threads:[~2009-11-16 17:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 2:33 [PATCH] rt2800: do not enable tbtt unless we are in a beacon mode Josef Bacik
2009-11-16 14:21 ` Josef Bacik
2009-11-16 16:36 ` Luis R. Rodriguez
2009-11-16 17:44 ` Ivo van Doorn [this message]
2009-11-17 7:41 ` Holger Schurig
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=200911161844.25162.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=josef@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=users@host1.serialmonkey.com \
/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).