Skip to content

[RFC] schemas: chosen: describe new arm,security-state property #163

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[RFC] schemas: chosen: describe new arm,security-state property #163

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions dtschema/schemas/chosen.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,6 +66,17 @@ properties:

This random value should be provided by bootloader.

arm,security-state:
$ref: types.yaml#/definitions/string
enum: [ non-secure, secure ]
Copy link
Member

@robherring robherring Jun 27, 2025

Choose a reason for hiding this comment

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

"non-secure" is the default for what's expected, so I don't think we should have a value for it. Then it becomes a question of whether we'd ever need something beyond "secure" and this could just be a boolean.

Copy link
Author

@a3f a3f Jun 27, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

From my experience, the default for ARMv7 is the kernel first starting in secure mode, because there's no OP-TEE or TF-A that switches to normal world.

description:
This property indicates the boot CPU's security state at the time
control was handed off to the OS. It's mainly useful on ARMv7,
where no generic mechanism exists to query the security state.
The OS can make use of this information to skip privileged errata
fixups that are off limits for non-secure software executing
in the normal world.

linux,booted-from-kexec:
type: boolean
description:
Expand Down