* On samsung, kernel exposes a sysfs node to disable fastcharge at
will, depending on what the user sets in battery settings UI.
* Disabling fast charge may be useful for reducing the heat produced by
the device while charging, or for extending the lifespan of the battery
* This commit introduces the fastcharge HIDL, which writes in the node
/sys/class/sec/switch/afc_disable
0 or 1 depeding on user selection.
0 means that fastcharge is enabled, while 1 means that fastcharge is
disabled
Change-Id: I369ba9c437b3a83a88c2ce74d603b7d7ddd9cfbb
* TARGET_TAP_TO_WAKE_NODE is defined in if condition. But in DT2W_PATH, TARGET_DT2W_PATH is defined. Why?
* Use same flag for both, otherwise we need to define two flags for the dt2w path.
* Use TARGET_TAP_TO_WAKE_NODE instead of TARGET_DT2W_PATH, for similarity with qcom powerHAL.
Change-Id: I87cbdc3f2aa1a3f9f6509580f2c1f001129a0fda
This is a power HAL for non-qcom Samsung devices.
It currently supports standard multi-core systems as well as
big.LITTLE configurations.
This HAL auto-detects your touchscreen and touchkey input switches
and handles the interactive state requests.
I also implemented a check to make sure your touchkeys won't turn
on when they're not supposed to (for example when a CMHW class disables
the capacitive buttons and activates a software navigation solution).
This previously needed a kernel hack to make sure the touchkeys wouldn't
be activated when resuming from suspend.
Change-Id: I22888c5ac490c85c417c5457ea4f457f78ed3521
Patch Set 2: removed unused files,
as audio, camera and sensors are device specific
Patch Set 3: aries OMX
Patch Set 5: liblight patch for epic
Patch Set 9: liblight(s) is device specific, rmed it from here.
Change-Id: I57a3d5714037836bab441ee5a3e772c260fb21d4
Bruno Martins