From: ext Felipe Contreras <felipe.contreras@xxxxxxxxx> Subject: [PATCH v2t2 00/17] omap: mailbox: Date: Fri, 21 May 2010 23:44:32 +0200 > From: Felipe Contreras <felipe.contreras@xxxxxxxxx> > > Hi, > > The main purpose of this patch series is to be able to compile mailbox > mach platform data as built-in. > > [no changes since the last v2, just rebased on top of the latest > git://gitorious.org/~doyu/lk/mainline.git for-tony-mailbox] > > Currently, the code is split into three places: > 1) mach-omapX/devices.c: for platform_device_register() the resources > 2) mach-omapX/mailbox.c: do platform_driver_register(), fetch the resources, > and register logical mailboxes with omap_mbox_register() > 3) plat-omap/mailbox.c: implement omap_mbox_register() to add the mbox > to an internal linked list (static struct omap_mbox *mboxes) > > So, obviously 1) is always built-in, but 2) can't be because of the > dependency of omap_mbox_register(), which is in 3) and cannot be taken > out. > > Users of mailbox will load 3) due to omap_mbox_get(), but not 2), > therefore, no mailboxes will be registered. How are the above user of mailbox loaded at present? I think that "bridgedriver.ko" is the user of it and it is also a platform driver. Someone would have to load it without udev, right? -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
