Skip to content

Fix enum type to align with psa-arch-tests #11620

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 22, 2019

Conversation

jainvikas8
Copy link
Contributor

This is related to #11256
When TARGET_PSA is enabled on Cortex-A boards, the SECURE
is redeclared. So to minimize the impact we can redeclare this in
val.h which is used only by Mbed. And security_t itself is used in
mbed-os\components\TARGET_PSA\TESTS, but the SECURE string is not used.

This is related to ARMmbed#11256
When TARGET_PSA is enabled on Cortex-A boards, the SECURE
is redeclared. So to minimize the impact we can redeclare this in
val.h which is used only by Mbed. And `security_t` itself is used in
mbed-os\components\TARGET_PSA\TESTS, but the SECURE string is not used.

Renamed to `caller_security_t` which aligns with
https://github.com/ARM-software/psa-arch-tests
@jainvikas8 jainvikas8 changed the title Fix enum type to align with psa-arch-tests [WIP] Fix enum type to align with psa-arch-tests Oct 3, 2019
@ciarmcom ciarmcom requested a review from a team October 3, 2019 13:00
@ciarmcom
Copy link
Member

ciarmcom commented Oct 3, 2019

@jainvikas8, thank you for your changes.
@ARMmbed/mbed-os-maintainers please review.

@jainvikas8 jainvikas8 changed the title [WIP] Fix enum type to align with psa-arch-tests Fix enum type to align with psa-arch-tests Oct 3, 2019
@jainvikas8
Copy link
Contributor Author

@jamesbeyond Please, could you review it. Thanks.

} security_t;
CALLER_NONSECURE = 0x0,
CALLER_SECURE = 0x1,
} caller_security_t;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this changing actual enumerated types used by a developer ? Or is val.h a test only header file ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

val.h is a test only header file.

Copy link
Contributor

@0xc0170 0xc0170 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this breaking change - val.h is included outside of PSA (the application space)?

Copy link
Contributor

@jamesbeyond jamesbeyond left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In terms of greentea part this PR is OK for me. the changed files actually not part of the GreenTea framework, It is part of PSA Greentea test initialisation code. So the changes will not have impact to other greentea tests.

@0xc0170
Copy link
Contributor

0xc0170 commented Oct 21, 2019

@jainvikas8 please confirm this is backward compatible change. I'll start CI meanwhile

@jainvikas8
Copy link
Contributor Author

@jainvikas8 please confirm this is backward compatible change. I'll start CI meanwhile

There are NO API changes here. It is internal to test only code. So it should be backward compatible.

@mbed-ci
Copy link

mbed-ci commented Oct 21, 2019

Test run: SUCCESS

Summary: 11 of 11 test jobs passed
Build number : 1
Build artifacts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants