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
This is to prepare dev_type test earlier. It checks whether /dev nodes
have labeles with dev_type or not.
Bug: 303367345
Test: build
Change-Id: I4feb079d4a3badc6362127a09f8d458755d7d2d2
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
Target FCM level 8 requires the newer version of the following HALs:
android.hardware.boot
Add the older version of these HALs into the customized product FCM
Remove below from customized product FCM and follow general rule:
android.hardware.biometrics.face
android.hardware.biometrics.fingerprint
android.hardware.contexthub
android.hardware.radio.config
Bug: 310792617
Change-Id: Ide9a0fd3cab4f6b23179b93d4a814eac3ede7b67
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
* changes:
usb: update usb hal version to v3
usb: update incompatible charger warning reason
Usb: Populate connected status of non compliant port partners only when not populated
Usb: Set connected status when connected to non compliant port partners
Usb: non-compliant port partner implementation
In the kernel, it is possible for the DisplayPort Alt Mode
driver to queue an Enter Mode message to the tcpm and have
that message be interupted by a Power Role or Vconn swap,
which results in the Port Partner never entering Alt Mode.
Add a debounce that checks to make sure that the port partner
enters Alt Mode when DisplayPort Alt Mode is active on the
port. On trigger, reattempt to send Enter Mode through the
tcpm up to 2 times.
Test: Manual test on device - put device into Preferred
Source role, test to see if Alt Mode reentry triggers
when original entry is interrupted by PR Swap from
monitor.
Bug: 308383356
(cherry picked from commit 04d1e94d10515f03e66cdfe16a23924e561cb3f3)
Change-Id: I96563c9900a01e428850e4873371bcdb0225aa07
Signed-off-by: RD Babiera <rdbabiera@google.com>
c2.android.av1-dav1d.decoder is based on dav1d implementation.
This dav1d-based sw av1 decoder provides better decoding throughput
than the default gav1-based av1 decoder on mid-to-low-tier devices.
c2.android.av1.decoder will be deprecate eventually before that we keep
both decoders.
Bug: 309412792
Test: run cts -m CtsMediaDecoderTestCases -t android.media.decoder.cts.VideoDecoderPerfTest --module-arg CtsMediaDecoderTestCases:instrumentation-arg:codec-prefix:=c2.android.av1.decoder
Change-Id: I7fa441b94127bcde45363d5445b97537358d6759
Report COMPLIANCE_WARNING_INPUT_POWER_LIMITED instead of
COMPLIANCE_WARNING_OTHER to flag incompatible chargers. The underlying
logic that generates the warning remains the same, what's changed is
the enum that's being used.
The purpose of the change is to have a warning type that better
represents what actually happens and free up COMPLIANCE_WARNING_OTHER
that was intended to act as a fallback reason code.
The flag enable_input_power_limited_warning controls whether to switch
to the new enum, while the flag enable_usb_data_compliance_warning
controls the new enums that are added as FlaggedApi in the framework.
Both flags need to be on to enable the change.
Bug: 308700954
Bug: 301380358
Test: manual tests with local flag override
Change-Id: I6595706d1b83d533fc2d3e29086773270e045ede
Set mode, power role and data role on non compliant port partners
only if the portStatus is not already populated. Compliance warnings
such as missing rp do not populate these fields during
getPortStatusHelper
Test: manual test on device
Bug: 279251052
Bug: 301380358
Change-Id: Ibe71bdd5c521ba90c124d89bd56af90087c0df18
Set mode, power role and data role when connected to non compliant
port partners.
Test: manual test on device
Bug: 268584498
Bug: 301380358
Change-Id: I6c3e7df09a61e26f3b976a86bd65cb646edd653d
Signed-off-by: Badhri Jagan Sridharan <badhri@google.com>
(cherry picked from commit 7c2d62aafc219af11252dabf49d84d84b7ccfa57)
Adds vendor code for non-compliant charger feature.
Minor port of commit 96ccf93453583642a15dd96b1e4d6bf0645fc10b
Test: atest VtsAidlUsbTargetTest
Test: manual test on device
Bug: 301380358
Change-Id: Ie1a48b1acaaae9a53f3b9bfebcfee7a2f4814810
(cherry picked from commit 96ccf93453583642a15dd96b1e4d6bf0645fc10b)
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
