linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: wwguy <wey-yi.w.guy@intel.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Intel Linux Wireless <ilw@linux.intel.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [RFC 4/4] iwlwifi: use writeb,writel,readl directly
Date: Mon, 06 Feb 2012 08:32:52 -0800	[thread overview]
Message-ID: <1328545972.14547.15.camel@wwguy-ubuntu> (raw)
In-Reply-To: <1328544564-8696-4-git-send-email-sgruszka@redhat.com>

On Mon, 2012-02-06 at 17:09 +0100, Stanislaw Gruszka wrote:
> That will save us some CPU cycles at run time.
> 
> Obviously I do not think port-based IO is possible, but I added
> check for that during probe just in case.
> 
> Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
> ---
>  drivers/net/wireless/iwlwifi/iwl-pci.c |   12 ++++++++----
>  1 files changed, 8 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/net/wireless/iwlwifi/iwl-pci.c b/drivers/net/wireless/iwlwifi/iwl-pci.c
> index 03702a2..32b326d 100644
> --- a/drivers/net/wireless/iwlwifi/iwl-pci.c
> +++ b/drivers/net/wireless/iwlwifi/iwl-pci.c
> @@ -153,18 +153,17 @@ static u32 iwl_pci_get_hw_id(struct iwl_bus *bus)
>  
>  static void iwl_pci_write8(struct iwl_bus *bus, u32 ofs, u8 val)
>  {
> -	iowrite8(val, IWL_BUS_GET_PCI_BUS(bus)->hw_base + ofs);
> +	writeb(val, IWL_BUS_GET_PCI_BUS(bus)->hw_base + ofs);
>  }
>  
>  static void iwl_pci_write32(struct iwl_bus *bus, u32 ofs, u32 val)
>  {
> -	iowrite32(val, IWL_BUS_GET_PCI_BUS(bus)->hw_base + ofs);
> +	writel(val, IWL_BUS_GET_PCI_BUS(bus)->hw_base + ofs);
>  }
>  http://www.gossamer-threads.com/lists/linux/kernel/960145
>  static u32 iwl_pci_read32(struct iwl_bus *bus, u32 ofs)
>  {
> -	u32 val = ioread32(IWL_BUS_GET_PCI_BUS(bus)->hw_base + ofs);
> -	return val;
> +	return readl(IWL_BUS_GET_PCI_BUS(bus)->hw_base + ofs);
>  }
>  
>  static const struct iwl_bus_ops bus_ops_pci = {
> @@ -417,6 +416,11 @@ static int iwl_pci_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
>  		goto out_pci_disable_device;
>  	}
>  
> +	if (pci_resource_flags(pdev, 0) & IORESOURCE_IO) {
> +		dev_printk(KERN_ERR, bus->dev, "not supported I/O method");
> +		goto out_pci_disable_device;
> +	}
> +
>  	pci_bus->hw_base = pci_iomap(pdev, 0, 0);
>  	if (!pci_bus->hw_base) {
>  		dev_printk(KERN_ERR, bus->dev, "pci_iomap failed");

I believe iwl driver were use readl/writel before switch to
ioread32/iowrite32 (long time ago)

http://www.gossamer-threads.com/lists/linux/kernel/960145

also, AFAIK, the readl/writel IO functions still works but their use in
new code is discouraged.

Wey
 




  reply	other threads:[~2012-02-06 16:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06 16:09 [RFC 1/4] iwlwifi: dump stack when fail to gain access to the device Stanislaw Gruszka
2012-02-06 16:08 ` wwguy
2012-02-07  8:01   ` Stanislaw Gruszka
2012-02-07 14:21     ` Guy, Wey-Yi
2012-02-08 10:52       ` Stanislaw Gruszka
2012-02-06 16:09 ` [RFC 2/4] iwlwifi: always check if got h/w access before write Stanislaw Gruszka
2012-02-06 16:13   ` wwguy
2012-02-07  8:05     ` Stanislaw Gruszka
2012-02-07 14:20       ` Guy, Wey-Yi
2012-02-06 16:09 ` [RFC 3/4] iwlwifi: cleanup/fix memory barriers Stanislaw Gruszka
2012-02-06 16:13   ` Johannes Berg
2012-02-07  8:11     ` Stanislaw Gruszka
2012-02-07  8:25       ` Johannes Berg
2012-02-06 16:09 ` [RFC 4/4] iwlwifi: use writeb,writel,readl directly Stanislaw Gruszka
2012-02-06 16:32   ` wwguy [this message]
2012-02-07  8:22     ` Stanislaw Gruszka
2012-02-07 14:22       ` Guy, Wey-Yi
2012-02-10 12:01 ` [RFC 1/4] iwlwifi: dump stack when fail to gain access to the device Stanislaw Gruszka
2012-02-23 10:14   ` Stanislaw Gruszka

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=1328545972.14547.15.camel@wwguy-ubuntu \
    --to=wey-yi.w.guy@intel.com \
    --cc=ilw@linux.intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sgruszka@redhat.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).