Currently, USB gadgdet hal couldn't access configfs nodes during
device booting. The permission of configfs nodes are root as default,
and they are modified to system by init process. Therefore, USB
gadget HAL can't access them before permission changes completely.
The patch will modify permission of USB gadget hal so that it can
access configfs nodes without permission change.
Bug: 204378488
Test: check connection time
Change-Id: I97f5446a51183225227744043e4a6e0088fecf0b
Change local hbm node ownership to allow framework to access.
Bug: 205640231
Test: check ownership after boot
Signed-off-by: Shiyong Li <shiyongli@google.com>
Change-Id: Iba041a9cf8672682411f2167f8677b30e5979027
Added SPDX-license-identifier-Apache-2.0 to:
conf/Android.bp
Bug: 68860345
Bug: 151177513
Bug: 151953481
Test: m all
Change-Id: Ie09443987ffc0749d8400387415c7257c033ddb6
Add a file "fstab.gs201-fips" alongside the existing "fstab.gs201" in
order to specify different encryption settings in FIPS mode.
"androidboot.fstab_suffix=gs201-fips" on the kernel command line will be
used to select the FIPS fstab when needed.
As the two fstabs should be otherwise identical, generate them from a
template file so that they will stay in sync.
Note that generating the fstabs requires that they be installed as build
system modules rather than via PRODUCT_COPY_FILES, which results in the
vendor_ramdisk copy of the fstabs being installed to system/etc rather
than /. This shouldn't cause any problem, now that Android has been
updated to look for the fstab in this location too.
(cherry-pick from device/google/gs101)
Test: Boot to home screen with/without fips mode
Bug: 202417706
Signed-off-by: Konstantin Vyshetsky <vkon@google.com>
Change-Id: I8fdc1c9a91399816fa2d4c53f282d63e988ce7d5
Currently, the streaming low hint is not used yet.
but we plan to use it with 30fps mode or at the modes that can remove
prefer idle.
(cherry-pick from device/google/gs101)
Bug: 205010238
Bug: 195327798
Signed-off-by: Peter Liu <pingchienliu@google.com>
Change-Id: Ibc75bf596bd05831605643c3fe427154fa626093
high-group is running on CPU 6-7.
mid-group is running on CPU 4-5.
mid-high-gropu is running on CPU 4-7.
Move camera tasks to CPU 4-7 for 1 seconds when AP launch.
(cherry-pick from device/google/gs101)
Bug: 205010238
Bug: 194271751
Test: GCA
Change-Id: I8e13e9ad0057b8f42f8ed3958bf0c6d58a5a02bc
This will improve the snapshot performance, especially JPEG encode.
(cherry-pick from device/google/gs101)
Bug: 205010238
Bug: 192067605
Test: Boot, CTS
Change-Id: I9b879d2c462e0a59891d9a36c770484d00b53e6e
CAMERA_STREAMING has the setting "TAPreferHighCap=1". GCA_CAMERA_SHOT should set "TAPreferHighCap=1" as well in case user leaves the viewfinder.
We could get better performance with "HighCapacityStartCpu=6".
(cherry-pick from device/google/gs101)
Bug: 205010238
Bug: 192534118
Test: manual R4
Change-Id: I85c77ac1ccc2176312b54a6acdd37df55a658f04
Add MIF, INT boost powerhint configuration for CAMERA_BACKEND_BOOST to
improve stability
(cherry-pick from device/google/gs101)
Bug: 205010238
Bug: 168654554
Test: 1. Check clock freq related file when camera start
2. Check face id function work correctly
3. P21 Camera Test Checklist done
Change-Id: Ia39acd531063bcf93c2db9971d783f6da8006502
clock when camera lauch and secure camera is not used
Add mem, mid CPU cluster power hint configuration when CAMERA_LAUCH
(cherry-pick from device/google/gs101)
Bug: 205010238
Bug: 168654554
Test: 1. Check clock freq related file when camera start
2. Check perfetto to make sure CPU clock setting does not reset by
BACKEN boost power hint
3. P21 camera checklist
Change-Id: Iadc7058c605533f8bd394dff1d9711bb7aca6897
GCA need intensive processing for camera shot and need to tune the
system performance to speed up the processing time. Adds
GCA_CAMERA_SHOT_{BIGCPU/BIGMIDCPU/ALLCPU} power hints to enable GCA to do
adequate power hint for this situation.
(cherry-pick from device/google/gs101)
Bug: 205010238
Bug: 187373665
Test: On device with GCA: b/187373665#comment8 with forrest.
Change-Id: Ife75e52a60de4d67369280998b193fe3ca7f8173
Reason for remove: face enroll fail
(cherry-pick from device/google/gs101)
Bug: 205010238
Bug: 168654554
Bug: 187759712
Test: check ISP clock freq no change on local device
Change-Id: I7d70c1fdd7e5d067db1941cced69a375b66ebc89
Prefer high cap and prefer idle is to optimize power and
trade off with scheduling latency.
Applying to app side does has no regression on frame drops.
And we can not apply prefer idle to hal process as it impact performance.
(cherry-pick from device/google/gs101)
Bug: 205010238
Bug: 190127212
Test:
1080p60: 20mW power saving, 59fps no regression
slow-mo 240fps: 239+fps
Change-Id: I548becbd2d6ccac8b576cfe54f9021bbf30b4801
improve camera start performace
(cherry-pick from device/google/gs101)
Bug: 205010238
Bug: 168654554
Test: 1. check clock freq related file when camera start
2. P21 camera checklist
Change-Id: I3447a6028846cc873e9c7195826c470bceaf03c8
Add two more mode for power hint fine tuning.
streaming extreme targets 240fps mode and streaming low targets photo
mode.
Test:
this change is no op, so we will do the test on corresponding lyric
change (ag/14804030).
(cherry-pick from device/google/gs101)
Bug: 205010238
Bug: 189886881
Signed-off-by: Peter Liu <pingchienliu@google.com>
Change-Id: Icd31501347108ccb5b0ec278a92bee89f543c192
Some GCA features perform better when running in high capacity cpus.
It is set in CAMERA_STREAMING_STANDARD, so photo mode and video mode
of 30 fps will use this setting.
(cherry-pick from device/google/gs101)
Bug: 205010238
Bug: 188777413
Test: ta_prefer_high_cap set correctly
Change-Id: I2fd444635a352d1c6236fd82eb82e67ca1799c97
Current mid cpu max clock is constrained by little cpu cap.
The cpu cluster clock constraint is going to be significantly reduced,
so put the current mid cap to avoid mid cpu regression.
Further fine tuning on the cap will be continued later.
(cherry-pick from device/google/gs101)
Bug: 205010238
Bug: 186564130
Signed-off-by: Peter Liu <pingchienliu@google.com>
Change-Id: I1e4568bb6e6167c91d8f98da337b1dd849a278bb
During streaming high fps mode, the BW is high and lead to CPU memory
high latency. This hint tries to avoid raising the CPU clock
at the condition when CPU is waiting for data access.
(cherry-pick from device/google/gs101)
Bug: 205010238
Bug: 184583714
Test:
4k60: 59+fps
1080p60fps: 58fps (b/186806120, disable eis can get 60fps)
Power benefit 80-100mW
Signed-off-by: Peter Liu <pingchienliu@google.com>
Change-Id: I3849dfd170085f7e10b5c53d27af353026a4093a
Prefer high cap will choose the mid / high cores when possible with
consideration of energy efficiency.
Running task on high cores with low clock is more efficient than running
at little core with high clock.
This hint also addresses CTS issues with keeping latency_sensitive = 1.
(equivalent to prefer idle)
This hint adds:
1) Enable prefer_high_cap of camera vendor group
2) Set high_capacity_start_cpu to 4
4) Set MemFreq floor
5) Change camera-daemon/cpu.uclamp.latency_sensitive owner to root
(cherry-pick from device/google/gs101)
Bug: 205010238
Bug: 186564130
Test:
android.hardware.camera2.cts.RobustnessTest#testAeAndAfCausality (5/5)
android.hardware.cts.CameraTest#testPreviewCallback (5/5)
android.hardware.camera2.cts.CameraDeviceTest#testCameraDeviceRepeatingBurst (5/5)
android.hardware.cts.CameraTest#testFocusDistances (3/6). (3/6) without CL.
*****************************************************************
raven Camera CTS Test Results
*****************************************************************
Tests Passed: 217, Failed: 0, Not found: 0, Status unknown: 0
Change-Id: Ia2abb0eb9c57fa05c4db7bf1d02053e303301781
In this commit, I remove WiFiOverlay and will add it into project
folder.
Bug: 204946036
Test: overlay configuration works as expected.
Change-Id: Iac69ff8749de7c2f43117f8e136bbfd0bd9a719d
This is not needed in device-specific init.rc file, because it's
is superseded by commit https://r.android.com/1866693.
Bug: 203720638
Test: presubmit
Change-Id: I74cfa6f3aa0c9125559f3241ed8e23f8a8510616
Fix to delete RTO too when delete all aiding received
Add mutex to protect malloc/free
Fix for the bug of power mode logging in ONCHIP_NMEA
[GNSS] Enable CHPP for P22
Reporting PLMN (MCC+MNC) of SIM and Network
[O6] 5s GPS outage when OnChip/Host switching
5G E911 AGPS implementation
Please clarify gnss error message
[SQ1A] [O6] Native crash - AID_GPS - signal 6 (SIGABRT)../gpsd (BrcmGpsHalLogJava::Log)
Bug:195383842
Bug:197716902
Bug:199048681
Bug:199265307
Bug:199818363
Bug:199114573
Bug:200107911
Bug:201582435
Bug:203068978
Verify Test: 203751055
Test: build pass and GNSS verify test pass
Change-Id: I2b667c559c1d955c981561c56bb11ab9a9952044
- This fixes ravenclaw build by continuing to use slider as
target_device for camera tuning.
- Can be updated in the future by properly providing ravenclaw
target_device throughout 3A.
Bug: 204945921
Test: Compiles.
Change-Id: Icb010127eedde87e2c2e0f59d6061d52f53e3ec5
The current name is confusing, as "device" normally refers to the
product name, not the SOC name.
Bug: 203283069
Test: build and flash affected devices
Change-Id: I51014a3316dec4509e0113280b723efb95d26fad
Enable the realted property and the needed files
for MMAP use cases.
Bug: 202810406
Test: Oboetester
Change-Id: Ie851dc0152589f405558c744b0101115d9f1d9b0
- use P7 config file as first draft
- add uwb country conf script
- add country config file (b/196073172)
Signed-off-by: Rex Lin <rexcylin@google.com>
Bug: 201232020
Test: ranging works with local build
Change-Id: I8c912becaa5b04f5656ff5b182028c02cc07fe06
On userdebug & eng builds, change the owner/group of SJTAG sysfs files
that need to be written to 'system', so that BetterBug is able to write
these files.
Bug: 204381544
Test: Ensure that the writable files in the following directories have
'system' as their owner & group:
/sys/devices/platform/sjtag_ap/interface/
/sys/devices/platform/sjtag_gsa/interface/
Signed-off-by: Peter Csaszar <pcsaszar@google.com>
Change-Id: I1fd61f702960a266bc8a2f84d1a1358ccefe3c9c
