summaryrefslogtreecommitdiffstats
path: root/include/hardware/activity_recognition.h
Commit message (Collapse)AuthorAgeFilesLines
* Replace integer constants with strings in Activity Recognition HAL.Aravind Akella2014-06-031-26/+47
| | | | Change-Id: I67d543869f5870f9e771c36c0fe1d58e7495ca57
* Activity Recognition HAL.Aravind Akella2014-05-191-33/+37
| | | | | | Add separate methods for enabling/disabling activities and rename activity constants. Change-Id: I5986f6cf6ceb12a88f3d881ac5ccb6b9b50a2e58
* Described restrictions for common HAL object methods.Stewart Miles2014-05-121-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Inheritance of HAL object is performed by composing a child structure of a single parent structure located at offset 0 followed by new data members and function pointers in the child structure. For example, struct child { struct parent common; int a_data_member; void (*a_method)(struct child *c, int v); }; HAL code assumes this layout when accessing child structures given a pointer to a parent structure such that users write code like the following... void child_method(struct *parent, int v) { struct child * c = (struct child*)parent; // do stuff with c } Code above will break if a member is added before "common" in "struct child". This change adds comments that describe the restriction on the location of parent HAL objects within a derived HAL object. HAL objects that already have comments that describe the required location of parent objects are not modified. Change-Id: Ibe4300275286ef275b2097534c84f1029d761d87
* Activity Recognition HAL.Aravind Akella2014-04-281-0/+186
Change-Id: I6fa175376464a4498fc9ed71dc33199be4754599