Commit graph

5 commits

Author SHA1 Message Date
Chengu Wang
eb1bd05175 Define AR HAL API more clearly
- Initial event.
- No events after disable_activity_event.
- Synchronized flush.

Change-Id: I9cce29c18cd0c771e2c838ae1c2634fb71585d20
2015-12-17 16:47:45 -08:00
Aravind Akella
871b748733 Replace integer constants with strings in Activity Recognition HAL.
Change-Id: I67d543869f5870f9e771c36c0fe1d58e7495ca57
2014-06-03 01:37:50 +00:00
Aravind Akella
153c40ce8b Activity Recognition HAL.
Add separate methods for enabling/disabling activities and rename activity constants.

Change-Id: I5986f6cf6ceb12a88f3d881ac5ccb6b9b50a2e58
2014-05-19 11:13:28 -07:00
Stewart Miles
84d35492b1 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
2014-05-12 12:35:37 -07:00
Aravind Akella
462eae34ce Activity Recognition HAL.
Change-Id: I6fa175376464a4498fc9ed71dc33199be4754599
2014-04-28 18:27:49 -07:00