On Fri, Jan 30, 2015 at 9:41 PM, Ohad Ben-Cohen <ohad@xxxxxxxxxx> wrote: [..] > Since the existence of several hwblocks is still fictional (Bjorn, > please confirm too?), we may prefer to introduce changes to support it > only when it shows up; it all depends on the amount of changes needed. > Suman, care to take a look please? > It turns out that the Qualcomm platforms have two additional "remote spinlock" mechanisms - both using shared memory. On most platforms only 1 (out of these 3) is actually consumed, but e.g. the older msm7x30 uses 2 of them (SMEM and DAL). Due to its age I don't think it's on anyones todo list to actually support this platform as of today; but it's out there. None of these hwlocks are allocated dynamically, so if needed a dynamic base_id (-1 like other frameworks) would be a acceptable solution - and can easily be implemented when we need it. Regards, Bjorn -- 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
