| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
Change-Id: I3652382433d365407bf006d71f36743aa89a76ee
|
| |
|
|
|
|
|
|
|
|
|
| |
Define two new tags for FBE Key Management.
FBE_ICE: This is a boolean which specifies if new key
management is used.
KEY_TYPE: Specifies if it is a DE_USER or a CE_USER key.
CRs-Fixed: 2288316
Change-Id: Id9468d1fab0b0517a0a96734cdfe5612855fd2d9
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit does following:
- Add/Remove softap interface at runtime, if needed.
- Use wlan.concurrent.interface as default softap interface.
- Add build time support to enable SAP+SAP feature using
QC_WIFI_HIDL_FEATURE_DUAL_AP flag. if enabled use wlan.interface
as second SAP interface.
Change-Id: Icde3d54eda0f142e20f33cdb7ed95152eeee0bec
CRs-Fixed: 2257197
wifi: Add logic to create secondary interface for STA mode too.
Previously we introduced dynamic interface create/remove logic for
SAP interface where wlan.concurrent.interface was given first
preference for SAP interface.
Remove this preference and fallback to use the default order of
choosing interface names. Also add create/remove logic for secondary
interface in STA mode too.
Change-Id: Iec5c4492096327a18e67f5129736a9bd3c8533f0
CRs-Fixed: 2268421
wifi: Remove dynamic interfaces as part of wifi chip stop/cleanup.
During interface initialization for additional SAP/STA request, new
interface is created dynamically. This interface is removed during
teardown. In cases, where wifi stop request comes before teardown,
dynamically created interface(s) are not getting destroyed.
This CL is to remove dynamically created interfaces as part of wifi
chip stop/cleanup. Additionally, move invalidateAndRemoveDependencies
before remove interface.
Change-Id: I2df499252670f63ee22223176c71273b33f70679
CRs-Fixed: 2533958
[Pig]: Update to LA.QSSI.11.0.r1-06700-qssi.0
Change-Id: I9d469526965e595d77732913f6607dcafab19a01
|
| |\
| |
| |
| | |
Change-Id: Id9168e2c172586eb917007f6dd6b3922b022db66
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Add atrace hal to the readtracefs group
Bug: 214591300
Test: adb shell perfetto (Use config with atrace_categories)
Change-Id: Id9e06f88539b59480d5cf57a4ba67cef4676c1d5
Merged-In: Id9e06f88539b59480d5cf57a4ba67cef4676c1d5
|
| |\|
| |
| |
| | |
Change-Id: Idb8b15a45ff5484b65af7d9ffb3c4fa989f860eb
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
run VtsHalGraphicsComposerV2_2TargetTest will timeout failed
when there is dual displays. use `std::unordered_set` Display type,
`std::vector<Display>(mDisplays.begin(), mDisplays.end())` as
getDisplays return value, mDisplays elements order may not be
same as the order of hotplug events during boot matters.
We should store `mDisplays` as `std::vector`, since the order of
hotplug events during boot matters in determining the primary display.
Bug: 209409863
Test: run vts -m VtsHalGraphicsComposerV2_2TargetTest
Signed-off-by: Kui1 Wu <wukui1@xiaomi.com>
Change-Id: I628ad593640f28fb8a916822a91ac2c578cc299d
|
| |\|
| |
| |
| | |
Change-Id: I0c0e01f06373eda669262012d0f44644d397d452
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/1908681
Bug: 207920538
Change-Id: I4eb369495d27e697679ecb3d4381f0b3e0cef758
Merged-In: I388bc51e58b5680b5b5c806d88a338822af0c8a7
|
| |\|
| |
| |
| | |
Change-Id: I8517f19891cfec7bc67e5a754465584c121a3aac
|
| | |\
| | |
| | |
| | | |
sc-v2-dev
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
V6 and V7 use the audio policy configuration file for generating
the set of test profiles. The generator must only take into
account profiles of mix ports that are routed to device ports of
attached devices. Otherwise the HAL can rightfully refuse
to create a stream for the profile when the device isn't attached.
Bug: 205808571
Test: atest HalAudioV6_0GeneratorTest
Test: atest HalAudioV7_0GeneratorTest
Test: atest VtsHalAudioV6_0TargetTest
Test: atest VtsHalAudioV7_0TargetTest
Change-Id: I798f978c1c0bc32831c20e4b08338b462d8eea16
Merged-In: I798f978c1c0bc32831c20e4b08338b462d8eea16
|
| |\| |
| | |
| | |
| | | |
Change-Id: Ib7a0b60f2f202250941b169bbeaae3936d7b379e
|
| | |\ \ |
|
| | | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Update the VTS tests so that attestation keys are not created with
another purpose.
Bug: 197096139
Test: VtsAidlKeyMintTargetTest
Merged-In: Ib6e4ad98cbe5c3015138854679b11fa0e683ade9
Change-Id: Ib6e4ad98cbe5c3015138854679b11fa0e683ade9
Ignore-AOSP-First: cross-merge from aosp/master
|
| | |\ \
| | |/
| |/|
| | |
| | |
| | | |
* changes:
KeyMint VTS: extra unique ID test
KeyMint VTS: check INCLUDE_UNIQUE_ID works
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Test that specifying RESET_SINCE_ID_ROTATION results in a different
unique ID value.
Test: VtsAidlKeyMintTargetTest
Bug: 202487002
Change-Id: I2aed96514bf9e4802f0ef756f880cac79fa09554
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Bug: 202487002
Test: atest VtsAidlKeyMintTargetTest (on CF, O6)
Merged-In: I8bc674b47549aa1133f816c510289774db752e04
Change-Id: I8bc674b47549aa1133f816c510289774db752e04
Ignore-AOSP-First: already in aosp/master
|
| |\| |
| | |
| | |
| | | |
Change-Id: I7ecdede63de7066ef61002a43a73a9948f86274a
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The profiles generator wasn't loading correctly from the Audio
Policy Manager config file profiles with unpopulated attributes,
which is typical for dynamic profiles.
Bug: 204314749
Test: atest HalAudioV7_0GeneratorTest
Change-Id: I514a4e03da165cacb5dbaaa16470130895681484
Merged-In: I514a4e03da165cacb5dbaaa16470130895681484
|
| |\| |
| | |
| | |
| | | |
Change-Id: I4fb1731023442ee51c9315bfd32cf5e379f6defa
|
| | |/
| |
| |
| |
| |
| |
| | |
Bug: 203031664
Test: VTS
Change-Id: I68e7352ed95a8487dee291de493c78cf1491d569
Merged-In: I68e7352ed95a8487dee291de493c78cf1491d569
|
| |\|
| |
| |
| | |
Change-Id: Iac4222cd16e036b5179dec79ec3121a488ef3070
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Ensure that if TEST_PATTERN_MODE is listed in physical request keys, the
corresponding physical camera must support the privacy related test
pattern modes.
Test: Run Camera VTS with Cuttlefish emulator
Bug: 204108650
Change-Id: I8f378ab642c7c010a2ba73a8e89e65c91ba780eb
|
| |\|
| |
| |
| | |
Change-Id: I9a1508d726c90ae3194c4177df48aa91c405c558
|
| | |\ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
As per documentation the default auto rotate&crop mode must
be overriden before passing the capture request back to the
camera provider.
Bug: 204407427
Test:
atest
VtsHalCameraProviderV2_4TargetTest:PerInstance/CameraHidlTest#processCaptureRequestPreview/0_internal_0
atest
VtsHalCameraProviderV2_4TargetTest:PerInstance/CameraHidlTest#processMultiCaptureRequestPreview/0_internal_0
atest
VtsHalCameraProviderV2_4TargetTest:PerInstance/CameraHidlTest#processCaptureRequestBurstISO/0_internal_0
atest
VtsHalCameraProviderV2_4TargetTest:PerInstance/CameraHidlTest#flushPreviewRequest/0_internal_0
Change-Id: I1e1d387a04add8be9a281fcc3f78a867990248b3
|
| |\| |
| | |
| | |
| | | |
Change-Id: I8f70dbcc27621c906a9f1314fea6eb19d860fb67
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The multi-camera Grf requirement is now only applicable to rear facing
camera.
Test: Run test on Pixel devices
Bug: 204252005
Change-Id: Idb7735eebdc104f6ee6a5946b50c11aea809eb85
|
| |\| |
| | |
| | |
| | | |
Change-Id: I0f9a7d2b7bd50243b67f19138cf731c97126d548
|
| | |\ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug: 203031664
Test: manual
Change-Id: I6c9cbad7cd4fd19eb0b77c55ff37298b97f32050
|
| |\| | |
| | | |
| | | |
| | | | |
Change-Id: I68bc0a3d1a507e15e3792dadb987b285865db099
|
| | |\ \ \ |
|
| | | |/ /
| | | |
| | | |
| | | |
| | | |
| | | | |
Fix: 203414344
Test: m -j and start CAN services
Change-Id: I423ab883d959f234a52adf680fae91bf264bea8b
|
| |\| | |
| | | |
| | | |
| | | | |
Change-Id: I674da039b7c10936d732e8e01c2a0c7b59426501
|
| | |\ \ \
| | | | |
| | | | |
| | | | | |
setAllowedNetworkTypesBitmap" into sc-v2-dev
|
| | | |/ /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fix VTS for getAllowedNetworkTypesBitmap and
setAllowedNetworkTypesBitmap, which should not rely on
getRadioHalCapabilities.
Bug: b/199809900
Test: atest VtsHalRadioV1_6TargetTest
Change-Id: I0b50e7e6c0d406a62f7a1e2ea8ac9bc3a71d8aeb
Merged-In: I0b50e7e6c0d406a62f7a1e2ea8ac9bc3a71d8aeb
|
| | |\ \ \ |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The flags field in UserInfo is a int32_t that contains multiple
UserFlags 'or'ed together. We should not parse it as enum.
Test: atest android.hardware.automotive.vehicle@2.0-utils-unit-tests
Bug: 202520478
Change-Id: Ie7e81a8a5f39f6070e35f2e77bce88a211fd526b
|
| |\| | | |
| | | | |
| | | | |
| | | | | |
Change-Id: Ic52e613bcfc2a9df76a18fcc4e7f65987e3ae51b
|
| | |\ \ \ \ |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This CL makes following changes to fix VTS failures reported on Seahawk
reference platform.
* Correct the definition of RawStreamConfig and its size constant.
* Update all test cases to use a stream configuration reported by the
target camera device.
* Update CameraStreamExternalBuffering test cases to take internally
allocated buffers into account.
Bug: 192460757
Bug: 199626993
Test: atest VtsHalEvsV1_1TargetTest
Change-Id: Ia03775ae543617ba5057e91bbbb5aed9221d1a30
|
| |\| | | | |
| | | | | |
| | | | | |
| | | | | | |
Change-Id: I5b2bcc034918c90137995a8d6303fe7e88ee44ce
|
| | | |_|/ /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This reverts commit 6f36dd6e31ac1c2d62cd9283a4d07c7c684e5872.
Differing only by vsync period was not a requirement on Android R, and
it shouldn't be added after-the-fact to an existing HAL version.
There are devices on the market that switch seamlessly between configs
that differ in resolution/dpi, and therefore have those configs in a
common group.
Bug: 200184776
Merged-In: Id0bfc67e55d5139fddb2b359cabafd9281c33734
Change-Id: Ib6e6a8c5f45c9829ea30d031e1cfa9a4fb775535
|
| |\| | | |
| | | | |
| | | | |
| | | | | |
Change-Id: I1b83c0f752240dfde3cacd93d3f579ca40d88712
|
| | |\ \ \ \
| | | | | |
| | | | | |
| | | | | | |
sc-v2-dev
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
cp: aosp/1428863 to sc-v2-dev branch as b/202788915 mentioned
This used to be present on the old host side VTS tests, port the feature to
target side since host side VTS tests are deprecated.
Also,
i) Added a separate test: VtsHalWifiV1_4TargetTest to test the wifi
chip methods. Putting them in VtsHalWifiApV1_4TargetTest will prevent
these from running on devices without AP feature.
ii) Ensured all the non-NAN, non-RTT tests disable framework for
testing. NAN/RTT tests uses framework to check if the corresponding
package manager feature exists.
Bug: 166529516
Bug: 202788915
Test: atest \
VtsHalWifiApV1_0TargetTest \
VtsHalWifiApV1_4TargetTest \
VtsHalWifiV1_0TargetTest \
VtsHalWifiV1_4TargetTest
Change-Id: I05aab6992277601633a0f926a8262c4c27402e93
Merged-In: I05aab6992277601633a0f926a8262c4c27402e93
|
| | |\ \ \ \ \
| | |_|_|/ /
| |/| | | |
| | | | | |
| | | | | |
| | | | | | |
Original change: https://googleplex-android-review.googlesource.com/c/platform/hardware/interfaces/+/16087108
Change-Id: I29de6a4bf01101cb32d2aafd8a4dce8fa5f398c0
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
In some implementations P2P device interface is created under
primary interface(wlan0 by default). In those implementations
p2p device name is predefined in system property wifi.direct.interface.
And the interface is created by supplicant with primary interface as
the parent interface. The naming of p2p device interface is
p2p-dev-<parent interface> ("p2p-dev-wlan0").
With STA+STA feature, wlan0 interface gets deleted in certain scenarios
and wlan1 becomes the active interface. In such scenarios P2P fails to
create the interface as parent interface wlan0 is deleted.
To fix the issue update the p2p device interface from system property
based on the current active wlan interface. ie First get the p2p parent
interface name from p2p device interface name set in property.
Check if the parent interface derived from p2p device interface name is
the current active interface. If not, get the current active interface
and update the name as p2p-dev-<ifname> ("p2p-dev-wlan1").
This helps HIDL/supplicant to get an active wlan interface from p2p
device interface name and succeed in creating the p2p interface under the
active interface.
Bug: 203434193
Test: Manual - Tested STA+STA which ended up deleting wlan0 interface.
Then ran p2p tests and confirmed that p2p scan and connection
works.
Change-Id: I522cec02a662c057e21d434f3ed98c7e7a4ca8f0
Merged-In: I522cec02a662c057e21d434f3ed98c7e7a4ca8f0
(cherry picked from commit 7f2822aff735e3c4f727de0759f867791db129ed)
|