All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Hawkins <dwh@ovro.caltech.edu>
To: "Wyse, Chris" <chris.wyse@windriver.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Calling PCI Autoconfig again
Date: Mon, 06 Mar 2006 20:32:39 -0800	[thread overview]
Message-ID: <440D0CE7.9030702@ovro.caltech.edu> (raw)
In-Reply-To: <927594BA71733F4BAA815162B79A3F513B27FD@ala-mail04.corp.ad.wrs.com>

Wyse, Chris wrote:
> Hi,
>  
> I'm working on a board (PPC440GX CPU) that has an FPGA on it.  The FPGA 
> software has a PCI interface.  If I load the FPGA, then boot the Linux 
> kernel, the FPGA is recognized as a device on the PCI bus.  However, I'd 
> like to load the FPGA after the kernel has booted, then run autoconfig 
> again to detect the device.  What's the best way to do this? 
>  
> Please send responses directly to me (in addition to the list), since I 
> am not subscribed to the list.

Hi Chris,

I haven't had to do this, but I've thought about how I might do it.

In compact PCI, you can hot-swap a PCI device, and the Linux host
is supposed to go and re-enumerate the PCI bus. There is a
pci (host-side) hotplug skeleton in the source;

linux-2.6/drivers/pci/hotplug/pcihp_skeleton.c

I believe you can do the following;

   - consider the 440GX is a hotplug controller
     (and write a hotplug driver appropriately)
   - when Linux loads the FPGA, the FPGA generates a hotplug
     event, i.e., it just got plugged in
     (I'm not sure what signal is generated, perhaps a
      power-management interrupt PME#?)
   - the 440GX hotplug controller re-enumerates the PCI bus
     and finds the device

I'm sure you can get an idea from the hotplug skeleton what
re-enumeration entails.

Cheers
Dave

  reply	other threads:[~2006-03-07  4:33 UTC|newest]

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

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=440D0CE7.9030702@ovro.caltech.edu \
    --to=dwh@ovro.caltech.edu \
    --cc=chris.wyse@windriver.com \
    --cc=linuxppc-embedded@ozlabs.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 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.