linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix <ic.felix@gmail.com>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com
Subject: Re: [PATCH 2/3] carl9170: reduce channel change delay
Date: Tue, 28 Dec 2010 16:39:38 -0800	[thread overview]
Message-ID: <1293583178.4197.21.camel@darkslate> (raw)
In-Reply-To: <E1PWwiD-0003TF-Qt@debian64.daheim>

Hi Christian,

in 2006 people didn't worry about bg-scan yet, so this stuff didn't get
optimized. Make it look like ath9k for ar9001. Btw I deeply appreciate
your work.

Best regards, Felix

On Sun, 2010-12-26 at 18:22 +0100, Christian Lamparter wrote:
> By removing two "safety" msleeps (and an echo nop), the
> channel change delay is effectively halved. Previously,
> the delay could be as long as 260 ms and the device
> could not go off-channel without risking to miss the
> next DTIM beacon [interval ~307 ms].
> 
> Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
> ---
> Hi Felix,
> 
> It seems that removing the msleeps doesn't have ANY negative effect
> on the operation. Furthermore ath9k doesn't need the 20ms+ msleeps
> in the phy codepaths either. So, I wonder if this is just some old
> "safety" buffers which survived otus and ar9170usb development
> phases, or is there some merit to them?
> 
> Regards,
> 	Chr
> ---
>  drivers/net/wireless/ath/carl9170/phy.c |    8 --------
>  1 files changed, 0 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/net/wireless/ath/carl9170/phy.c b/drivers/net/wireless/ath/carl9170/phy.c
> index 122e75e..b6b0de6 100644
> --- a/drivers/net/wireless/ath/carl9170/phy.c
> +++ b/drivers/net/wireless/ath/carl9170/phy.c
> @@ -1029,8 +1029,6 @@ static int carl9170_init_rf_bank4_pwr(struct ar9170 *ar, bool band5ghz,
>  	if (err)
>  		return err;
>  
> -	msleep(20);
> -
>  	return 0;
>  }
>  
> @@ -1660,12 +1658,6 @@ int carl9170_set_channel(struct ar9170 *ar, struct ieee80211_channel *channel,
>  			return err;
>  
>  		cmd = CARL9170_CMD_RF_INIT;
> -
> -		msleep(100);
> -
> -		err = carl9170_echo_test(ar, 0xaabbccdd);
> -		if (err)
> -			return err;
>  	} else {
>  		cmd = CARL9170_CMD_FREQUENCY;
>  	}



      reply	other threads:[~2010-12-29  0:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-26 17:22 [PATCH 2/3] carl9170: reduce channel change delay Christian Lamparter
2010-12-29  0:39 ` Felix [this message]

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=1293583178.4197.21.camel@darkslate \
    --to=ic.felix@gmail.com \
    --cc=chunkeey@googlemail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).