linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: "Wyse, Chris" <chris.wyse@windriver.com>
Cc: linuxppc-embedded@ozlabs.org, "McComb,
	Michael" <michael.mccomb@windriver.com>,
	"Touron, Emmanuel" <emmanuel.touron@windriver.com>
Subject: Re: Calling PCI Autoconfig again
Date: Tue, 7 Mar 2006 10:26:30 -0600	[thread overview]
Message-ID: <BAB64425-65CD-4311-9A93-004EBA27729A@kernel.crashing.org> (raw)
In-Reply-To: <927594BA71733F4BAA815162B79A3F513B2958@ala-mail04.corp.ad.wrs.com>


On Mar 7, 2006, at 8:17 AM, Wyse, Chris wrote:

> Hi,
>
> This code will do the rescan of the PCI that we need for the FPGA.
> However, it currently only supports a single execution after the FPGA
> gets loaded.  Additional calls will continue to add FPGA devices to  
> the
> PCI device list data structure.  I'm going to make some changes to  
> it to
> handle multiple calls and to support multiple device ids.  I'm  
> expecting
> it to take a day or two, but I'll make an initial cut at it today that
> will let us load the Spartan FPGA (only once).  This driver will be
> loaded when the kernel boots, so I believe that we'll just need to  
> make
> a call into it (we won't have to dynamically load it like the phob
> driver).

I'm dealing with this exact same situation and having a discussion on  
lkml regarding the proper way to do this.  In your case, do you care  
what addresses the FPGA is assigned at?

http://marc.theaimsgroup.com/?l=linux-kernel&m=114140791428032&w=2

> Michael,
>
> For the FPGA loader, you should load the FPGA, then make a call to
> pci_rescan_bus0() (I'm renaming check_hw() to pci_rescan_bus0()).   
> Next,
> you need to do a pci_find_device() to detect the newly loaded  
> FPGA.  If
> the pci_find_device() fails, assume that the FPGA load has not
> completed, so delay for some time frame (100 ms??), then rescan again.
> If still not found, rescan up to MAX_PCI_RESCANS (probably set it  
> to 3)
> times, then return an error that the FPGA load failed.

Do you not know when the FPGA load is done?  I assume its under  
software control so the "fpga loader" should just call the PCI setup  
code once it has completed successfully.

- kumar

  reply	other threads:[~2006-03-07 16:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-07 14:17 Calling PCI Autoconfig again Wyse, Chris
2006-03-07 16:26 ` Kumar Gala [this message]
2006-03-07 16:53   ` Mark Chambers
2006-03-07 16:59     ` Kumar Gala
2006-03-07 17:22       ` Mark Chambers
  -- strict thread matches above, loose matches on Subject: below --
2006-03-07 19:25 Wyse, Chris
2006-03-07 19:57 ` Kumar Gala
2006-03-07 13:49 Wyse, Chris
2006-03-06 21:34 Wyse, Chris
2006-03-07  4:32 ` David Hawkins
2006-03-07 15:48 ` Michael Richardson

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=BAB64425-65CD-4311-9A93-004EBA27729A@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=chris.wyse@windriver.com \
    --cc=emmanuel.touron@windriver.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=michael.mccomb@windriver.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 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).