Setting the owner of /dev/logbuffer_cpif as system to allow the
dump_modem script to read the logs as part of bugreport
Test: Tested bugreport on device
Bug: 318949647
Change-Id: I402049e9b7b42b31f6fd07e8bf3a9cafefdc6526
Signed-off-by: Mahesh Kallelil <kallelil@google.com>
init.zuma.soc.rc and init.zumapro.soc.rc only contain SOC related settings.
init.zumapro.board.rc contain board related settings
Bug: 311016628
Test: Build image and flash on KM4
Change-Id: I8f805a58a146009f301b9cb0da9d781c0f2245d9
After USB enumeration, some SD card readers do not send signals to the
device when the SD card is inserted or removed.
To support SD card hotplugging, this patch enables in-kernel
media-presence polling, which will check the SD card status every 2
seconds after a SD card reader is attached.
Bug: 186479576
Test: SD card insertion/removal and data copy (see b/301566595)
Change-Id: I46ebaa4321d0e7bfbc048910ff8cc72e8e4f9a92
Signed-off-by: Kuen-Han Tsai <khtsai@google.com>
The mq-deadline I/O scheduler is more stable than BFQ. Additionally, the
boot time is shorter with the mq-deadline I/O scheduler. Hence this CL.
Bug: 186902601
Change-Id: I3db5f132ca3485af9a84a3df63c8b0881c5fbdc8
Signed-off-by: Bart Van Assche <bvanassche@google.com>
For tuning gpu and tpu heavy mitigation, update divider to /4 instead of
/8. For triggering level, update TPU to 13.5A from 12A and update GPU
from 8A to 9A.
Bug: 315520392
Bug: 315519863
Bug: 315522696
Test: build and readback changes
Change-Id: If0b459ccc071ee9d25884e0c830b829f12eca314
Signed-off-by: Hiroshi Akiyama <hiroshiakiyama@google.com>
Presently the SOFT_OCP_GPU setting is very close to the actual OCP_GPU
level. Lower to 5A to separate the trigger levels. Update OCP_GPU to 8A
from 12A which exceeds programmable threshold.
Bug: 311832771
Test: boot device and check sysfs node readout for triggered_lvl
Change-Id: I27f9834200af1a85a1cf1abee2d9b58374cbb321
Signed-off-by: Hiroshi Akiyama <hiroshiakiyama@google.com>
Current zumapro proto devices are using init.zuma.rc which is a copy of
init.zumapro.rc. It won't work well for proto devices since it's based
on zuma soc. This change ports perf related configurations from zuma.
Also fix few perf configurations in current zumapro init rc file.
Bugs: 313501809
Test: build, flash and device boots
Change-Id: I3825f0b2e3fa8023ae6f953bb674cd32ddc53581
Set `avb_keys=no_such_key` for dynamic kernel partitions to allow booting
unlocked devices with a custom kernel. This allows a few things:
1) Dogfooders can flash a custom kernel without wiping their device.
This can help developers track down hard-to-reproduce bugs without
rolling out a patch to the whole dogfooder population.
2) Developers can uprev their device's kernel without wiping their
device or packaging the kernel with an Android platform build.
Note: we are using "no_such_key" to ensure an AVB keys file doesn't
accidentally get created.
Test: Flash CI build. Then flash custom kernel on top.
Bug: 274825778
Change-Id: If5ec2d8bcada451bb8291e66ca17014d2fa4ba1b
For P24 proto devices, they use zuma soc, it should load init.zuma.rc.
However due to hw difference between P23 and P24, init.zuma.rc cannot
be used on P24 directly. As P24 is brought up using init.zumapro.rc.
Fork init.p24.zuma.rc from init.zumapro.rc for P24 only.
Bug: 311016628
Test: flash KM4 proto and make sure init.zuma.rc is loaded.
Change-Id: Ib28b7ed5cf8b6f1bad1a7494a31a4eeaab608b67
Vendor sched procfs path hierarchy gets updated in kernel.
Update the paths in init rc file and task profiles to match the change.
Bug: 289151587
Test: pts-tradefed run commandAndExit pts -m PtsPerfWbsTestCases
-t com.google.android.perfwbs.pts.SchedulerTest
Change-Id: I22a97a08a87a402fb661a90a1e1c7a7a7f8536b3
Change the owner and group of the DRM module debug file to system to
grant permission for hwcomposer.
Bug: 301599195
Bug: 305948305
Test: check HWC can access it
Change-Id: Ib7ef46173bae350da85521f1baf19a0498481c10
allow ThermalHAL to overwrite trip point of rfpa_therm
Bug: 296476775
Test: adb shell ls -al dev/thermal/tz-by-name/rfpa_therm/trip_point_*
to validate permissions
Change-Id: Ib74e21d1c18f4e59f10cea3b52473e6935deed33
SMPL_WARN will trigger heavy mitigation while UVLO1 will trigger lighter
mitigation. This change will lower SMPL_WARN's voltage trigger threshold
to 3.0V and increase UVLO1's voltage trigger to 3.1V.
Bug: 308670320
Test: Read sysfs node for correct value
Change-Id: I7b179c442ee54df1971ffe882a363a45826a3f5b
Signed-off-by: Hiroshi Akiyama <hiroshiakiyama@google.com>
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
move the rfkill permission setting from post-fs-data to early_boot
stage because the kernel/net/rfkill/rfkill.ko may not be loaded on
post-fs-data stage and cause the permission setting failed.
Bug: 305968983
Test: reboot and check Bluetooth status
Change-Id: I985f53076066f5b69b919285faa52d1bed6892a7
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
