| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
Some vendors are confused by the use of errors vs acquired messages
This adds documentation on how they should be used.
Fixes bug 22728578
Change-Id: I5e6a8f7b159ec331a59202fa64b7320e43661429
|
|
|
|
|
|
|
| |
doc change.
Change-Id: If7e5738f921b0e91e46efc813d9f3c4bd1502832
Signed-off-by: Sasha Levitskiy <sanek@google.com>
|
|
|
|
|
|
|
| |
Bug: 21282699
Change-Id: I02e13b7da0ad361a95b981f9745aac039151f356
Signed-off-by: Sasha Levitskiy <sanek@google.com>
|
|
|
|
|
| |
Change-Id: Iba2f6a5bc7a2923c3e9b92684a2fab2190f14fd5
Signed-off-by: Sasha Levitskiy <sanek@google.com>
|
|
|
|
|
| |
Change-Id: Ibe991d5f5e4bb77a859284a8f890a6bccc663448
Signed-off-by: Sasha Levitskiy <sanek@google.com>
|
|
|
|
|
| |
Change-Id: I4a1da563a96a1e097ea56e0dced8c02820aa8485
Signed-off-by: Sasha Levitskiy <sanek@google.com>
|
|
|
|
|
| |
Change-Id: Ic6e7ad21cd3a253a38a6291bf08517c7e441af2b
Signed-off-by: Sasha Levitskiy <sanek@google.com>
|
|
|
|
|
| |
Change-Id: If45ebc228425eaa43bf9abde934f8bb4e7d97e6c
Signed-off-by: Sasha Levitskiy <sanek@google.com>
|
|
|
|
| |
Change-Id: Ied10a03213b8473b1a625229a75b7af6126d635a
|
|
|
|
| |
Change-Id: I416dcc42fd70926875cc77e0c2cc958fdfcd9f9d
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds vendor-specific messaging capabilities to the
HAL driver to avoid the possibility of vendors clobbering
general-purpose methods. The framework translates these
additional messages as an offset into a custom message array.
Additionally, authenticate() now takes a group id to restrict
authentication to a subset of possible fingerprints.
Bug 16487912
Change-Id: I8a92a6c86b4729af03a5576b4a150b1c73fbc9cc
|
|
|
|
|
| |
Change-Id: I4ab0a511417742a4b0b912ebf98a3773ec22bb10
Signed-off-by: Sasha Levitskiy <sanek@google.com>
|
|
|
|
| |
Change-Id: I7a4b1caadfe499d2394c8645e45903759b672e8b
|
|
|
|
|
| |
Change-Id: If943fe6b46a8261ca936e07a36e11c10c7e6d63a
Signed-off-by: Sasha Levitskiy <sanek@google.com>
|
|
|
|
|
|
|
| |
match confidence.
Change-Id: I62ce57054b7e0cfda8aa260176e504113677d993
Signed-off-by: Sasha Levitskiy <sanek@google.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
Change-Id: Id0a8e120043c00bf351aa1c9d3f0c06c2e4af947
Signed-off-by: Sasha Levitskiy <sanek@google.com>
|
|
|
|
|
| |
Change-Id: I7a2593837148ad80df970d89950f396c7704e71b
Signed-off-by: Sasha Levitskiy <sanek@google.com>
|
|
|
|
|
| |
Change-Id: I99e8e2f24f0264c2217d67a75fe437756596053c
Signed-off-by: Sasha Levitskiy <sanek@google.com>
|
|
|
|
|
|
|
| |
requested functionality.
Change-Id: Ib99e3edb99579ac4495918eb57d1022d75dccb57
Signed-off-by: Sasha Levitskiy <sanek@google.com>
|
|
Change-Id: I4e55c42841c3b6a1327a16bdf6d1d4bb3847c7f3
Signed-off-by: Sasha Levitskiy <sanek@google.com>
|