| 06ef205ebcb0d3f0fe2b88ddcea73e646981940e |
|
07-Nov-2014 |
Sharvil Nanavati <sharvil@google.com> |
Update module names to not use C preprocessor and to be at top of headers.
/system/bt/btcore/include/module.h
|
| 55fe5dc034bfc4d835816021c76bfae1c55e4890 |
|
07-Nov-2014 |
Chris Manton <cmanton@google.com> |
Expand include pathnames and add bd root path
Hopefully this will squash the sem_t semaphore_t collision
/system/bt/btcore/include/module.h
|
| 3c511e667e593c8ea594ca24b1d7712214245863 |
|
29-Sep-2014 |
Zach Johnson <zachoverflow@google.com> |
Add temporary callbacked wrapper for module startup
When all is said and done with the module conversions, all lifecycle functions
will run on the lifecycle managment thread, which can be blocked while waiting
for futures.
This CL means new modules can depend on that fact during start_up, alllowing
newly converted modules to be spliced into the existing startup callback madness
without having to sacrifice clean implementation.
We can add other callbacked lifecycle function variants as necessary.
/system/bt/btcore/include/module.h
|
| 72f308ee6d3983ae2c0d67be3de2451f2dd72dcb |
|
23-Sep-2014 |
Zach Johnson <zachoverflow@google.com> |
First pass at implementing modules
This first step creates the notion of a module and corresponding
lifecycle functions, with helpers to simplify working with them.
Once everything is converted over to this module format, then we
can make the stack manager automagically find the correct order for
init/start_up/shut_down/clean_up
/system/bt/btcore/include/module.h
|