All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: "Christian P. Schmidt" <schmidt@digadd.de>
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: How can PCI resource allocation fail?
Date: Thu, 12 Mar 2009 20:36:30 -0600	[thread overview]
Message-ID: <49B9C6AE.5050308@gmail.com> (raw)
In-Reply-To: <49B9959F.1080705@digadd.de>

Christian P. Schmidt wrote:
> Hi all,
> 
> I'm toying with the alsa-driver for the Creative Labs X-Fi. I'm working on the PCI Express version of this card, though, which is
> the same as the PCI version plus a PCIe to PCI bridge but has a different ID:
> 
>           +-1c.2-[0000:03-04]----00.0-[0000:04]----00.0  1102:0009
> 
> 03:00.0 PCI bridge: Creative Labs Device 7006
> 04:00.0 Audio device: Creative Labs [SB X-Fi Xtreme Audio] CA0110-IBG
> 
> Now, after adding the ID, the driver fails:
> 
> [46833.487579] CA0106 0000:04:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
> [46833.487586] CA0106 0000:04:00.0: PCI INT A disabled
> [46833.487588] cannot allocate the port
> [46833.487594] CA0106: probe of 0000:04:00.0 failed with error -16
> 
> The actual error is occurring in
> 
> 	chip->port = pci_resource_start(pci, 0);
> 	chip->res_port = request_region(chip->port, pci_resource_len(pci,0), "snd_ca0106");
> 	if (!chip->res_port) {
> 		snd_ca0106_free(chip);
> 		printk(KERN_ERR "cannot allocate the port\n");
> 		return -EBUSY;
> 	}
> 
> This from /proc/iomem:
> 
> f9f00000-f9ffffff : PCI Bus 0000:03
>   f9f00000-f9ffffff : PCI Bus 0000:04
>     f9ffc000-f9ffffff : 0000:04:00.0
> 
> Some additional debug output tells me that the code is actually trying to allocate 16k starting from f9ffc000. What could be
> potential reasons for the failure? Do I have to do something with the bridge before I can try to request the region?

request_region is requesting IO ports. The PCI BAR on the card is MMIO 
memory, not IO ports, so request_mem_region has to be used. It's 
possible that this driver isn't set up to handle MMIO space.

  reply	other threads:[~2009-03-13  2:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-12 23:07 How can PCI resource allocation fail? Christian P. Schmidt
2009-03-13  2:36 ` Robert Hancock [this message]
2009-03-13  7:44 ` Clemens Ladisch
2009-03-13  7:44   ` [alsa-devel] " Clemens Ladisch
2009-03-13  8:24   ` Takashi Iwai
2009-03-13  8:24     ` [alsa-devel] " Takashi Iwai
2009-03-13 10:24     ` Vedran Miletić
2009-03-13 10:24       ` [alsa-devel] " Vedran Miletić

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=49B9C6AE.5050308@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schmidt@digadd.de \
    /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.