mirror of
https://github.com/Evolution-X/hardware_interfaces
synced 2026-02-01 11:36:00 +00:00
Only require RKP on T+ chipsets
It turns out we had a bug (b/263844771) in how RKP support was detected, and that was fixed. However, due to this bug, some S chipests shipped without RKP support which is now required by the tests. This change drops the RKP requirement from S chipsets. There should be no new S chipsets, so this effectively grandfathers in the previous ones that were skipped by the RKP VTS tests. T+ tests (both VTS and other suites) will verify that RKP support is there, so there is no gap introduced by this change. Bug: 297139913 Test: VtsAidlKeyMintTargetTest (cherry picked from https://android-review.googlesource.com/q/commit:8be875e0d0c18b8de67744c8b9629f2ff518dd60) Merged-In: I387e5f058ada698747aac103c1745682291f2d1c Change-Id: I387e5f058ada698747aac103c1745682291f2d1c
This commit is contained in:
committed by
Cherrypicker Worker
parent
bd4cdc6a9a
commit
166d160b78
@@ -1295,15 +1295,12 @@ std::pair<ErrorCode, vector<uint8_t>> KeyMintAidlTestBase::UpgradeKey(
|
||||
}
|
||||
|
||||
bool KeyMintAidlTestBase::IsRkpSupportRequired() const {
|
||||
if (get_vsr_api_level() >= __ANDROID_API_T__) {
|
||||
return true;
|
||||
}
|
||||
|
||||
if (get_vsr_api_level() >= __ANDROID_API_S__) {
|
||||
return SecLevel() != SecurityLevel::STRONGBOX;
|
||||
}
|
||||
|
||||
return false;
|
||||
// This is technically not a match to the requirements for S chipsets,
|
||||
// however when S shipped there was a bug in the test that skipped the
|
||||
// tests if KeyMint 2 was not on the system. So we allowed many chipests
|
||||
// to ship without RKP support. In T we hardened the requirements around
|
||||
// support for RKP, so relax the test to match.
|
||||
return get_vsr_api_level() >= __ANDROID_API_T__;
|
||||
}
|
||||
|
||||
vector<uint32_t> KeyMintAidlTestBase::ValidKeySizes(Algorithm algorithm) {
|
||||
|
||||
Reference in New Issue
Block a user