* Ohad Ben-Cohen <o...@wizery.com> [101018 00:41]: > From: Simon Que <s...@ti.com> > > Add driver for OMAP's Hardware Spinlock module. > > The OMAP Hardware Spinlock module, initially introduced in OMAP4, > provides hardware assistance for synchronization between the > multiple processors in the device (Cortex-A9, Cortex-M3 and > C64x+ DSP).
... > +EXPORT_SYMBOL_GPL(omap_hwspin_trylock); > +EXPORT_SYMBOL_GPL(omap_hwspin_lock_timeout); > +EXPORT_SYMBOL_GPL(omap_hwspin_unlock); > +EXPORT_SYMBOL_GPL(omap_hwspinlock_request); > +EXPORT_SYMBOL_GPL(omap_hwspinlock_request_specific); > +EXPORT_SYMBOL_GPL(omap_hwspinlock_free); > +EXPORT_SYMBOL_GPL(omap_hwspinlock_get_id); Please let's not add yet another omap specific layer that will make it incrementally harder to have generic drivers. Instead, we can do the omap specific locking in the platform code and then the drivers can use the functions passed in the platform_data if they're implemented. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
