On Tue, Sep 09, 2014 at 12:36:54PM -0300, Mauro Carvalho Chehab wrote: > Hmm... it seems that there are still several drivers still relying on > the functions declared at: omap-dma.h: > > $ grep extern include/linux/omap-dma.h |perl -ne 'print "$1\n" if (m/extern\s\S+\s(.*)\(/)' >funcs && git grep -f funcs -l > arch/arm/mach-omap1/pm.c > arch/arm/mach-omap2/pm24xx.c > arch/arm/plat-omap/dma.c > drivers/dma/omap-dma.c > drivers/media/platform/omap/omap_vout_vrfb.c > drivers/media/platform/omap3isp/isphist.c > drivers/media/platform/soc_camera/omap1_camera.c > drivers/mtd/onenand/omap2.c > drivers/usb/gadget/udc/omap_udc.c > drivers/usb/musb/tusb6010_omap.c > drivers/video/fbdev/omap/omapfb_main.c > include/linux/omap-dma.h > > Perhaps we can remove the header and mark all the above as BROKEN. Not quite. You'll notice that drivers/dma/omap-dma.c appears in that list. That is because right now, the new code has to co-operate with the old legacy code to ensure that both do not try and operate on the same hardware channel simultaneously. Right now, when anyone tries to use any of the drivers using the legacy APIs, they will get a warning printed in their kernel message log. This is part of my attempt to try and find out: (a) whether anyone is using these drivers (b) whether we can delete these drivers That warning has not been in the kernel long enough to be certain of anything - it was merged during the last merge window (despite me having it ready to go since the previous merge window, it would not have been correct to introduce a new warning during the -rc period.) What I recommend is that you just don't mark the OMAP drivers for compile testing right now, especially as their future is rather uncertain. -- FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up according to speedtest.net. -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
