From: Jean-Francois Dagenais <jeff.dagenais@gmail.com>
To: linux-newbie@vger.kernel.org
Subject: PCI express late appearance on bus
Date: Fri, 11 Mar 2011 11:52:55 -0500 [thread overview]
Message-ID: <1299862375.8754.5.camel@jfddesk> (raw)
Hi all,
Under the most recent linux kernel, we are using intel chipset COM
modules (kontron and other OEMs probably) as the computer part of our
products. An FPGA device is connected to 4 lanes of PCI express. Right
now the FPGA gets programmed by a flash PROM at power up, so the BIOS
enumerates it initially.
Since we don't need the device at boot time, I want to get rid of the
PROM and program the FPGA using SPI from the CPU later during the boot
process, i.e. after user-space init, perhaps when I modprobe my driver
module, in module_init... This would mean that at BIOS PCI enumeration,
the device would be dead on the bus.
I was thinking of the hotplug feature of PCI express to get the PCI
subsystem to suddenly declare the presence of the device. Or perhaps
after I program the FPGA I would poke something in the PCI subsystem to
make it enumerate the PCI config space again?
Some things to consider:
- our PCIe device is a bus master, we use DMAR through the vt-d IOMMU to
create large chunk of device side contiguous addresses DMA area on our
current product (will do without for our next product)
- We are considering the latest Atom E6xx and it's fellow chipset and
perhaps uEFI for our next product. Does the firmware necessarily need to
be hotplug aware or can everything be controlled from linux? Do I even
have to worry about this?
- The card would obviously always be physically connected (closed
casing), so I guess some pins on PCI Express bus would have to be
asserted/deasserted to trigger a presence detect once the FPGA
programming is done perhaps?
Are there examples of other device drivers in the kernel that do
something similar? Any pointers are appreciated.
Thanks in advance
/jfd
--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
reply other threads:[~2011-03-11 16:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1299862375.8754.5.camel@jfddesk \
--to=jeff.dagenais@gmail.com \
--cc=linux-newbie@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