Google Git
Sign in
chromium / chromiumos / platform2 / libmems / ba9dbf825c3dd58747f77b699ccbee8489257a9e
commitba9dbf825c3dd58747f77b699ccbee8489257a9e[log] [tgz]
authorhscham <hscham@chromium.org>Thu Mar 17 05:32:12 2022
committerCopybara-Service <copybara-worker@google.com>Thu Apr 07 09:50:42 2022
treed8078a3e7335d1c3c339a5a155463861b58b94c6
parent69141d56e44d96f7298bc38a2e5dba1a82f204cc [diff]
platform2: remove unused base/macro.h

base/macros.h will be removed in r941411 (crrev.com/c/3279210). All
usages of DISALLOW_* macros have been migrated to delete ctors and
ignore_result to std::ignore so it is safe to remove the include.

See LSC proposal: go/chromeos-lsc-libchrome-remove-base-macro

BUG=b:211560276
TEST=CQ

Change-Id: Ia8a34295fa11c7c2bc88f37394f8855c67dace80
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/3531653
Owners-Override: Dominick Ng <dominickn@google.com>
Reviewed-by: Hidehiko Abe <hidehiko@chromium.org>
Commit-Queue: Grace Cham <hscham@chromium.org>
Tested-by: Grace Cham <hscham@chromium.org>
NOKEYCHECK=True
GitOrigin-RevId: 59189cee984506c11969e028f2a520fbecebbda6
3 files changed
tree: d8078a3e7335d1c3c339a5a155463861b58b94c6
  1. BUILD.gn
  2. common_types.cc
  3. common_types.h
  4. export.h
  5. iio_channel.h
  6. iio_channel_impl.cc
  7. iio_channel_impl.h
  8. iio_context.h
  9. iio_context_impl.cc
  10. iio_context_impl.h
  11. iio_device.cc
  12. iio_device.h
  13. iio_device_impl.cc
  14. iio_device_impl.h
  15. iio_device_test.cc
  16. iio_device_trigger_impl.cc
  17. iio_device_trigger_impl.h
  18. iio_event.cc
  19. iio_event.h
  20. iio_event_impl.cc
  21. iio_event_impl.h
  22. iio_event_test.cc
  23. libmems.pc
  24. libmems_test_support.pc
  25. OWNERS
  26. README.md
  27. test_fakes.cc
  28. test_fakes.h
README.md

Chrome OS IIO Sensor Utility Library

Project goal and motivation

This library provides a set of wrapper and test helpers around libiio.

It is meant to provide a common foundation for Chrome OS to access and interface IIO sensors, with:

  • a strong emphasis on testability;
  • readable code, with the ergonomics typical of platform2;
  • high performance.

Class hierarchy

At the root of the hierarchy, there exists the IioContext, which represents the IIO devices currently available on the system. These can be retrieved by name and inspected, via instances of IioDevice.

An IioDevice allows reading and writing attributes of an IIO device via type-safe helper APIs. It also offers support for configuring the buffer and trigger of an IIO device, which we use in order to allow the Chrome UI to read accelerometer data and support screen rotation.

An IioDevice also exposes a list of IioChannels, which can individually be enabled and disabled.

Test mocks

Useful mocks for the core classes are provided, such that a test author can focus on the logic of the unit tests and share a common testing language with other engineers working in this space. Sharing the foundation of testing IIO sensor access helps ensure that any improvement in this area can benefit all clients.