Skip to content

[doc,otp_ctrl] Clarify read access specification #106

@matutem

Description

@matutem

Description

The documentation of partition's read access control is not clear. Some improvements:

  • the generated otp_ctrl_partitions.md file mentions read_lock as being CSR or digest, so the spec needs to explain what this means
  • with that explained, the spec can be more precise about read access and decouple it from the secret attribute
  • this would enable the read_lock hjson attribute of secret partitions to be either of the three options (none, csr, digest) but arguably only csr and digest should be legal

Separately, the term "hardware partition" is vague. Replace it with either partitions with hardware digests or buffered partitions, but these are synonymous since buffered partitions require hardware digests to perform consistency checks.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions