Re: DVF_ATTACH_INPROGRESS

2018-11-30 Thread SAITOH Masanobu
On 2018/11/29 17:36, Masanobu SAITOH wrote:  Hi.  While I've been working for suspend/resume, I've noticed that some devices are reported "WARNING: power management not supported" in config_attach_loc() even though the driver has pmf_device_register() in it. The reason is that

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

2018-11-30 Thread Jared McNeill
On Fri, 30 Nov 2018, Martin Husemann wrote: On Fri, Nov 30, 2018 at 02:22:37PM -0400, Jared McNeill wrote: The driver can call pci_intr_type on the handle returned by pci_intr_alloc to see what kind of interrupt (INTx/MSI/MSI-X) was negotiated. Yeah, but the fear was that some hardware could

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

2018-11-30 Thread Martin Husemann
On Fri, Nov 30, 2018 at 02:22:37PM -0400, Jared McNeill wrote: > The driver can call pci_intr_type on the handle returned by pci_intr_alloc > to see what kind of interrupt (INTx/MSI/MSI-X) was negotiated. Yeah, but the fear was that some hardware could either do a single INT or (lots of) MSI{X},

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

2018-11-30 Thread Jared McNeill
On Wed, 28 Nov 2018, 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 device-specific (a value in a register, typically), meaning