AU: disable GPIOs in production; some structural changes
Since we are not making use of the GPIO funcionality in UE for the
moment, it's been advised that it should be disabled. This CL does just
that, plus a few small changes:
* Adds a "no-op" GPIO implementation, which simply returns a constant
value every time it's being asked whether test-mode was signaled (in
this case, we set it to return false).
* The GPIO handler is embedded in SystemState. This makes sense from
both the conceptual and usability standpoint. The SystemState object
can be parametrized to initialize either a real or a no-op GPIO
handler.
BUG=chromium-os:32263
TEST=passes unit tests; does not engage GPIO protocol on x86-alex
Change-Id: I8121647baa7611041073dcf305beddab57c0e49c
Reviewed-on: https://gerrit.chromium.org/gerrit/40633
Reviewed-by: Jay Srinivasan <jaysri@chromium.org>
Commit-Queue: Gilad Arnold <garnold@chromium.org>
Tested-by: Gilad Arnold <garnold@chromium.org>
diff --git a/udev_interface.h b/udev_interface.h
index b9765a8..4b8fc17 100644
--- a/udev_interface.h
+++ b/udev_interface.h
@@ -22,6 +22,8 @@
// more appropriate to an object-oriented setting...
class UdevInterface {
public:
+ virtual ~UdevInterface() {}
+
// Interfaces for various udev closers. All of these are merely containers for
// a single pointer to some udev handle, which invoke the provided interface's
// unref method and nullify the handle upon destruction. It should suffice for
@@ -133,6 +135,8 @@
// Implementation of libudev interface using concrete udev calls.
class StandardUdevInterface : public UdevInterface {
public:
+ virtual ~StandardUdevInterface() {}
+
// Concrete udev API wrappers utilizing the standard libudev calls.
virtual const char* ListEntryGetName(struct udev_list_entry* list_entry) {
return udev_list_entry_get_name(list_entry);