linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wey-Yi Guy <wey-yi.w.guy@intel.com>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org,
	ipw3945-devel@lists.sourceforge.net, "Winkler,
	Tomas" <tomas.winkler@intel.com>,
	Wey-Yi Guy <wey-yi.w.guy@intel.com>
Subject: [PATCH 08/16] iwlwlifi: update rx write pointer w/o request mac access in the CAM mode
Date: Wed, 10 Nov 2010 09:56:42 -0800	[thread overview]
Message-ID: <1289411810-23093-9-git-send-email-wey-yi.w.guy@intel.com> (raw)
In-Reply-To: <1289411810-23093-1-git-send-email-wey-yi.w.guy@intel.com>

From: Winkler, Tomas <tomas.winkler@intel.com>

In iwl_rx_queue_update_write_ptr function
replace iwl_write_direct32 with iwl_write32 when not in power save mode.
We don't have to go through grab nic access as the NIC is already awake.

Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
Signed-off-by: Wey-Yi Guy <wey-yi.w.guy@intel.com>
---
 drivers/net/wireless/iwlwifi/iwl-rx.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/net/wireless/iwlwifi/iwl-rx.c b/drivers/net/wireless/iwlwifi/iwl-rx.c
index f436270..baca4cc 100644
--- a/drivers/net/wireless/iwlwifi/iwl-rx.c
+++ b/drivers/net/wireless/iwlwifi/iwl-rx.c
@@ -153,7 +153,7 @@ void iwl_rx_queue_update_write_ptr(struct iwl_priv *priv, struct iwl_rx_queue *q
 	} else {
 		/* Device expects a multiple of 8 */
 		q->write_actual = (q->write & ~0x7);
-		iwl_write_direct32(priv, rx_wrt_ptr_reg, q->write_actual);
+		iwl_write32(priv, rx_wrt_ptr_reg, q->write_actual);
 	}
 
 	q->need_update = 0;
-- 
1.7.0.4


  parent reply	other threads:[~2010-11-10 18:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-10 17:56 [PATCH 00/16] update for 2.6.37 Wey-Yi Guy
2010-11-10 17:56 ` [PATCH 01/16] iwlagn: update PCI ID for 6000g2b series devices Wey-Yi Guy
2010-11-10 17:56 ` [PATCH 02/16] iwlagn: update PCI ID for 6000g2a " Wey-Yi Guy
2010-11-10 17:56 ` [PATCH 03/16] iwlagn: update PCI ID for 100 " Wey-Yi Guy
2010-11-10 17:56 ` [PATCH 04/16] iwlagn: fix non-5000+ build Wey-Yi Guy
2010-11-10 17:56 ` [PATCH 05/16] iwlwifi: Legacy isr only used by legacy devices Wey-Yi Guy
2010-11-10 17:56 ` [PATCH 06/16] iwlwifi: put all the isr related function under ops Wey-Yi Guy
2010-11-10 17:56 ` [PATCH 07/16] iwlwifi: legacy tx_cmd_protection function Wey-Yi Guy
2010-11-10 17:56 ` Wey-Yi Guy [this message]
2010-11-10 17:56 ` [PATCH 09/16] iwlwifi: resending QoS command when HT changes Wey-Yi Guy
2010-11-10 17:56 ` [PATCH 10/16] iwlagn: fix needed chains calculation Wey-Yi Guy
2010-11-10 17:56 ` [PATCH 11/16] iwlagn: fix RXON issues Wey-Yi Guy
2010-11-10 17:56 ` [PATCH 12/16] iwlagn: re-enable calibration Wey-Yi Guy
2010-11-10 17:56 ` [PATCH 13/16] iwlagn: fix RXON HT Wey-Yi Guy
2010-11-10 17:56 ` [PATCH 14/16] iwlwifi: seperate disconnected antenna function Wey-Yi Guy
2010-11-10 17:56 ` [PATCH 15/16] iwlwifi: disable disconnected antenna for advanced bt coex Wey-Yi Guy
2010-11-10 17:56 ` [PATCH 16/16] iwlagn: enabel shadow register Wey-Yi Guy
2010-11-10 18:16 ` [PATCH 00/16] update for 2.6.37 John W. Linville
2010-11-10 18:47   ` Guy, Wey-Yi

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=1289411810-23093-9-git-send-email-wey-yi.w.guy@intel.com \
    --to=wey-yi.w.guy@intel.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=tomas.winkler@intel.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).