The hispeed_freq value is read only in the inizialization process.
If we decide to change it later writing a new value to the node
this new value wont be taken into consideration by the power hal.
Lets update the hispeed_freq value in the power hal before using
it to limit the max cpu freq when we go into power save mode.
Change-Id: I4b8c7f67259750b2931b18c3871874022aa6054d
* Simplify interactive changes
* Better support for non-touchkey devices
* Only perform read I/O in samsung_power_set_interactive
if needed (improves wake->panel_on delay)
Change-Id: If7bd6a1833ac7605db437ef3664230f9a452d58b
* 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
