History log of /system/nvram/hal/include/nvram/hal/tests/scoped_nvram_device.h
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
e52a7f4addee2c1b6b85fbd445890ccc1c5fc2d1 25-Jan-2017 Rahul Chaudhry <rahulchaudhry@google.com> system/nvram: fix typos and clang-tidy warnings

This change fixes a few typos and clang tidy warnings related to the
"llvm-namespace-comment" checks.

Bug: 26936282
Test: WITH_TIDY=1 WITH_TIDY_CHECKS="llvm-namespace-comment" mm
Change-Id: Ib2783ee52713c2b0e5da1b8131c7baec696e74f9
/system/nvram/hal/include/nvram/hal/tests/scoped_nvram_device.h
088471151b7784cef5a8555e1f155454df106113 08-Mar-2016 Darren Krahn <dkrahn@google.com> Add support for get_max_space_size_in_bytes().

This method, added in v1.1 of the HAL, allows an implementation to
report the maximum supported size for a single space.

This CL also includes a few enhancements to improve testing and adds a
top level Android.mk for convenience.

BUG=27480753

Change-Id: I962cc7a31e869e72920cd80146b69974e50d5745
/system/nvram/hal/include/nvram/hal/tests/scoped_nvram_device.h
811b136ab381658b7ec80aff885f80db495424d2 18-Feb-2016 Darren Krahn <dkrahn@google.com> Add HAL tests for access-controlled nvram.

These tests cover behavior documented by the HAL specification. They are
useful for evaluating conformance of an implementation. There are a few
features which are not tested because they cannot be undone without
factory reset. These features require manual testing.

- disable_create
- NV_CONTROL_PERSISTENT_WRITE_LOCK

BUG=26770111

Change-Id: I8d24fd5180ba33310172a5458589abe6fdf021aa
/system/nvram/hal/include/nvram/hal/tests/scoped_nvram_device.h