On Fri, May 19 2017 at 02:41:43 PM, Matthias Brugger <matthias.bgg@xxxxxxxxx> wrote: > On 19/05/17 15:13, laurentiu.tudor@xxxxxxx wrote: >> From: Stuart Yoder <stuart.yoder@xxxxxxx> >> >> Move the source files out of staging into their final locations: >> -include files in drivers/staging/fsl-mc/include go to include/linux/fsl >> -irq-gic-v3-its-fsl-mc-msi.c goes to drivers/irqchip > > This driver has as compatible "arm,gic-v3-its". I wonder if this is > correct and if it should be moved like this out of staging. This is no different from the way we handle *any* bus that uses the GICv3 ITS as an MSI controller. Each bus provides its glue code that latches onto the ITS node, and calls into the generic code. Now, when it comes to moving this out of staging, here is my concern: There is mention of a userspace tool (restool) used to control the HW. Where is this tool? Where is the user ABI documented? Thanks, M. -- Jazz is not dead. It just smells funny. _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
