public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: proper way to assign fixed PCI resources to a "hotplug" device
Date: Fri, 3 Mar 2006 15:27:39 -0800	[thread overview]
Message-ID: <20060303232739.GA11796@kroah.com> (raw)
In-Reply-To: <A9483AAD-670C-4D03-9996-6AE89F6FD4FB@kernel.crashing.org>

On Fri, Mar 03, 2006 at 05:13:55PM -0600, Kumar Gala wrote:
> 
> On Mar 3, 2006, at 4:07 PM, Greg KH wrote:
> 
> >On Fri, Mar 03, 2006 at 11:42:03AM -0600, Kumar Gala wrote:
> >>I was wondering what the proper way to assign and setup a single PCI
> >>device that comes into existence after the system has booted.  I have
> >>an FPGA that we load from user space at which time it shows up on the
> >>PCI bus.
> >
> >Idealy your BIOS would set up this information :)
> >
> >>It has a single BAR and I need to assign it at a fixed address in PCI
> >>MMIO space.
> >>
> >>All of the exported interfaces I see have to do with having the
> >>kernel assign the BAR automatically for me.
> >>
> >>the following looks like what I want to do:
> >>
> >>bus = pci_find_bus(0, 3);
> >>dev = pci_scan_single_device(bus, devfn);
> >>pci_bus_alloc_resource(...);
> >>pci_update_resource(dev, dev->resource[0], 0);
> >>pci_bus_add_devices(bus);
> >>
> >>However, pci_update_resource() is not an exported symbol, so I could
> >>replace that code with the need updates to the actual BAR.
> >>
> >>Is this the "right" way to go about this or is there a better
> >>mechanism to do this.
> >
> >Take a look at how the compat pci hotplug driver does this, you  
> >probably
> >just need to do the same as it.
> 
> I found cpqhp_configure_device(), but I dont see anything about how  
> to handle assigned a fixed address to the BAR.

I don't know either, try asking on the pci hotplug mailing list and CC:
Scott, the author of that driver for how his devices work around that.

thanks,

greg k-h

  reply	other threads:[~2006-03-03 23:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-03 17:42 proper way to assign fixed PCI resources to a "hotplug" device Kumar Gala
2006-03-03 22:07 ` Greg KH
2006-03-03 22:39   ` Kumar Gala
2006-03-03 23:18     ` Greg KH
2006-03-03 23:28       ` Kumar Gala
2006-03-03 23:50         ` Scott Murray
2006-03-09 16:49       ` Kumar Gala
2006-03-03 23:18     ` Jeff Garzik
2006-03-08  2:00       ` Greg KH
2006-03-08  2:31         ` Tejun Heo
2006-03-08  5:27           ` Greg KH
2006-03-08 11:39             ` Ivan Kokshaysky
2006-03-08 16:40               ` thockin
2006-03-08 21:21                 ` Ivan Kokshaysky
2006-03-08 21:57                   ` thockin
2006-03-08 22:11                     ` Ivan Kokshaysky
2006-03-08 23:54                       ` thockin
2006-03-03 23:13   ` Kumar Gala
2006-03-03 23:27     ` Greg KH [this message]
2006-03-03 23:40       ` Scott Murray

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=20060303232739.GA11796@kroah.com \
    --to=greg@kroah.com \
    --cc=galak@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    /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