linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Linux IDE mailing list <linux-ide@vger.kernel.org>
Subject: Re: PCI: Remove users of pci_enable_device_bars()
Date: Sat, 02 Feb 2008 01:27:32 -0500	[thread overview]
Message-ID: <47A40D54.70509@garzik.org> (raw)
In-Reply-To: <200802020506.m1256FVn024064@hera.kernel.org>

Linux Kernel Mailing List wrote:
> Commit:     0948391641918b95d8d96c15089eb5ac156850b3

>     PCI: Remove users of pci_enable_device_bars()
>     
>     This patch converts users of pci_enable_device_bars() to the new
>     pci_enable_device_{io,mem} interface.
>     
>     The new API fits nicely, except maybe for the QLA case where a bit of
>     code re-organization might be a good idea but I prefer sticking to the
>     simple patch as I don't have hardware to test on.
>     
>     I'll also need some feedback on the cs5520 change.
>     
>     Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
>     Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>

> --- a/drivers/ata/pata_cs5520.c
> +++ b/drivers/ata/pata_cs5520.c
> @@ -229,7 +229,7 @@ static int __devinit cs5520_init_one(struct pci_dev *pdev, const struct pci_devi
>  		return -ENOMEM;
>  
>  	/* Perform set up for DMA */
> -	if (pci_enable_device_bars(pdev, 1<<2)) {
> +	if (pci_enable_device_io(pdev)) {
>  		printk(KERN_ERR DRV_NAME ": unable to configure BAR2.\n");
>  		return -ENODEV;
>  	}
> diff --git a/drivers/ide/pci/cs5520.c b/drivers/ide/pci/cs5520.c
> index 6ec00b8..10adc49 100644
> --- a/drivers/ide/pci/cs5520.c
> +++ b/drivers/ide/pci/cs5520.c
> @@ -156,8 +156,14 @@ static int __devinit cs5520_init_one(struct pci_dev *dev, const struct pci_devic
>  	ide_setup_pci_noise(dev, d);
>  
>  	/* We must not grab the entire device, it has 'ISA' space in its
> -	   BARS too and we will freak out other bits of the kernel */
> -	if (pci_enable_device_bars(dev, 1<<2)) {
> +	 * BARS too and we will freak out other bits of the kernel
> +	 *
> +	 * pci_enable_device_bars() is going away. I replaced it with
> +	 * IO only enable for now but I'll need confirmation this is
> +	 * allright for that device. If not, it will need some kind of
> +	 * quirk. --BenH.
> +	 */
> +	if (pci_enable_device_io(dev)) {
>  		printk(KERN_WARNING "%s: Unable to enable 55x0.\n", d->name);
>  		return -ENODEV;
>  	}

So...  did the feedback mentioned in the commit log ever appear?  :)

	Jeff




       reply	other threads:[~2008-02-02  6:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200802020506.m1256FVn024064@hera.kernel.org>
2008-02-02  6:27 ` Jeff Garzik [this message]
2008-02-02 20:01   ` PCI: Remove users of pci_enable_device_bars() Bartlomiej Zolnierkiewicz
2008-02-02 20:05     ` Greg KH
2008-02-03  5:32       ` Benjamin Herrenschmidt

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=47A40D54.70509@garzik.org \
    --to=jeff@garzik.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=benh@kernel.crashing.org \
    --cc=gregkh@suse.de \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).