dt-bindings: riscv: cpus: Clarify mmu-type interpretation
authorSamuel Holland <samuel.holland@sifive.com>
Wed, 27 Dec 2023 17:57:38 +0000 (09:57 -0800)
committerPalmer Dabbelt <palmer@rivosinc.com>
Thu, 11 Jan 2024 15:36:28 +0000 (07:36 -0800)
commita452816132d699bbb2af6fab8530685306054bda
tree8e19f6860c560233c769ff359ac461439bc11efa
parent951df4eb817cbb23fcac9e61de3ef4f8ca2c1a1d
dt-bindings: riscv: cpus: Clarify mmu-type interpretation

The current description implies that only a single address translation
mode is available to the operating system. However, some implementations
support multiple address translation modes, and the operating system is
free to choose between them.

Per the RISC-V privileged specification, Sv48 implementations must also
implement Sv39, and likewise Sv57 implies support for Sv48. This means
it is possible to describe all supported address translation modes using
a single value, by naming the largest supported mode. This appears to
have been the intended usage of the property, so note it explicitly.

Fixes: 4fd669a8c487 ("dt-bindings: riscv: convert cpu binding to json-schema")
Signed-off-by: Samuel Holland <samuel.holland@sifive.com>
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
Link: https://lore.kernel.org/r/20231227175739.1453782-1-samuel.holland@sifive.com
Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
Documentation/devicetree/bindings/riscv/cpus.yaml