From: Jeff Garzik <jeff@garzik.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>,
Jiri Slaby <jirislaby@gmail.com>,
Nick Kossifidis <mickflemm@gmail.com>
Subject: Re: [PATCH] RFC: move ath5k to use pci_request_selected_regions()
Date: Thu, 01 Nov 2007 15:28:00 -0400 [thread overview]
Message-ID: <472A28C0.6060106@garzik.org> (raw)
In-Reply-To: <20071101192251.GB3201@pogo>
Luis R. Rodriguez wrote:
> Documentation/pci.txt states:
>
> "If your PCI device driver doesn't need I/O port resources assigned to
> I/O Port BARs, you should use pci_enable_device_bars() instead of
> pci_enable_device() in order not to enable I/O port regions for the
> corresponding devices. In addition, you should use
> pci_request_selected_regions() and pci_release_selected_regions()
> instead of pci_request_regions()/pci_release_regions() in order not to
> request/release I/O port regions for the corresponding devices."
>
> So shall we? This also re-arranges the pci_release_selected_regions()
> as per the documenation.
>
> Changes to base.c
> Changes-licensed-under: 3-clause-BSD
>
> Signed-off-by: Luis R. Rodriguez <mcgrof@gmail.com>
IMO the documentation is a bit bogus:
pci_request_regions() ensures that nobody else will touch -any- of your
resources.
I see no logical reason to enable sharing of I/O regions with another
driver, which would be the net effect of avoiding their request/release
by using pci_request_selected_regions()
pci_enable_device() and pci_request_regions() are just fine; the strange
and lesser-used APIs should be avoided unless you _need_ to use them.
Jeff
next prev parent reply other threads:[~2007-11-01 19:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 19:22 [PATCH] RFC: move ath5k to use pci_request_selected_regions() Luis R. Rodriguez
2007-11-01 19:28 ` Jeff Garzik [this message]
2007-11-01 22:38 ` Luis R. Rodriguez
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=472A28C0.6060106@garzik.org \
--to=jeff@garzik.org \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=mickflemm@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.