Hi Jeff,
yes. We are using a canyonlands board with 460ex.
Ok.
2. You have some PCI device - what? Have you tested it works in a
standard PCI bus? Eg. ran lspci from an x86 host.
It is a FPGA board that we are using to develop a video codec/SOC. We
have not connected it an x86; however, we know the the PCI interface is
working because we can talk to the FPGA board.
Ok, so that means the BARs are setup.
3. When your host processor boots, it assigns the PCI resources.
On an x86, its the BIOS that assigns the PCI addresses and IRQs
on the PCI devices. For your 460EX, it could be your bootloader,
or it could be your host OS (Linux).
We are using the vanilla versions of u-boot and linux for the
canyonlands boards and have made few changes and definitely not to the
PCI setup.
4. If you boot Linux on your 460EX and run lspci, and the device
configuration space register for the IRQ line is 0, then your
host has not setup the PCI interface on your device correctly.
So what does the output of lspci look like?
5. Once you have the PCI IRQ assigned to the device correctly,
you need to know which IRQ line on the host this corresponds to.
I'm pretty sure that needs to be described in the DTS as
commented by Stefan.
So are you saying linux should be writing the irq number to the
INTERRUPT_LINE config reg? This is what I expected but I do not see
it.
Yes. U-Boot or Linux needs to configure the PCI interface.
The output of lspci, or a logic analyzer trace of the PCI
activity on boot would help tell you what is happening.
I believe the DTS is being parsed properly and the connection is made
to the correct interrupt line on the device.
Right, so if someone asserted the interrupt the host would
understand it was from the PCI system.
But somebody still needs to assign and IRQ number, right?
Yep. It might require enabling a PCI subsystem in U-Boot.
I recall playing with a Yosemite board and a PCI card,
but I forget whether I had to do anything to enable
PCI configuration space setup. Post a question to the
U-Boot list.
This is the part that is not clear, there is an irq field in
pci_dev structure which is filled in after looking at the
DTS and I just want to be sure this is the irq number to
be used when calling request_irq.
Really? I thought the pci_dev structures represent the
devices found on the PCI bus, and the IRQ line in
that structure was merely copied from the configuration
space registers. When you request that interrupt, the
code would have to remap it to a host IRQ line, which
it would use the DTS for. (But I'm just speculating).
Bottom line is; if the IRQ field of lspci is 0, then you
need to figure out that problem first :)
Cheers,
Dave
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
