Timeline for enable/disable PCI interrupts
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 7, 2015 at 7:32 | answer | added | Simon Richter | timeline score: 2 | |
| Nov 15, 2015 at 6:02 | comment | added | Mark | @pjc50, if a driver selects to use a certain type of interrupts, e.g. INTx, does it have to disable MSI/MSI-X interrupts delivery via MSI_CAP pci registers? (And the other way around -- disable INTx when using MSI) | |
| Nov 13, 2015 at 18:47 | history | tweeted | twitter.com/StackElectronix/status/665239591658631168 | ||
| Nov 13, 2015 at 18:21 | comment | added | johnnymopo | IF you are using linux, could you use the DMA framework for your application? It is very nice, you create the transaction, and it returns with an optional timeout when transaction is complete - you don't have to fool with the actual interrupt | |
| Nov 13, 2015 at 16:39 | comment | added | pjc50 | You generally have to enable them all the way up by providing configuration for what should be done with the interrupt. Once that's done disabling is on the CPU only for brief periods of noninterruptible computing, until you deconfigure the device (eg for power saving) | |
| Nov 13, 2015 at 16:38 | comment | added | Tom Carpenter | In Windows KMDF drivers you specify in the driver .inf file what type of interrupts to use (MSI vs INTx vs MSI-x) and the driver framework will correctly configure the PCIe config space itself when it loads. I don't know about other OSes, but as .inf's are Windows specific I think it probably is OS dependent. | |
| Nov 13, 2015 at 16:32 | review | First posts | |||
| Nov 13, 2015 at 19:33 | |||||
| Nov 13, 2015 at 16:31 | history | asked | Mark | CC BY-SA 3.0 |