staging: fsl-mc-bus: using MSI?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I have seen a few randconfig builds where FSL_MC_BUS is enabled.
This selects GENERIC_MSI_IRQ_DOMAIN -- even if CONFIG_PCI and
CONFIG_PCI_MSI are not enabled.  (This is with COMPILE_TEST enabled.)

I see in the README.txt file that the DPAA2/MC does use some kind of
message interrupts.

Several of the source files #include <linux/msi.h>.
I guess that these files get whatever they need from <linux/msi.h>
even though several of the CONFIG_ options are not enabled.

Anyway, having GENERIC_MSI_IRQ_DOMAIN enabled without CONFIG_PCI and
CONFIG_PCI_MSI causes a couple of build errors -- with COMPILE_TEST.


../kernel/irq/msi.c: In function 'msi_domain_alloc_irqs':
../kernel/irq/msi.c:356:19: error: storage size of 'arg' isn't known
  msi_alloc_info_t arg;
                   ^

../drivers/base/platform-msi.c:37:19: error: field 'arg' has incomplete type
  msi_alloc_info_t arg;
                   ^

thanks,
-- 
~Randy
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel



[Index of Archives]     [Linux Driver Backports]     [DMA Engine]     [Linux GPIO]     [Linux SPI]     [Video for Linux]     [Linux USB Devel]     [Linux Coverity]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux