* Used by GCAM for DSP-accelerated HDR processing
* Arguably we should label /vendor/dsp/cdsp/fastrpc_shell_3 to
same_process_hal_file like Pixels, but the partition is prebuilt thus
we're unable to relabel it.
* Copy the file to writable tmpfs, setup attributes and bind mount back
to workaround the limitation.
[ghostrider-reborn]:
Allow adsp/cdsprpcd and neuralnetworks HAL to access fastrpc_shell_3
[kras edit:
1. rename some contexts as per qva/kona
2. extend to allow camera HAL and VPP service to access it as well]
[dereference23: Remove VPP policy because atoll doesn't use it]
Co-authored-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
Change-Id: Ide90e5c7307d413db5ece736e859559f06679545
There are several VMTs inside that library that are prone to change
on CAF merges.
So far, last LA.QSSI.11.0.r1-12300-qssi.0 merge already modified
ConfigInterface VMT in a way that's not backwards compatible thus
it'd be better if we provided a prebuilt library instead.
Change-Id: I25fe58e6721b8d0e67882f576cfaf288c9992fc9
LPRX was disabled previously on request because of some power issues.
Now that all the power issues is resolved enable the LPRX by default.
Change-Id: Ie3655bacfd06d47598b04e8c2c89233a000307ce
CRs-Fixed: 2459952
Currently, with drop_bcn_on_chan_mismatch disable
default value of drop_bcn_on_chan_mismatch is overwritten
and abnormal rssi is observed for some beacons.
To avoid the issue remove drop_bcn_on_chan_mismatch
from ini, So that default value of drop_bcn_on_chan_mismatch
can be used.
Change-Id: I6e7ec9327a2e13d1fed73bec2fedf8b584989930
CRs-Fixed: 2588983
TDLS off-channel feature is needed only for
certification. Disable the feature in production
builds.
Bug: 161320896
Test: Basic wifi sanity test.
Change-Id: I6d7a3e6bf58402c3c398bb8570cdc5ab1f7ca05d
* This enables Deep Sleep mode, additionally to QPower
* With this configuration, QPower manages the new Deep sleep mode
-> Leads to amazing power savings
Change-Id: I32dbaee6406fbe01594176ba14c9f3f0c6d16714
We're not using perfd so this is useless.
Signed-off-by: Subhajeet Muhuri <subhajeet.muhuri@gmail.com>
Change-Id: I3b436f3f747c6955335513a133da81d27a6fbf60
* proprietary perfd blobs can finally be nuked without breaking goodix
* we could even map the functions to use libperfmgr powerhints in the future
Change-Id: I124652f3041761966a3e3bd97c757fecc39cc5fb
It is no longer a surprise for anyone to see Xiaomi shipping the same
device with different displays and different displays usually mean
different touchscreen drivers.
The current double tap handling in the power HAL only takes into
account one specific node, meant to be set in the device tree.
However, if the touchscreen was registered as a different input device
it would cause the feature to be broken. Address the issue by iterating
through the input devices in order to find one supported touchscreen
input to be used.
Co-authored-by: LuK1337 <priv.luk@gmail.com>
Change-Id: I2f7fb4a8b0c9cd1a16d6c2b93602d285a191f170
The maximum frequency isn't effective from power consumption terms on
both clusters [1]. Replace maximum frequencies with lower ones to save some power.
[1] https://github.com/kdrag0n/freqbench/tree/96d72eac/results/sm7125/main
Change-Id: I6336bfce0dae8f578704c0bd9644c2829389762f
The difference in wakeup latencies isn't so significant, let CPU cores enter
deeper idle states to save some power.
Change-Id: I9b24adc356bf35bbdc0bda6e0eee982b4daf1350
