linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arik Nemtsov <arik@wizery.com>
To: <linux-wireless@vger.kernel.org>
Cc: Luciano Coelho <coelho@ti.com>, Igal Chernobelsky <igalc@ti.com>,
	Arik Nemtsov <arik@wizery.com>
Subject: [PATCH 07/10] wlcore: modify bss loss parameters
Date: Tue, 15 May 2012 17:08:57 +0300	[thread overview]
Message-ID: <1337090940-13750-7-git-send-email-arik@wizery.com> (raw)
In-Reply-To: <1337090940-13750-1-git-send-email-arik@wizery.com>

From: Igal Chernobelsky <igalc@ti.com>

Modify default parameters to reduce firmware BSS lose
probability in congested environment.

[Applied to 18xx configuration as well - Arik]

Signed-off-by: Igal Chernobelsky <igalc@ti.com>
Signed-off-by: Arik Nemtsov <arik@wizery.com>
---
 drivers/net/wireless/ti/wl12xx/main.c |    4 ++--
 drivers/net/wireless/ti/wl18xx/main.c |    4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/net/wireless/ti/wl12xx/main.c b/drivers/net/wireless/ti/wl12xx/main.c
index 7e65ee3..08bec7f 100644
--- a/drivers/net/wireless/ti/wl12xx/main.c
+++ b/drivers/net/wireless/ti/wl12xx/main.c
@@ -227,8 +227,8 @@ static struct wlcore_conf wl12xx_conf = {
 				.rule        = CONF_BCN_RULE_PASS_ON_CHANGE,
 			},
 		},
-		.synch_fail_thold            = 10,
-		.bss_lose_timeout            = 100,
+		.synch_fail_thold            = 12,
+		.bss_lose_timeout            = 400,
 		.beacon_rx_timeout           = 10000,
 		.broadcast_timeout           = 20000,
 		.rx_broadcast_in_ps          = 1,
diff --git a/drivers/net/wireless/ti/wl18xx/main.c b/drivers/net/wireless/ti/wl18xx/main.c
index c5ec94b..10a0ba1 100644
--- a/drivers/net/wireless/ti/wl18xx/main.c
+++ b/drivers/net/wireless/ti/wl18xx/main.c
@@ -350,8 +350,8 @@ static struct wlcore_conf wl18xx_conf = {
 				.rule        = CONF_BCN_RULE_PASS_ON_CHANGE,
 			},
 		},
-		.synch_fail_thold            = 10,
-		.bss_lose_timeout            = 100,
+		.synch_fail_thold            = 12,
+		.bss_lose_timeout            = 400,
 		.beacon_rx_timeout           = 10000,
 		.broadcast_timeout           = 20000,
 		.rx_broadcast_in_ps          = 1,
-- 
1.7.9.5


  parent reply	other threads:[~2012-05-15 14:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 14:08 [PATCH 01/10] wlcore: fix sparse warnings related to static functions Arik Nemtsov
2012-05-15 14:08 ` [PATCH 02/10] wlcore: use the original elp time in forced_ps mode Arik Nemtsov
2012-05-15 14:08 ` [PATCH 03/10] wlcore: fix dynamic_ps_timeout time regression Arik Nemtsov
2012-05-15 14:08 ` [PATCH 04/10] wlcore: fixes for connection_loss_work Arik Nemtsov
2012-05-15 14:08 ` [PATCH 05/10] wlcore: use correct link for bcast/multicast frames Arik Nemtsov
2012-05-15 14:08 ` [PATCH 06/10] wlcore: flush before stopping AP Arik Nemtsov
2012-05-15 14:08 ` Arik Nemtsov [this message]
2012-05-15 14:08 ` [PATCH 08/10] wlcore: increase number of BA sessions to 3 Arik Nemtsov
2012-05-15 14:08 ` [PATCH 09/10] wl18xx: add dependency on mac80211 Arik Nemtsov
2012-05-15 14:09 ` [PATCH 10/10] wlcore: set wl->ht_cap per-band Arik Nemtsov
2012-06-05 14:30 ` [PATCH 01/10] wlcore: fix sparse warnings related to static functions Luciano Coelho

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=1337090940-13750-7-git-send-email-arik@wizery.com \
    --to=arik@wizery.com \
    --cc=coelho@ti.com \
    --cc=igalc@ti.com \
    --cc=linux-wireless@vger.kernel.org \
    /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).