netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Olof Johansson <olof@lixom.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 3/9] pasemi_mac: Abstract out register access
Date: Mon, 02 Jul 2007 08:32:24 -0400	[thread overview]
Message-ID: <4688F058.7040805@pobox.com> (raw)
In-Reply-To: <20070622200511.GD11723@lixom.net>

Olof Johansson wrote:
> Abstract out the PCI config read/write accesses into reg read/write ones, still
> calling the pci accessors on the back end.
> 
> Signed-off-by: Olof Johansson <olof@lixom.net>
> 
> 
> Index: netdev-2.6/drivers/net/pasemi_mac.c
> ===================================================================
> --- netdev-2.6.orig/drivers/net/pasemi_mac.c
> +++ netdev-2.6/drivers/net/pasemi_mac.c
> @@ -81,6 +81,48 @@ MODULE_PARM_DESC(debug, "PA Semi MAC bit
>  
>  static struct pasdma_status *dma_status;
>  
> +static unsigned int read_iob_reg(struct pasemi_mac *mac, unsigned int reg)
> +{
> +	unsigned int val;
> +
> +	pci_read_config_dword(mac->iob_pdev, reg, &val);
> +	return val;
> +}
> +
> +static void write_iob_reg(struct pasemi_mac *mac, unsigned int reg,
> +			  unsigned int val)
> +{
> +	pci_write_config_dword(mac->iob_pdev, reg, val);
> +}
> +
> +static unsigned int read_mac_reg(struct pasemi_mac *mac, unsigned int reg)
> +{
> +	unsigned int val;
> +
> +	pci_read_config_dword(mac->pdev, reg, &val);
> +	return val;
> +}
> +
> +static void write_mac_reg(struct pasemi_mac *mac, unsigned int reg,
> +			  unsigned int val)
> +{
> +	pci_write_config_dword(mac->pdev, reg, val);
> +}
> +
> +static unsigned int read_dma_reg(struct pasemi_mac *mac, unsigned int reg)
> +{
> +	unsigned int val;
> +
> +	pci_read_config_dword(mac->dma_pdev, reg, &val);
> +	return val;
> +}
> +
> +static void write_dma_reg(struct pasemi_mac *mac, unsigned int reg,
> +			  unsigned int val)
> +{
> +	pci_write_config_dword(mac->dma_pdev, reg, val);
> +}

The general concept is fine, but you should use 'u32' and similar 
size-based types for your input and output values.



  reply	other threads:[~2007-07-02 12:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070622194720.614405000@lixom.net>
2007-06-22 20:04 ` [PATCH 1/9] pasemi_mac: Fix TX interrupt threshold Olof Johansson
2007-07-02 12:37   ` Jeff Garzik
2007-06-22 20:05 ` [PATCH 2/9] pasemi_mac: Clean TX ring in poll Olof Johansson
2007-07-02 12:34   ` Jeff Garzik
2007-07-03 20:31     ` Olof Johansson
2007-06-22 20:05 ` [PATCH 3/9] pasemi_mac: Abstract out register access Olof Johansson
2007-07-02 12:32   ` Jeff Garzik [this message]
2007-06-22 20:05 ` [PATCH 4/9] pasemi_mac: Use MMIO instead of pci config accessors Olof Johansson
2007-07-02 12:37   ` Jeff Garzik
2007-06-22 20:05 ` [PATCH 5/9] pasemi_mac: Enable L2 caching of packet headers Olof Johansson
2007-06-22 20:05 ` [PATCH 6/9] pasemi_mac: Simplify memcpy for short receives Olof Johansson
2007-06-22 20:05 ` [PATCH 7/9] pasemi_mac: Minor performance tweaks Olof Johansson
2007-06-22 20:05 ` [PATCH 8/9] pasemi_mac: Reduce locking when cleaning TX ring Olof Johansson
2007-06-22 20:05 ` [PATCH 9/9] pasemi_mac: Enable LLTX Olof Johansson

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=4688F058.7040805@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=netdev@vger.kernel.org \
    --cc=olof@lixom.net \
    /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).