Re: pci_intr_alloc() vs pci_intr_establish() - retry type?

2018-11-28 Thread Michael
Hello, On Wed, 28 Nov 2018 07:48:09 -0500 (EST) Mouse wrote: > >> This reminds me - how does a driver know if any kind of MSI support > >> is even available? > > it shouldn't need to. > > Okay, then I'm missing something. I've seen hardware where enabling > MSI is something

Re: pci_intr_alloc() vs pci_intr_establish() - retry type?

2018-11-28 Thread Robert Swindells
Jared McNeill wrote: >On Wed, 28 Nov 2018, Jaromír Doleček wrote: > >> pci_intr_alloc() checks what the device claims to support down the >> call stack, reading the PCI config space. I assume there some >> negotiation between the PCI bus and the device. I hope device can't >> claim to support

Re: pci_intr_alloc() vs pci_intr_establish() - retry type?

2018-11-28 Thread Mouse
>> This reminds me - how does a driver know if any kind of MSI support >> is even available? > it shouldn't need to. Okay, then I'm missing something. I've seen hardware where enabling MSI is something device-specific (a value in a register, typically), meaning _something_ MD, presumably the

Re: pci_intr_alloc() vs pci_intr_establish() - retry type?

2018-11-28 Thread Jared McNeill
On Wed, 28 Nov 2018, Jaromír Doleček wrote: pci_intr_alloc() checks what the device claims to support down the call stack, reading the PCI config space. I assume there some negotiation between the PCI bus and the device. I hope device can't claim to support e.g. MSI-X if the bus doesn't.