> The part I'm not clear what the purpose of "pool-hwlock" was. One use-case was a set of hwlocks having no fixed purpose, and being available for dynamic allocation between the OS and other entities (e.g. some RTOS on another core). The set of locks forming a reusable pool, and any information associated with them (e.g. the logical IDs used by the other entity) are a property of that interface rather than the hwlock provider. So you'd describe those pools of locks in some interface-specific manner, consuming hwlocks from a set of hwlock providers. Hopefully that doesn't maek things less clear... Mark. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
