| 871b74873329f414ec8db3febadebf45e2003572 |
|
28-May-2014 |
Aravind Akella <aakella@google.com> |
Replace integer constants with strings in Activity Recognition HAL.
Change-Id: I67d543869f5870f9e771c36c0fe1d58e7495ca57
/hardware/libhardware/include/hardware/activity_recognition.h
|
| 153c40ce8bceb6674f605a10f98b84179cf7f204 |
|
07-May-2014 |
Aravind Akella <aakella@google.com> |
Activity Recognition HAL.
Add separate methods for enabling/disabling activities and rename activity constants.
Change-Id: I5986f6cf6ceb12a88f3d881ac5ccb6b9b50a2e58
/hardware/libhardware/include/hardware/activity_recognition.h
|
| 84d35492b145cebc000f8fd72818eb25b8e65c04 |
|
01-May-2014 |
Stewart Miles <smiles@google.com> |
Described restrictions for common HAL object methods.
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
/hardware/libhardware/include/hardware/activity_recognition.h
|
| 462eae34ce11e8e6bf5e28dc252d2d11052694e3 |
|
15-Mar-2014 |
Aravind Akella <aakella@google.com> |
Activity Recognition HAL.
Change-Id: I6fa175376464a4498fc9ed71dc33199be4754599
/hardware/libhardware/include/hardware/activity_recognition.h
|