414 MHz is not enough to handle more intensive blur scenarios, e.g. a
single layer of notification shade blur with more content on top or
2 layers of blur when pulling down the notification shade on the recents
overview. Bumping the frequency slightly to 515 MHz alleviates most of
the jank in these scenarios.
Change-Id: I6e4671460911e26753c1f91383fff61b6e1cf500
We're using this hint for GPU-intensive blur, so it should boost the GPU
to a frequency high enough for that.
Change-Id: Ie88f6bb9a6acf979c70ecfb442a8d9774d509a22
Currently all writes to the dev interface are done
by WriteStringToFd that uses char internally.
The current values seem to expect to be written as s32,
this sadly won't happen and triggers a special case in
the write handling of pm_qos_power_write:
it expects char buffers to be encoded as base16 and
decodes them.
This means the current 44 is actually 0x44 -> 68 seen by
the kernel.
Luckily it seems like both accepted values for this node
don't hit the threshold to enter C2, so it was never
noticed in real usage and didn't effect the device
C-States handling during hints.
Signed-off-by: Luca Stefani <luca.stefani.ge1@gmail.com>
Change-Id: Ic544d4dcaa1edc3de913aed737baf1af88a45360
