Disable cgroup kernel memory accounting to avoid unnecessary overhead
This is from similar change in zuma: ag/22891292
Bug: 300516320
Test: Boot
Change-Id: I1378fe11db294449978ea8e0157e8d8964a9a112
It's for early boot stage boost. After early init stage, change
it back to the default 32ms.
This is from the similar change we had in zuma: ag/23681609
Bug: 300516320
Test: check the device boot.
Change-Id: I2286a94c31480766540e20cab619cc87363bdd1f
Powerhal was disabled because the kernel vendor scheduler was disabled.
It caused log spamming since lots of procfs nodes were missing.
Now vendor schedule has been enabled, so enable the powerhal here.
Bug: 300514842
Test: manual device test.
Change-Id: Ia7407c15f68c31ede29442b4dc0e2777d749dcab
Disable page_pinner.
Bug: 304617279
Test: no page_pinner dir in debugfs
Change-Id: Ie2afe120068af3eb6bd469f3bb4ca27d46b7fec7
Signed-off-by: Minchan Kim <minchan@google.com>
It looks like this device configuration was copied before ag/22597180
was applied.
Zuma Pro counterpart for the following patch:
zuma: Bump deqp conformance level to 2023
Git hash f1c32332c3488e9c42008367e044f241f3abc8a5
Test: atest VtsGpuTests:com.android.gpu.vts.VulkanTest#checkCpuVulkanRequirements
&& atest VtsGpuTests:com.android.gpu.vts.OpenGlEsTest#checkOpenGlEsDeqpLevelIsHighEnough
Bug: 303925354
Change-Id: I709e1951b1f65a28e9bda08387924afc84c1d5b0
It looks like this device configuration was copied before ag/22512002
was applied.
Zuma Pro counterpart for the following patch:
Define mali configuration path explicitly
Git hash 7038bae086b572038ddb3d7b203b34b9519dd0fe
Test: None
Bug: 303925354
Change-Id: I39e3e4d0731129e3f5238700e0351840aed69f6d
It looks like this device configuration was copied before ag/22095163
was applied.
Zuma Pro counterpart for the following patch:
Fix mali memory protection sysprop names
Git hash c438c66fe03679b4791002d46afd83c2dca429b8
Test: CtsDeqpTestCases (dEQP-VK.protected_memory.stack.stacksize_*)
Bug: 303925354
Change-Id: I23400f4b2bd0c7e6ebe408e54b0c3ec209472b8c
Query the port partner's SVIDs when the DisplayPort driver sysfs
is not recognized so that the USB HAL can identify whether or not
the port partner supports Thunderbolt.
Test: manual verification on device - test to see that cableStatus
is set to NOT_CAPABLE on hub that supports Thunderbolt but not
DisplayPort Alt Mode. Then verify that device not capable of being
a DisplayPort sink but does support Thunderbolt does not trigger
this status.
Bug: 288150501
Change-Id: Iaba60ecc5510acecee1e1d3241611906c738a263
Signed-off-by: RD Babiera <rdbabiera@google.com>
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:873766c6f0c668ba526eaefe18ecc5e51ce87d67)
this should work with ag/24900428: equations of caimoto virtual skin
sensors
Bug: 296476775
Test: adb shell ls -al dev/thermal/tz-by-name/btmspkr_therm/trip_point_*
Change-Id: I943cb4b5323984bb1e6a4541978926f427d4ee12
Adds functionality for enabling and disabling DisplayPort Alt Mode
on the port through enableUsbData in the USB HAL to comply with USB
restrictions for heightened security mode.
Test: manual test on device - use enableUsbData dumpsys command to
turn off DisplayPort and then turn it back on while connected to a
partner sink.
Bug: 297208252
Change-Id: I9f071bce802b728f2229abc08efb2204e4c2505a
Signed-off-by: RD Babiera <rdbabiera@google.com>
