For PDK build, the "vendor/arm" path doesn't exist. The modules will be
built from vendor/google_devices/zumapro/prebuilts/gpu.
Flag: EXEMPT bugfix
Bug: 364491703
Test: 1. lunch comet-trunk_staging-eng
2. m libGLES_mali vulkan.mali libOpenCL libgpudataproducer
Change-Id: Ie58b2707fb9774f4a3552561b809c3c15d3803ef
This reverts commit 7e10eefc25.
Reason for revert: Re-enable EHLD since kernel EHLD issue is fixed.
Bug: 354380599
Change-Id: I588c2b96a69cabb7be8d264c9591b61da80fb5e2
The 16kb kernels need to select the fstab that has this configurations:
- data partition: fstab
- metadata partition: ext4
Bug: 350101696
Test: Built zumapro target and checked mounted partitions
Flag: EXEMPT bugfix
Change-Id: I2fc82946cdbadee7af0b3f6fc026b846fa79a146
The f2fs block size has to be set up to 16384 for 16kb kernels.
Bug: 350101696
Test: Built zumapro device and checked mounted partitions
Flag: EXEMPT bugfix
Change-Id: Ie3bf17d78da62a20882b17363afeb3a3a8a984e0
The zumapro targets that only boot with 16kb kernels will
have this filesystem setup for data and metadata partitions:
- data partition: f2fs
- metadata partition: ext4
Important: For the HW file encryption to work in the data partition in 16kb kernels the `dusize_4k` parameter has to be set:
```
fileencryption=:aes-256-hctr2:inlinecrypt_optimized+wrappedkey_v0+dusize_4k
```
Bug: 350101696
Test: built pgagnostic target and checked the fs for mounted
partitions.
Flag: EXEMPT bugfix
Change-Id: I566618e6fa1db2ff4463e00e8d091e7226ba0399
This variable doesn't do anything for devices launching with
API level 26 or later, and the initial zumapro devices (Pixel 9)
launched with API level 34.
Bug: 307369186
Test: presubmit
Flag: EXEMPT trivial build cleanup
Change-Id: If23568e7e1fc0dff05467e6b4fc97376c06c2233
For PDK build, the "vendor/unbundled_google" path doesn't exist.
"GoogleDialer" will be built from vendor/google_devices/zumapro/proprietary/GoogleDialer.
Flag: EXEMPT bugfix
Bug: 364510147
Test: export USES_GOOGLE_DIALER_CARRIER_SETTINGS=true; m GoogleDialer
Change-Id: I5c6796036627a5ae208dfda3ea19ead550a55c9a
The preferred_idle_mask is changed during boot time, but it does not
restore to the default setitng as in powerhint, so some node may keep
the wrong value when framework restarts.
Bug: 248621289
Test: build pass
Flag: NONE init rc file change does not support flags
Change-Id: Ib11681b9a751b1d67d02e9788d888e515d5a3519
kernel dev attribute has now been renamed from enable_usb
to move_data_to_usb. Update the same.
Bug: 251381400
Bug: 357028350
Flag: EXEMPT bugfix
Signed-off-by: Badhri Jagan Sridharan <badhri@google.com>
Change-Id: I8e4aa0b2e09bfef807f0169eabb79e2fa2e4d2c7
(ported from ag/20309232)
Signed-off-by: Kyle Tso <kyletso@google.com>
- power measurement result is on b/262803152#comment5
Bug: 355912013
Test: spatial audio
Flag: EXEMPT bugfix
Change-Id: I1b0712254875bbecc89cd2355a3eac18d3789666
Write to /sys/class/typec/port<...>/device/update_sdp_enum_timeout
to reduce SDP enumeration timeout value when device is in charger
mode. This will enable faster detection of a DCP port.
Test: Validate (in charger mode) that the sysfs attribute is 1
(meaning lower sdp timeout value is being used). Read dmesg to
see print showing timeout value is 5000ms.
Bug: 356685367
Flag: EXEMPT bugfix
Change-Id: I1bc872911d7f1eab26e62fe6f12fba05608e0f83
(porter from commit 3644ca07e87069fd2bed99f9f1fe13862ad43f62)
Signed-off-by: Amit Sunil Dhamne <amitsd@google.com>
Indicate to the kernel that the usb gadget is pulled up
by writing to `update_sdp_enum_timeout` sysfs node. Write
to this node will inform the kernel that it can lower the SDP
timeout alarm value which is used to detect an SDP port
vs a DCP.
Bug:356685367
Test: Check `update_sdp_enum_timeout` is written into after usb
gadget is pulled up. Verify that the alarm timeout lowers.
Flag: EXEMPT bugfix
Change-Id: Id3ae7e7a20b236cec6604414a7f81860e868bdd0
(ported from commit d8e2a02998fc1db9be00dab69a213378fb3caede)
Signed-off-by: Amit Sunil Dhamne <amitsd@google.com>
Revert submission 28323508-common_perf_init
Reason for revert: Potential culprit for b/360746202- verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.
Reverted changes: /q/submissionid:28323508-common_perf_init
Change-Id: Ice26f3451cec999b3b2b3e2f42c0aa06eff68f75
